https://bugzilla.suse.com/show_bug.cgi?id=1201121
Bug ID: 1201121 Summary: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---
Starting with the Tumbleweed snapshot installed on June 7th I get
kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
in my journal on every boot. Running fwupdmgr I get
fwupd[6102]: 12:26:06:0015 FuPluginDfu truncated DFU interface data, no bcdDFUVersion
The daemon nevertheless is starting.
Because there is no newer firmware for any of my devices I am not able to test, if an update would work despite these error messages. This is a XPS 13 9310 2-in-1/0NVVG0, BIOS 2.8.1 02/25/2022.
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c1
Takashi Iwai tiwai@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@mike.franken.de, | |tiwai@suse.com Flags| |needinfo?(opensuse@mike.fra | |nken.de)
--- Comment #1 from Takashi Iwai tiwai@suse.com --- When you boot with the previous kernel, does the message disappear? Please give the full dmesg output and the hwinfo output.
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c2
--- Comment #2 from Michael Hirmke opensuse@mike.franken.de --- (In reply to Takashi Iwai from comment #1)
When you boot with the previous kernel, does the message disappear? Please give the full dmesg output and the hwinfo output.
"Starting with the Tumbleweed snapshot installed on June 7th" - so this error exists for at least four weeks and a few kernels now.
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c3
--- Comment #3 from Michael Hirmke opensuse@mike.franken.de --- Created attachment 860052 --> https://bugzilla.suse.com/attachment.cgi?id=860052&action=edit dmesg
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c4
--- Comment #4 from Michael Hirmke opensuse@mike.franken.de --- Created attachment 860053 --> https://bugzilla.suse.com/attachment.cgi?id=860053&action=edit hwinfo
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c5
--- Comment #5 from Michael Hirmke opensuse@mike.franken.de --- Still exists with latest Tumblweed snapshot and kernel 5.18.9-1-default.
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c6
--- Comment #6 from Takashi Iwai tiwai@suse.com --- (In reply to Michael Hirmke from comment #2)
(In reply to Takashi Iwai from comment #1)
When you boot with the previous kernel, does the message disappear? Please give the full dmesg output and the hwinfo output.
"Starting with the Tumbleweed snapshot installed on June 7th" - so this error exists for at least four weeks and a few kernels now.
Then please report at the next time earlier. Delaying the report makes the debugging much harder in general.
You can check which 5.17.x kernel from my OBS home:tiwai:kernel:5.17 repo. It'd be good to know whether the last 5.17.x shows the same issue or not.
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c7
--- Comment #7 from Michael Hirmke opensuse@mike.franken.de --- (In reply to Takashi Iwai from comment #6)
(In reply to Michael Hirmke from comment #2)
(In reply to Takashi Iwai from comment #1)
When you boot with the previous kernel, does the message disappear? Please give the full dmesg output and the hwinfo output.
"Starting with the Tumbleweed snapshot installed on June 7th" - so this error exists for at least four weeks and a few kernels now.
Then please report at the next time earlier. Delaying the report makes the debugging much harder in general.
If would have done that, if I had seen the error in my log earlier. But I had a long stay in hospital, where I had limited possibilities to access the log.
You can check which 5.17.x kernel from my OBS home:tiwai:kernel:5.17 repo. It'd be good to know whether the last 5.17.x shows the same issue or not.
I'll try. Thx!
https://bugzilla.suse.com/show_bug.cgi?id=1201121 https://bugzilla.suse.com/show_bug.cgi?id=1201121#c8
Michael Hirmke opensuse@mike.franken.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #8 from Michael Hirmke opensuse@mike.franken.de --- Problem vanished.