http://bugzilla.opensuse.org/show_bug.cgi?id=1093298 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |lnussel@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093298 http://bugzilla.opensuse.org/show_bug.cgi?id=1093298#c2 --- Comment #2 from Vinzenz Vietzke --- (In reply to Takashi Iwai from comment #1)

This usually indicates some BIOS firmware errors.

Could you check the kernel in OBS Kernel:stable repo and see whether these messages are gone?

Nope, unfortunately that didn't change anything.

If the messages have to be suppressed completely, you can pass loglevel=0 boot option instead of quiet option. ("quiet" is equivalent with loglevel=4.)

Thanks, that helped somehow. Error messages are supressed, but now Plymouth is gone as well. Any hints on that? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093298 http://bugzilla.opensuse.org/show_bug.cgi?id=1093298#c4 --- Comment #4 from Vinzenz Vietzke --- (In reply to Takashi Iwai from comment #3)

Maybe you can pass both options: quiet loglevel=0 ?

That didn't change anything. Regular boot messages appear until "Starting Plymouth..." followed by a few black lines and then further regular messages continuing.

Or plymouth.enable=1 might forcibly enable plymouth, too.

With this parameter all boot messages (ACPI errors included) are gone but still no plymouth. All in all this is what I have set in /etc/default/grub: "splash=silent quiet loglevel=0 plymouth.enable=1 showopts acpi_os_name=Linux acpi_osi= acpi_backlight=vendor" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093298 http://bugzilla.opensuse.org/show_bug.cgi?id=1093298#c6 Richard Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown@suse.com --- Comment #6 from Richard Brown --- Found the following which might be helpful https://bugzilla.redhat.com/show_bug.cgi?id=1413342 - Fedora bug about the same issue, closed as CANTFIX https://bugzilla.kernel.org/show_bug.cgi?id=193531 - Upstream kernel bug tracking the same issue -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093298 http://bugzilla.opensuse.org/show_bug.cgi?id=1093298#c8 --- Comment #8 from Zhao Qiang 赵强 --- Hi Takashi

From my point of view: if we agree this is a bug, then the direct fix is to disable the BIOS firmware errors in the kernel. Currently, we adjust the kernel log level, this solution doing much more than the expectation and it can't work with Plymouth. From Plymouth side, what you want is make it works with "loglevel=0" option right?

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093298 http://bugzilla.opensuse.org/show_bug.cgi?id=1093298#c10 --- Comment #10 from Takashi Iwai --- Vinzenz, could you try loglevel=1 instead of loglevel=0? Just a blind shot, but this might make difference. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1093298 http://bugzilla.opensuse.org/show_bug.cgi?id=1093298#c12 George Anchev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |studio@anchev.net --- Comment #12 from George Anchev --- I also get about 10 such messages on each boot: [ 1.790724] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364) [ 1.790732] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff880187d6acd0), AE_NOT_FOUND (20170303/psparse-543) This started to happen after update from Leap 42.3 to 15.0. Previously those could be seen in dmesg only but I have always had those messages. My kernel command line contains "splash=verbose quiet showopts elevator=deadline" I see some comments for an approach aimed to silence the messages but is this the right thing to do? Isn't the message an indication that there is something that needs fixing? BTW I don't know if this is related but just noticed it today: https://lkml.org/lkml/2018/7/27/921 -- You are receiving this mail because: You are on the CC list for the bug.