Bugzilla – Bug 1210639
Kernel 6.2+ fails to boot on Intel Atom x5-Z8300
Last modified: 2024-03-24 02:10:11 UTC
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
Could you try to boot with blacklisting the atomisp driver? Pass module_blacklist=atomisp boot option.
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.
Created attachment 866400 [details] dmesg
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).
Created attachment 866401 [details] hwinfo
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.
$ sudo modprobe atomisp modprobe: ERROR: could not insert 'atomisp': Operation not permitted
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.
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.
(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.
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.
Created attachment 872528 [details] dmesg and hwinfo from old and new kernel
I have same problem on openSUSE Tumbleweed (see also https://bugzilla.suse.com/show_bug.cgi?id=1219628 ). When I try "sudo modprobe atomisp", the system just freezes.
*** Bug 1219628 has been marked as a duplicate of this bug. ***
A more interesting part is whether you can get the kernel Oops messages found in the log. With the later modprobe, it's highly possible that the system runs and keeps the dying message. Please check the previous boot log.
Created attachment 872534 [details] log with failed modprobe I used "sudo journalctl -b-1" to obtain the log. Failed modprobe I tried ca. 11:12 and hard rebooted ca. 10 min. later. HTH
(In reply to Vojtech Zeisek from comment #16) > Created attachment 872534 [details] > log with failed modprobe > > I used "sudo journalctl -b-1" to obtain the log. Failed modprobe I tried ca. > 11:12 and hard rebooted ca. 10 min. later. HTH Hm, it doesn't show anything about atomisp unlike the previous report. Didn't you see those messages about the firmware load errors?
> Didn't you see those messages about the firmware load errors? Nothing. As soon as I submit the modprobe command, notebook freezes completely and I can do nothing and see nothing.
OK, thanks. Then it's not easy to get the crash log, and without such info, debugging and fixing the problem is hardly possible. So I decided rather to disable this broken driver from our kernels. It's been broken over a year, and it's a very rarely used device. The next kernel should drop the atomisp driver and you can remove the blacklist later, too.