Bug 216629

Summary: After update to kernel 6.0.0 Thinkpad T60 and maybe some others old laptops did not poweroff
Product: Power Management Reporter: Igor V. Kuznetsov (virex)
Component: OtherAssignee: Rafael J. Wysocki (rjw)
Status: NEW ---    
Severity: high CC: regressions, tiwai
Priority: P1    
Hardware: Intel   
OS: Linux   
Kernel Version: 6.0.0 Subsystem:
Regression: Yes Bisected commit-id:

Description Igor V. Kuznetsov 2022-10-26 17:31:45 UTC 
After poweroff command OS halted but power is still on. 

I tested on another old laptops, and on old fujitsu Fujitsu-Siemens all work fine, but on others thinkpad T60 poweroff did not work

Poweroff last work fine on 5.19.12.1 kernel

I also try to test poweroff on 6.1.0-rc2-1.g796d87f and it is still did not work.

Video of testing https://youtu.be/A7-RqM1Ph3Q

(also created at link: https://bugzilla.opensuse.org/show_bug.cgi?id=1204717)
Comment 1 Artem S. Tashkinov 2022-10-27 08:46:12 UTC 
You may want to perform regression testing using git bisect.

Since your hw is relatively old very view people have hit the bug which means it's not known which means it may require you to act on it.
Comment 2 Igor V. Kuznetsov 2022-10-28 06:52:23 UTC 
About testing using git bisect, how exactly do it? I don't know anything about it.
Comment 3 Igor V. Kuznetsov 2022-10-28 06:53:25 UTC 
Can you tell me where to read about it, some rtfm or anything else?
Comment 4 Takashi Iwai 2022-10-31 09:33:39 UTC 
When you look for "linux kernel git bisect" on the net, you'll find many articles.
e.g.
  https://nathanchance.dev/posts/working-with-git-bisect/
  https://docs.kernel.org/admin-guide/bug-bisect.html
  https://kernelnewbies.org/Linux_Kernel_Tester%27s_Guide_Chapter4

My advice is to try to reduce the kernel config before starting bisection.
You can run "make localmodconfig" to get a minimalistic kconfig with the currently used modules, and you can use it as a base.  It's safer to modify CONFIG_LOCALVERSION not to override the existing kernels, too.

Also, git-bisect may switch the base kernel version (e.g. jumping from 6.0 to 5.18-rc5 or vice versa).  When switching the older base kernel version, the new kconfig items may be dropped.  Hence it's better to save the kconfig per version locally.

Last but not least, double-check you're testing with the right kernel.  It often becomes confusing which kernel you're testing, since the kernel version jumps up and down.  You can modify CONFIG_LOCALVERSION to indicate which test kernel it is, or set CONFIG_LOCALVERSION_AUTO and verify the git commit ID.