ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

Sin · 2015-10-20 23:08:50

Hello,
I have a little thing here... and i wanna ask you for help...
So the story goes like this:

Had W7, updated to W10 and random shutdowns started to occur. I was sure the overheating was causing this so i wanted to clean my laptop and in mean while i istalled arch. Ofc, it didnt help. Eventually

dmesg | grep -i acpi

told me this:

[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND (20110112/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f3425468), AE_NOT_FOUND (20110112/psparse-536)

From what i understand When upgrading from W7 to W10 OS become corrupted > BIOS pulled ACPI info from OS (this would explain why this nightmare is OS-indipendent and occures in BIOS too) > Every OS i try to install (which is not so easy since it shuts down in the middle of installation) fail. For now im using old installation of ubuntu i had on some random hdd, and in like one month i had 1 shutdown.

Maybe im wrong but this doesnt matter, i came here, today to ask for a little mercy...
PS. BIOS flashing is suicide right now.

ewaller · 2015-10-21 17:26:00

Welcome to Arch Linux.

Moving to Installation.
You might tell us what make and model is the machine. Also, be aware we can help you with Arch Linux only. For Ubuntu, we will refer you to their forums.
FWIW

[Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

can just be ignored. I think the other messages are benign as well. At least I do not think they are related to your problem.

Does the laptop have a log that you can get to from the BIOS/Firmware setup functions that tell you why it shut down?

Sin · 2015-10-21 23:12:02

Tomorrow i will try to post something. Anyway from what im reading it looks like system halts because of overheating - the problem is, it doesnt overheat... i may also try to install arch with acpi=off.

Dmesg

give me this:

ACPI: Thermal Zone [THRM] (46 C)

Meh, it looks like its a bad moment to be a linux newbe...

Last edited by Sin (2015-10-21 23:12:59)

ewaller · 2015-10-22 03:16:05

I still think if you told is the make and model it might be helpful. You might want to read the article linked in my signature.

Sin · 2015-10-22 13:23:27

Toshiba Satellite A300-1BU PSAJ4E
And here is the story as detailed as i remember:
>Upgraded from W7 to W10 and random halts started, but only after playing some games on facebook for few minutes
>Installed lated ubuntu, and nothing changer realy
>Installed Arch and it seemed like issue was gone but honestly i just used web browser for few days so i cant tall
>Opened laptop, cleaned it, changed thermal compound
>Booted arch and halts where immediate after boot
>I tried installing W7 or Ubuntu but i cant complete the installation process because of halts.
>Tought it may be some settings in BIOS. There is not realy any option to change other than Ahci, multicore, Execute Disable Bit.
>Also while in BIOS i noticed it halts here too.
>Tried memtest86 - halt. Tried 3 ramstics but its all the same.
>Out of despair i tried to boot from old hdd with ubuntu 10.04 - it works! I had only 1 halt when playing Urban Terror for like 40min. But since i cant install anything on this outdated mess i use only firefox and its just fine.

And one more thing: Befor halting, fan starts to spin fast for few seconds. Temps are ~40°C.

Alad · 2015-10-22 13:36:24

Check that the fans have an air gap available.

http://imgur.com/a/WvZ81

P.S. Sensor readings are often inaccurate (wrong placement, poor calibration etc. - search on a good tech site like silentpcreview.com on the matter)

Last edited by Alad (2015-10-22 13:39:37)

Sin · 2015-10-22 13:39:50

Yes, they have. As i said, temps are all good, at least this is what sensors are reporting.
...............
I mean, even if it was overheating (and it was befor i cleaned it with temps above 70°C), everything started to happen after upgrade to W10.

Last edited by Sin (2015-10-22 13:42:55)

Sin · 2015-11-06 13:05:55

Hello, its me again. Here is the kernel log before halt.

Nov  6 13:34:17 home-SA300 kernel: [ 3900.364315] usb 1-2: new high speed USB device using ehci_hcd and address 5
Nov  6 13:34:18 home-SA300 kernel: [ 3900.499725] cdc_acm 1-2:1.1: This device cannot do calls on its own. It is not a modem.
Nov  6 13:34:18 home-SA300 kernel: [ 3900.499886] cdc_acm 1-2:1.1: ttyACM0: USB ACM device
Nov  6 13:34:21 home-SA300 kernel: [ 3904.354403] usb 1-2: USB disconnect, address 5
Nov  6 13:34:22 home-SA300 kernel: [ 3904.624313] usb 1-2: new high speed USB device using ehci_hcd and address 6
Nov  6 13:34:22 home-SA300 kernel: [ 3904.808504] usbcore: registered new interface driver cdc_ether
Nov  6 13:34:22 home-SA300 kernel: [ 3904.812791] rndis_host 1-2:1.0: usb0: register 'rndis_host' at usb-0000:00:1a.7-2, RNDIS device, 02:5e:62:32:65:31
Nov  6 13:34:22 home-SA300 kernel: [ 3904.813046] usbcore: registered new interface driver rndis_host
Nov  6 13:34:22 home-SA300 kernel: [ 3904.834262] cfg80211: Calling CRDA to update world regulatory domain
Nov  6 13:34:22 home-SA300 kernel: [ 3904.838387] usbcore: registered new interface driver rndis_wlan
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842265] cfg80211: World regulatory domain updated:
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842268] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842271] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842274] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842276] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842278] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842281] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:32 home-SA300 kernel: [ 3915.200095] usb0: no IPv6 routers present

