TW: Strange messages from Kernel.....
Hi, since some time I receive every now and then strange messages from teh kernel: Message from syslogd@X1E at Dec 21 08:09:04 ... kernel:[22896.715276][ C0] Uhhuh. NMI received for unknown reason 20 on CPU 0. Message from syslogd@X1E at Dec 21 08:09:04 ... kernel:[22896.715282][ C0] Do you have a strange power saving mode enabled? Message from syslogd@X1E at Dec 21 08:09:04 ... kernel:[22896.715283][ C0] Dazed and confused, but trying to continue The Laptop - ThinkPad X1 Extreme running TW - was on low power last night, hibernated, and on shore power since 30 minutes. Power settings are 'standard'. However, my impression is, that on battery mode the Laptop consumes more power than usual. Was there a change in powermanagement recently? Expected: ~ 15W Actual: ~25W It takes 25W with Nvidia Card enabed, according to prime -select, nvidia card is turend off OK, these are already 2 questions, but from the same area. Cheers Axel
вівторок, 21 грудня 2021 р. 09:21:41 EET Axel Braun написано:
Hi,
However, my impression is, that on battery mode the Laptop consumes more power than usual. Was there a change in powermanagement recently?
Expected: ~ 15W Actual: ~25W
It takes 25W with Nvidia Card enabed, according to prime -select, nvidia card is turend off
OK, these are already 2 questions, but from the same area.
Cheers Axel
Hi, Check my message from yesterday [1] about TLP 1.4, it might be same problem. (short — try to revert nvidia to RUNTIME_PM_DRIVER_DENYLIST) [1] https://lists.opensuse.org/archives/list/support@lists.opensuse.org/ thread/AU3MZMIVHUN5VPBRXPZ3Y5TMMUJKJOVJ/ -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський
Hi Mykola Am Dienstag, 21. Dezember 2021, 19:36:35 CET schrieb Mykola Krachkovsky:
вівторок, 21 грудня 2021 р. 09:21:41 EET Axel Braun написано:
However, my impression is, that on battery mode the Laptop consumes more power than usual. Was there a change in powermanagement recently?
Expected: ~ 15W Actual: ~25W
It takes 25W with Nvidia Card enabed, according to prime -select, nvidia card is turend off
Check my message from yesterday [1] about TLP 1.4, it might be same problem. (short — try to revert nvidia to RUNTIME_PM_DRIVER_DENYLIST)
[1] https://lists.opensuse.org/archives/list/support@lists.opensuse.org/ thread/AU3MZMIVHUN5VPBRXPZ3Y5TMMUJKJOVJ/
I had seen this already, but thats not the cause of the issue More by chance I noticed that suspend mode is not working at all any more: - the LED in the lid blinks slowly, indicating suspend mode - however, the laptop is warm and consuming lots of power (which completely discharges the battery after a couple of hours) The log just indicates: kernel: acpi device:00: Failed to change power state to D0 at the end of the suspend process (Find full log plus following wake-up at https://paste.opensuse.org/17370583 ) Any idea how to investigate this? Cheers Axel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2021-12-26 at 10:29 +0100, Axel Braun wrote:
Hi Mykola
Am Dienstag, 21. Dezember 2021, 19:36:35 CET schrieb Mykola Krachkovsky:
вівторок, 21 грудня 2021 р. 09:21:41 EET Axel Braun написано:
...
I had seen this already, but thats not the cause of the issue
More by chance I noticed that suspend mode is not working at all any more: - the LED in the lid blinks slowly, indicating suspend mode - however, the laptop is warm and consuming lots of power (which completely discharges the battery after a couple of hours)
The log just indicates: kernel: acpi device:00: Failed to change power state to D0 at the end of the suspend process (Find full log plus following wake-up at https://paste.opensuse.org/17370583 )
Any idea how to investigate this?
Dez 26 00:16:40 X1E kernel: CPU11 is up Dez 26 00:16:40 X1E kernel: ACPI: PM: Waking up from system sleep state S3 Dez 26 00:16:40 X1E kernel: acpi device:00: Failed to change power state to D0 This is the end of the wake up process. <https://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface> G0 Working * S0 The computer is running and the CPU executes instructions. "Awaymode" is a subset of S0, where monitor is off but background tasks are running G1 Sleeping * S0ix Modern Standby,[35] or "Low Power S0 Idle". Partial processor SoC sleep.[36][37] Known to ARM and x86 devices. * S2 CPU powered off. Dirty cache is flushed to RAM * S3 commonly referred to as Standby, Sleep, or Suspend to RAM (STR): RAM remains powered * S4 Hibernation or Suspend to Disk: All content of the main memory is saved to non-volatile memory such as a hard drive, and the system is powered down G2 Soft Off * S5 G2/S5 is almost the same as G3 Mechanical Off, except that the power supply unit (PSU) still supplies power, at a minimum, to the power button to allow return to S0. A full reboot is required. No previous content is retained. Other components may remain powered so the computer can "wake" on input from the keyboard, clock, modem, LAN, or USB device G3 Mechanical Off The computer's power has been totally removed via a mechanical switch (as on the rear of a PSU). The power cord can be removed and the system is safe for disassembly (typically, only the real-time clock continues to run using its own small battery) Device states The device states D0–D3 are device dependent: D0 or Fully On is the operating state. As with S0ix, Intel has D0ix states for intermediate levels on the SoC.[38] D1 and D2 are intermediate power-states whose definition varies by device. D3: The D3 state is further divided into D3 Hot (has auxiliary power), and D3 Cold (no power provided): Hot: A device can assert power management requests to transition to higher power states. Cold or Off has the device powered off and unresponsive to its bus. The suspend actually happened here: Dez 25 18:46:10 X1E kscreenlocker_greet[15764]: ...... Dez 26 00:16:40 X1E kernel: bbswitc.... Notice the time jump. Some entries are actually written to the log when the machine wakes up, but belong to the suspend phase. Your problem, on wakeup, is logged here: Dez 25 18:46:10 X1E kernel: acpi device:00: Failed to change power state to D0 Dez 25 18:46:10 X1E kscreenlocker_greet[15764]: file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/components/UserList.qml:47:9: Unable to assign [undefine> Dez 26 00:16:40 X1E kernel: bbswitch: enabling discrete graphics Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. The suspend problem itself is not logged, because it mentions a problem going to D0, not to D3. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYcheIhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV1GUAnje08CFg4YrL7i/9SeUL zqQB9CQCAJwIDxim9xRkaykAKAgFQowl9Zfeeg== =9BsJ -----END PGP SIGNATURE-----
Hello Carlos, Am Sonntag, 26. Dezember 2021, 13:20:49 CET schrieb Carlos E. R.: ....
More by chance I noticed that suspend mode is not working at all any more: - the LED in the lid blinks slowly, indicating suspend mode - however, the laptop is warm and consuming lots of power (which completely discharges the battery after a couple of hours)
The log just indicates: kernel: acpi device:00: Failed to change power state to D0 at the end of the suspend process (Find full log plus following wake-up at https://paste.opensuse.org/17370583 )
Any idea how to investigate this?
Dez 26 00:16:40 X1E kernel: CPU11 is up Dez 26 00:16:40 X1E kernel: ACPI: PM: Waking up from system sleep state S3 Dez 26 00:16:40 X1E kernel: acpi device:00: Failed to change power state to D0
This is the end of the wake up process.
Correct.... ....
The suspend actually happened here:
Dez 25 18:46:10 X1E kscreenlocker_greet[15764]: ...... Dez 26 00:16:40 X1E kernel: bbswitc....
Notice the time jump. Some entries are actually written to the log when the machine wakes up, but belong to the suspend phase.
I'm pretty sure I closed the lid at 18:46 (suspend), and reopened at 00:16 (wakeup)
Your problem, on wakeup, is logged here:
Dez 25 18:46:10 X1E kernel: acpi device:00: Failed to change power state to D0 Dez 25 18:46:10 X1E kscreenlocker_greet[15764]: file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/compon ents/UserList.qml:47:9: Unable to assign [undefine>
That is the suspend.....
Dez 26 00:16:40 X1E kernel: bbswitch: enabling discrete graphics Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
The suspend problem itself is not logged, because it mentions a problem going to D0, not to D3.
...which is the odd thing, as suspend was at 18:46 I have now disabled tlp, and keep monitoring... Thanks Axel
On 26/12/2021 13.28, Axel Braun wrote:
Hello Carlos,
Am Sonntag, 26. Dezember 2021, 13:20:49 CET schrieb Carlos E. R.:
Any idea how to investigate this?
Dez 26 00:16:40 X1E kernel: CPU11 is up Dez 26 00:16:40 X1E kernel: ACPI: PM: Waking up from system sleep state S3 Dez 26 00:16:40 X1E kernel: acpi device:00: Failed to change power state to D0
This is the end of the wake up process.
Correct....
....
The suspend actually happened here:
Dez 25 18:46:10 X1E kscreenlocker_greet[15764]: ...... Dez 26 00:16:40 X1E kernel: bbswitc....
Notice the time jump. Some entries are actually written to the log when the machine wakes up, but belong to the suspend phase.
I'm pretty sure I closed the lid at 18:46 (suspend), and reopened at 00:16 (wakeup)
Yep.
Your problem, on wakeup, is logged here:
Dez 25 18:46:10 X1E kernel: acpi device:00: Failed to change power state to D0 Dez 25 18:46:10 X1E kscreenlocker_greet[15764]: file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/compon ents/UserList.qml:47:9: Unable to assign [undefine>
That is the suspend.....
"Change power state to D0" is waking up.
Dez 26 00:16:40 X1E kernel: bbswitch: enabling discrete graphics Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
The suspend problem itself is not logged, because it mentions a problem going to D0, not to D3.
...which is the odd thing, as suspend was at 18:46
Yes, but there is a moment during the suspend process when the hard disk is "stopped" and nothing more can be written to it, and after that is when the kernel does the actual suspend work. Any log entries done in that interval are stored in the memory of the syslog process, or the kernel message ring, I don't know for sure, and written when the hard disk is waken up again, so the timestamps for those events are wrong, they write the wake up time.
I have now disabled tlp, and keep monitoring...
-- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Am Sonntag, 26. Dezember 2021, 14:03:54 CET schrieb Carlos E. R.:
Your problem, on wakeup, is logged here:
Dez 25 18:46:10 X1E kernel: acpi device:00: Failed to change power state to D0 Dez 25 18:46:10 X1E kscreenlocker_greet[15764]: file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/comp on ents/UserList.qml:47:9: Unable to assign [undefine>
That is the suspend.....
"Change power state to D0" is waking up.
Dez 26 00:16:40 X1E kernel: bbswitch: enabling discrete graphics Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) Dez 26 00:16:40 X1E kernel: pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible) Dez 26 00:16:40 X1E kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
The suspend problem itself is not logged, because it mentions a problem going to D0, not to D3.
...which is the odd thing, as suspend was at 18:46
Yes, but there is a moment during the suspend process when the hard disk is "stopped" and nothing more can be written to it, and after that is when the kernel does the actual suspend work.
Any log entries done in that interval are stored in the memory of the syslog process, or the kernel message ring, I don't know for sure, and written when the hard disk is waken up again, so the timestamps for those events are wrong, they write the wake up time.
Ah OK....
I have now disabled tlp, and keep monitoring...
Noticed the issue again today. I have opened https://bugzilla.opensuse.org/show_bug.cgi?id=1194197 for this. Have a good new year! Axel
participants (4)
-
Axel Braun -
Axel Braun -
Carlos E. R. -
Mykola Krachkovsky