LinuxQuestions.org - [SOLVED] ACPI Error [DSSP] Namespace lookup failure AE_NOT

Page 1 of 2

Show 50 post(s) from this thread on one page

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - ACPI Error [DSSP] Namespace lookup failure AE_NOT_FOUND on Slackware 14 64 bit (https://www.linuxquestions.org/questions/slackware-14/acpi-error-%5Bdssp%5D-namespace-lookup-failure-ae_not_found-on-slackware-14-64-bit-4175448907/)

m1m	02-06-2013 11:55 AM

ACPI Error [DSSP] Namespace lookup failure AE_NOT_FOUND on Slackware 14 64 bit

1 Attachment(s)

I have Gigabyte GA-B75M-D3V rev 1.1 motherboard with F10 BIOS.
I've got this error on my fresh Slackware 14 x64.

Code:

ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)

ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88021484f848), AE_NOT_FOUND (20110623/psparse-536)

I've attached full log - look at 4.14s.
It looks like related to SATA/ATA, but I don't have any problems with my drives... (so far)

willysr

02-07-2013 10:15 PM

Looking from some sites, i think it's related to ACPI and it's something that can get fixed by upgrading the firmware for the ROM

is this a server machine or desktop or laptop?

m1m	02-08-2013 04:37 AM

It's my private desktop. By "upgrading the firmware for the ROM" you mean BIOS?
I wonder what this error means, because I don't observe any problems during work.

H_TeXMeX_H

02-08-2013 05:01 AM

See:
https://bugzilla.redhat.com/show_bug.cgi?id=491588

I agree with willysr, update the BIOS, but only using the motherboard flash utility (should be in the BIOS settings) or a DOS boot disk.

willysr

02-08-2013 06:34 AM

That's the same reference i browsed before i came to the conclusion on my post above

m1m	02-08-2013 09:42 AM

Hey guys! Mine error is different than this from bugzilla:

Code:

ACPI Error (psargs-0355): [CS03] Namespace lookup failure, AE_NOT_FOUND

ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU0._CST] (Node ffff8101affb0a10), AE_NOT_FOUND

This looks like CPU-related [\_PR_.CPU0._CST], while mine is [\_SB_.PCI0.SAT0.SPT1._GTF] and comes just after SATA/ATA discovery (look at my full log)

Any other ideas?

H_TeXMeX_H

02-08-2013 09:49 AM

I think it is still BIOS-related, so if you can update the BIOS, you probably should.

m1m	02-08-2013 09:55 AM

Actually I have latest BIOS

volkerdi

02-08-2013 05:24 PM

Unless you can pin any failure on this error message, I'd ignore it. That's Matthew Garrett told someone reporting the same message on Fedora, and he tends to know what he's talking about.

It's hard to boot the kernel without at least a few scary looking messages. I think that's why some people are keen to hide them behind a splash screen.

allend

02-08-2013 06:39 PM

I have started seeing these messages at boot since I installed the 3.7.1 kernel. I consider them harmless. Faulty or incomplete ACPI information from the BIOS is a longstanding issue for Linux, which actually bothers about such things.

Code:

[  13.628947] ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \GLBC 1 (20120913/utaddress-251)

[  13.644573] ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \SACT 2 (20120913/utaddress-251)

[  13.660041] ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \SSTS 3 (20120913/utaddress-251)

[  13.675489] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

d_K	03-05-2017 03:25 AM

This is the first result on DDG so I'm also chiming in here...

I also just got this error on Antergos when a new hdd installed. I was super-paranoid the drive was damaged in some way, but everything appears to be "normal," latest arch 4.9.11 kernel, latest Asus bios, I did a self-check on the drive, 0 bad sectors, etc. Could this error simply be the result of: no volume "name"/no partition table? I get hung up on errors like this for weeks and I really don't feel comfortable considering how much stupid money was involved:mad:

slacktroll

03-06-2017 09:50 AM

I have errors to

Code:

[  72.923480] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150930/utaddress-254)

[  72.924277] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150930/utaddress-254)

[  72.925115] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150930/utaddress-254)

[  72.925942] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000051F (\LED_) (20150930/utaddress-254)

[  72.926477] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20150930/utaddress-254)

I actual updated my bios before because of other issues. BIOS got flashed by backup bios because it was corrupt. After that i never overclocked my machine and never looked back either.

I really think these messages are just warnings...

konenas

12-02-2017 03:35 AM

Acpi error ae_not_found

ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)

Quote:

OpenSUSE Tumbleweed Linux
kernel 4.14.2 (latest)

dmidecode:
BIOS Information
Vendor: American Megatrends Inc.
Version: F8 (latest)
Release Date: 11/08/2017
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.12

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z270-HD3P
Version: Default string
Serial Number: Default string
UUID: 031B021C-040D-0590-1806-FEXXXXXXXXXX
Wake-up Type: Power Switch
SKU Number: Default string
Family: Default string

amiba

11-13-2018 07:19 PM

I've a simular Problem but in my case the CRU-Driveholder isn't able to mount any drive any more. The fault was coming up after upgrade from 16.04 ubuntu to 18.04 I don't know if it was there before but I can see, that right now my CRU-Drive for changing in different drives isn't working any more. That's very bad.

Iv got an MSI Board and the fault messages nearly the same it is only the date in the first row 20131115/psargs-359 and in the second row it is instead of SPT1._GTF it is SPT5._GTF] (Node ffff880214186a50), AE_NOT_FOUND (20131115/psargs-536)

it worked proper with 16.04 ubuntu and it is very bad as it isn't now possible to load quick data in. As that Drive is not more usable.

Quote:

Originally Posted by m1m (Post 4885681)

I have Gigabyte GA-B75M-D3V rev 1.1 motherboard with F10 BIOS.
I've got this error on my fresh Slackware 14 x64.

Code:

ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)

ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node ffff88021484f848), AE_NOT_FOUND (20110623/psparse-536)

I've attached full log - look at 4.14s.
It looks like related to SATA/ATA, but I don't have any problems with my drives... (so far)

SnowArch

02-11-2020 04:59 PM

I can't even get past the try or install ubuntu window without this error freezong it when udb installing ubuntu 10/18.04 tried.

All times are GMT -5. The time now is 03:00 AM.

Page 1 of 2

Show 50 post(s) from this thread on one page