And here is syslog:

Nov  6 13:34:17 home-SA300 kernel: [ 3900.364315] usb 1-2: new high speed USB device using ehci_hcd and address 5
Nov  6 13:34:18 home-SA300 kernel: [ 3900.499725] cdc_acm 1-2:1.1: This device cannot do calls on its own. It is not a modem.
Nov  6 13:34:18 home-SA300 kernel: [ 3900.499886] cdc_acm 1-2:1.1: ttyACM0: USB ACM device
Nov  6 13:34:18 home-SA300 modem-manager[726]: <info>  (ttyACM0) opening serial port...
Nov  6 13:34:19 home-SA300 modem-manager[726]: <info>  (ttyACM0) closing serial port...
Nov  6 13:34:19 home-SA300 modem-manager[726]: <info>  (ttyACM0) serial port closed
Nov  6 13:34:19 home-SA300 modem-manager[726]: <info>  (ttyACM0) opening serial port...
Nov  6 13:34:19 home-SA300 modem-manager[726]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2 claimed port ttyACM0
Nov  6 13:34:19 home-SA300 modem-manager[726]: <info>  (ttyACM0) closing serial port...
Nov  6 13:34:19 home-SA300 modem-manager[726]: <info>  (ttyACM0) serial port closed
Nov  6 13:34:19 home-SA300 NetworkManager[721]: <warn> (ttyACM0): failed to look up interface index
Nov  6 13:34:19 home-SA300 NetworkManager[721]: <info> (ttyACM0): new GSM device (driver: 'cdc_acm' ifindex: -1)
Nov  6 13:34:19 home-SA300 NetworkManager[721]: <info> (ttyACM0): exported as /org/freedesktop/NetworkManager/Devices/3
Nov  6 13:34:19 home-SA300 NetworkManager[721]: <info> (ttyACM0): now managed
Nov  6 13:34:19 home-SA300 NetworkManager[721]: <info> (ttyACM0): device state change: 1 -> 2 (reason 2)
Nov  6 13:34:19 home-SA300 NetworkManager[721]: <info> (ttyACM0): deactivating device (reason: 2).
Nov  6 13:34:19 home-SA300 NetworkManager[721]: <info> (ttyACM0): device state change: 2 -> 3 (reason 0)
Nov  6 13:34:21 home-SA300 kernel: [ 3904.354403] usb 1-2: USB disconnect, address 5
Nov  6 13:34:21 home-SA300 modem-manager[726]: <info>  (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2
Nov  6 13:34:21 home-SA300 NetworkManager[721]: <info> (ttyACM0): now unmanaged
Nov  6 13:34:21 home-SA300 NetworkManager[721]: <info> (ttyACM0): device state change: 3 -> 1 (reason 36)
Nov  6 13:34:21 home-SA300 NetworkManager[721]: <info> (ttyACM0): cleaning up...
Nov  6 13:34:21 home-SA300 NetworkManager[721]: <info> (ttyACM0): taking down device.
Nov  6 13:34:21 home-SA300 NetworkManager[721]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov  6 13:34:21 home-SA300 NetworkManager[721]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.624313] usb 1-2: new high speed USB device using ehci_hcd and address 6
Nov  6 13:34:22 home-SA300 kernel: [ 3904.808504] usbcore: registered new interface driver cdc_ether
Nov  6 13:34:22 home-SA300 kernel: [ 3904.812791] rndis_host 1-2:1.0: usb0: register 'rndis_host' at usb-0000:00:1a.7-2, RNDIS device, 02:5e:62:32:65:31
Nov  6 13:34:22 home-SA300 kernel: [ 3904.813046] usbcore: registered new interface driver rndis_host
Nov  6 13:34:22 home-SA300 kernel: [ 3904.834262] cfg80211: Calling CRDA to update world regulatory domain
Nov  6 13:34:22 home-SA300 kernel: [ 3904.838387] usbcore: registered new interface driver rndis_wlan
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842265] cfg80211: World regulatory domain updated:
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842268] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842271] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842274] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842276] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842278] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 kernel: [ 3904.842281] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  6 13:34:22 home-SA300 NetworkManager[721]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/net/usb0, iface: usb0)
Nov  6 13:34:22 home-SA300 NetworkManager[721]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/net/usb0, iface: usb0): no ifupdown configuration found.
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): carrier is OFF
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): new Ethernet device (driver: 'rndis_host' ifindex: 3)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): exported as /org/freedesktop/NetworkManager/Devices/4
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): now managed
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): device state change: 1 -> 2 (reason 2)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): bringing up device.
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): preparing device.
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): deactivating device (reason: 2).
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Added default wired connection 'Auto usb0' for /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/net/usb0
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): carrier now ON (device state 2)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): device state change: 2 -> 3 (reason 40)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) starting connection 'Auto usb0'
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): device state change: 3 -> 4 (reason 0)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) scheduled...
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) started...
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 2 of 5 (Device Configure) scheduled...
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 1 of 5 (Device Prepare) complete.
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 2 of 5 (Device Configure) starting...
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): device state change: 4 -> 5 (reason 0)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 2 of 5 (Device Configure) successful.
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 2 of 5 (Device Configure) complete.
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 3 of 5 (IP Configure Start) started...
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): device state change: 5 -> 7 (reason 0)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> dhclient started with pid 2185
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 3 of 5 (IP Configure Start) complete.
Nov  6 13:34:22 home-SA300 dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Nov  6 13:34:22 home-SA300 dhclient: Copyright 2004-2010 Internet Systems Consortium.
Nov  6 13:34:22 home-SA300 dhclient: All rights reserved.
Nov  6 13:34:22 home-SA300 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Nov  6 13:34:22 home-SA300 dhclient: 
Nov  6 13:34:22 home-SA300 NetworkManager[721]: <info> (usb0): DHCPv4 state changed nbi -> preinit
Nov  6 13:34:22 home-SA300 dhclient: Listening on LPF/usb0/02:5e:62:32:65:31
Nov  6 13:34:22 home-SA300 dhclient: Sending on   LPF/usb0/02:5e:62:32:65:31
Nov  6 13:34:22 home-SA300 dhclient: Sending on   Socket/fallback
Nov  6 13:34:22 home-SA300 dhclient: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 3
Nov  6 13:34:23 home-SA300 avahi-daemon[719]: Joining mDNS multicast group on interface usb0.IPv6 with address fe80::5e:62ff:fe32:6531.
Nov  6 13:34:23 home-SA300 avahi-daemon[719]: New relevant interface usb0.IPv6 for mDNS.
Nov  6 13:34:23 home-SA300 avahi-daemon[719]: Registering new address record for fe80::5e:62ff:fe32:6531 on usb0.*.
Nov  6 13:34:25 home-SA300 dhclient: DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 5
Nov  6 13:34:27 home-SA300 dhclient: DHCPOFFER of 192.168.42.15 from 192.168.42.129
Nov  6 13:34:27 home-SA300 dhclient: DHCPREQUEST of 192.168.42.15 on usb0 to 255.255.255.255 port 67
Nov  6 13:34:27 home-SA300 dhclient: DHCPACK of 192.168.42.15 from 192.168.42.129
Nov  6 13:34:27 home-SA300 dhclient: bound to 192.168.42.15 -- renewal in 1760 seconds.
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> (usb0): DHCPv4 state changed preinit -> bound
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 4 of 5 (IP4 Configure Get) started...
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info>   address 192.168.42.15
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info>   prefix 24 (255.255.255.0)
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info>   gateway 192.168.42.129
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info>   hostname 'home-SA300'
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info>   nameserver '192.168.42.129'
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> Scheduling stage 5
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> Done scheduling stage 5
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 4 of 5 (IP4 Configure Get) complete.
Nov  6 13:34:27 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 5 of 5 (IP Configure Commit) started...
Nov  6 13:34:27 home-SA300 avahi-daemon[719]: Joining mDNS multicast group on interface usb0.IPv4 with address 192.168.42.15.
Nov  6 13:34:27 home-SA300 avahi-daemon[719]: New relevant interface usb0.IPv4 for mDNS.
Nov  6 13:34:27 home-SA300 avahi-daemon[719]: Registering new address record for 192.168.42.15 on usb0.IPv4.
Nov  6 13:34:28 home-SA300 NetworkManager[721]: <info> (usb0): device state change: 7 -> 8 (reason 0)
Nov  6 13:34:28 home-SA300 NetworkManager[721]: <info> Policy set 'Auto usb0' (usb0) as default for IPv4 routing and DNS.
Nov  6 13:34:28 home-SA300 NetworkManager[721]: <info> Activation (usb0) successful, device activated.
Nov  6 13:34:28 home-SA300 NetworkManager[721]: <info> Activation (usb0) Stage 5 of 5 (IP Configure Commit) complete.
Nov  6 13:34:32 home-SA300 kernel: [ 3915.200095] usb0: no IPv6 routers present
Nov  6 13:34:36 home-SA300 ntpdate[2231]: step time server 91.189.89.199 offset -1.292096 sec

Last edited by Sin (2015-11-06 13:09:20)

Arch Linux

#1 2015-10-20 23:08:50

ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

#2 2015-10-21 17:26:00

Re: ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

#3 2015-10-21 23:12:02

Re: ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

#4 2015-10-22 03:16:05

Re: ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

#5 2015-10-22 13:23:27

Re: ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

#6 2015-10-22 13:36:24

Re: ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

#7 2015-10-22 13:39:50

Re: ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

#8 2015-11-06 13:05:55

Re: ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

Board footer