https://bugzilla.kernel.org/show_bug.cgi?id=218531
Hans de Goede (jwrdego...@fedoraproject.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwrdego...@fedoraproject.or
| |g
--- Comment #6 from Hans de Goede (jwrdego...@fedoraproject.org) ---
Thank you for reporting this and sorry about the regression.
> I've pinned down the commit after which the problem occurs:
> 847e1eb30e269a094da046c08273abe3f3361cf2 is the first bad commit
So you have build your own 6.6.17 kernel from source with just that commit
reverted and with that locally build 6.617 with that single commit reverted you
are not seeing this issue ?
> I think this CPU is in Goldmont microarchitecture group. The group is handled
> in a bit unique way in drivers/platform/x86/p2sb.c. I guess the commit
> affected
> handling of P2SB resource on machines with that architecture.
I just tried to reproduce this on one of my own laptops with a Apollo Lake
N3450 processor, but I cannot reproduce this. So this seems to be specific to
this one laptop model.
> dmesg (unhealthy): http://0x0.st/HRA7.txt
Unfortunately that is incomplete due to the errors being spammed to the log the
entire time, so it only contains a long list of the errors repeating.
Can you append " log_buf_len=50M" to your kernel commandline and then
*immediately*after boot run "dmesg > dmesg.txt"? And then please attach the
generated dmesg.txt here in bugzilla using bugzilla's attachment function.
Using pastebins is problematic because the links to these become invalid over
time.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
