https://bugzilla.kernel.org/show_bug.cgi?id=215101
Rob Frawley 2nd (ker...@robfrawley.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ker...@robfrawley.com
--- Comment #7 from Rob Frawley 2nd (ker...@robfrawley.com) ---
(In reply to Zhang Rui from comment #6)
> In dsdt WT1A device object is defined under \_SB.I2CA
> [...code...]
> However, in ssdt3
> [...code...]
> It is redefining the \_SB.I2CA.WT1A object.
Although it appears to be a *different* object collision
(`\_SB.PC00.SAT0.PRT0.PWRG` from `20210730/dswload2-326`), a similar issue was
reported at https://bugs.launchpad.net/acpi/+bug/1978398 for Ubuntu 22.04
running the 5.15.x kernel. In my case, this occurs on a Lenovo Thinkpad P17
(Model: 20YU0066US).
> Did you observe any functionality issue?
> If no, I'd prefer to close this bug report as there is nothing we can do in
> Linux kernel to avoid this BIOS bug.
While I have yet to notice any regressions in functionality or stability and am
therefore not particularly worried about an actual fix, I have experienced
issues *hiding* this ring buffer message, as I want to present a "streamlined,"
"pleasant" bootup experience. More specifically, why does this message punch
through the "quiet" boot option? Is there any way to quiet it without resorting
to `quiet loglevel=n` (which, if aggressive enough, could easily hide other
issues that may crop up in the future that I *do* want to be notified of)?
> This is caused by bogus firmware.
I'm unfamiliar with how the kernel handles ACPI, so for my own information, can
you clarify what you mean by "firmware?" IE, do you mean to say that the error
is actually propagating from the firmware active on the hardware device, or do
you mean the error is being caused by some official/community/other created
firmware blob loaded by the kernel for specific hardware?
If the former: is there a way to silence anything propagated from the firmware
but not other important kernel warnings?
If the latter: what is the source of these firmware blobs?
---
Thanks for any help you can provide!
--
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
