[Bug 1210639] New: Kernel 6.2+ fails to boot on Intel Atom x5-Z8300
http://bugzilla.suse.com/show_bug.cgi?id=1210639 Bug ID: 1210639 Summary: Kernel 6.2+ fails to boot on Intel Atom x5-Z8300 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: filippo.bonazzi@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Ever since the update to kernel 6.2 my MicroOS Desktop install on an old Intel Atom x5-Z8300 netbook fails to boot. It was working fine up to kernels 6.1.X. This is what I see at boot: [16.358810][ T587] atomisp-isp2 0000:00:03.0: atomisp: Error -2 while requesting firmware shisp_2401a0_v21.bin ^ this line was present at boot on older kernels too, but it still worked [16.414042][ T587] atomisp-isp2 0000:00:03.0: IUNIT power-off timeout. [16.414108][ T587] atomisp-isp2 0000:00:03.0: Failed to switch off ISP And it just freezes there. Sometimes I've also seen a line at the end such as this one: [...] watchdog: BUG: soft lockup - CPU#... stuck for ...s! but this line is not showing up right now that I'm trying to report it. This appears to be the same bug that someone else reported for Ubuntu https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015794 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |filippo.bonazzi@suse.com, | |tiwai@suse.com Flags| |needinfo?(filippo.bonazzi@s | |use.com) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Could you try to boot with blacklisting the atomisp driver? Pass module_blacklist=atomisp boot option. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c2 --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Also, please give the hwinfo and dmesg outputs from the previous working kernel. If the blacklisting worked, give the hwinfo and dmesg outputs from there, too. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c3 --- Comment #3 from Filippo Bonazzi <filippo.bonazzi@suse.com> --- Created attachment 866400 --> http://bugzilla.suse.com/attachment.cgi?id=866400&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c4 Filippo Bonazzi <filippo.bonazzi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(filippo.bonazzi@s | |use.com) | --- Comment #4 from Filippo Bonazzi <filippo.bonazzi@suse.com> --- Blacklisting the module made the system boot. Here are the hwinfo and dmesg outputs. There are some more boot errors that I had not seen previously (ov2722). -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c5 --- Comment #5 from Filippo Bonazzi <filippo.bonazzi@suse.com> --- Created attachment 866401 --> http://bugzilla.suse.com/attachment.cgi?id=866401&action=edit hwinfo -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- OK, then could you try to load atomisp module manually on the running 6.2 kernel? I guess you'll get the crash, but you might have a better chance to get the Oops. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c7 --- Comment #7 from Filippo Bonazzi <filippo.bonazzi@suse.com> --- $ sudo modprobe atomisp modprobe: ERROR: could not insert 'atomisp': Operation not permitted -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c8 --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- I guess it's because you're using MicroOS. IIRC, you need to fiddle with the temporary rw-mount via the transaction shell for allowing such operations. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c9 --- Comment #9 from Filippo Bonazzi <filippo.bonazzi@suse.com> --- I am physically away from that system now, so I'll have to retry in a few days/weeks. Could it also be secure boot? In the interest of having a working system, can I then just blacklist atomisp permanently and run with it until a real fix is found (if ever)? This is a hobby system so no big deal. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c10 --- Comment #10 from Takashi Iwai <tiwai@suse.com> --- (In reply to Filippo Bonazzi from comment #9)
I am physically away from that system now, so I'll have to retry in a few days/weeks. Could it also be secure boot?
I suspect rather the transactional update. Of course, it'd be better to turn off Secure Boot; otherwise it'll become difficult to test a new test kernel.
In the interest of having a working system, can I then just blacklist atomisp permanently and run with it until a real fix is found (if ever)? This is a hobby system so no big deal.
Sure, that'll work. The atomisp driver has been often broken, and I don't think you need it at all. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1210639 http://bugzilla.suse.com/show_bug.cgi?id=1210639#c11 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(filippo.bonazzi@s | |use.com) --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- In anyway, please try the 6.3 kernel (now available in OBS Kernel:stable repo for non-SecureBoot environment). If this still shows the problem, we'll need to report this to the upstream. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com