|
Bugzilla – Full Text Bug Listing |
| Summary: | System crashes during boot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Axel Keller <axel.keller> |
| Component: | Kernel | Assignee: | Ivan Ivanov <ivan.ivanov> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | axel.keller, ivan.ivanov, mbrugger, patrik.jakobsson, stefan.wahren, tiwai |
| Version: | Leap 15.3 | ||
| Target Milestone: | --- | ||
| Hardware: | aarch64 | ||
| OS: | openSUSE Leap 15.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Update list
Log with monitor Log without monitor |
||
Maybe same as bsc#1198484 "Regression in kernel update 5.3.18-150300.59.60.4" Hi, please, could you boot without monitor attached to device. Wait, let say 30 seconds, ssh to it and run dmesg -w and then plug the monitor. Then attach the whole log here. Thanks! Possibly a duplicate of bsc#1198534 I don't think that it is a duplicate of bsc#1198534, because the boot doesn't reach the login page. Therefore a ssh command cannot work. (In reply to Axel Keller from comment #4) > I don't think that it is a duplicate of bsc#1198534, because the boot > doesn't reach the login page. Therefore a ssh command cannot work. Yes, perhaps you're right. You can try to add the following to the kernel command line: modprobe.blacklist=vc4 If that works you might be hitting the bug in bsc#1198942 There are few VC4 related issues. I believe better match is bsc#(In reply to Axel Keller from comment #4) > I don't think that it is a duplicate of bsc#1198534, because the boot > doesn't reach the login page. Therefore a ssh command cannot work. Hm, have you checked? Login page and SSHd are different processes. Please, try what was described in comment#2. If this doesn't work try disabling vc4 driver as described by Patrik. (In reply to Patrik Jakobsson from comment #5) > (In reply to Axel Keller from comment #4) > > I don't think that it is a duplicate of bsc#1198534, because the boot > > doesn't reach the login page. Therefore a ssh command cannot work. > > Yes, perhaps you're right. > > You can try to add the following to the kernel command line: > modprobe.blacklist=vc4 > > If that works you might be hitting the bug in bsc#1198942 I tried this with the last published version openSUSE-Leap-15.3-ARM-KDE-raspberrypi.aarch64-2022.03.04-Build9.449.raw (It was not easy for me to figure out where and how the command line has to be extended during boot!) With this extension the system comes up, the login page works ... I'm wondering that a system is published which wasn't tested obviously. Created attachment 858534 [details]
Log with monitor
Created attachment 858535 [details]
Log without monitor
(In reply to Ivan Ivanov from comment #6) > There are few VC4 related issues. I believe better match is bsc#(In reply to > Axel Keller from comment #4) > > I don't think that it is a duplicate of bsc#1198534, because the boot > > doesn't reach the login page. Therefore a ssh command cannot work. > > Hm, have you checked? Login page and SSHd are different processes. > > Please, try what was described in comment#2. If this doesn't work > try disabling vc4 driver as described by Patrik. This I can only test with the previous version openSUSE-Leap-15.3-ARM-KDE-raspberrypi.aarch64-2021.05.31-Build9.201.raw because after an update the boot hangs totally. I'm not quite sure how to boot and to login without a monitor!? A ssh command doesn't work without login. So I managed it blind. See attachments. (In reply to Axel Keller from comment #10) > > I'm not quite sure how to boot and to login without a monitor!? A ssh > command doesn't work without login. So I managed it blind. See attachments. The idea is to use another computer from which you could ssh to RPi. So even without monitor you can login to device and watch dmesg output. Hi, yesterday i noticed a regression in current kernel mainline tree and it seems that the offending patch was already backported to openSuSE: https://lore.kernel.org/all/20220222140732.253819-1-maxime@cerno.tech/ This patch is broken and should be dropped. I already send a bugfix: https://marc.info/?l=linux-clk&m=165117066630375&w=2 Thanks, I noticed your fix, but it didn't help. (In reply to Ivan Ivanov from comment #13) > Thanks, I noticed your fix, but it didn't help. It comes as little surprise... Look at the vc4 problem WORKAROUND On the ssd-card (ROOT partition) add to /etc/modprobe.d/50-blacklist.conf: blacklist vc4 This enables correct booting. (In reply to Axel Keller from comment #14) > (In reply to Ivan Ivanov from comment #13) > > Thanks, I noticed your fix, but it didn't help. > > It comes as little surprise... > Look at the vc4 problem My reply was about Stefan Wahren comment#12. Anyway, it looks like you have hit bsc#1198534. Please, see my comment#10 in bsc#1198534. I am closing this as duplicate. Thanks! *** This bug has been marked as a duplicate of bug 1198534 *** |
Created attachment 858183 [details] Update list After updating Leap 15.3 on a Raspberry PI4 the system cannot be booted again (black screen) Also after a fresh installation of openSUSE-Leap-15.3-ARM-KDE-raspberrypi.aarch64-2022.03.04-Build9.449 and updating 18 packages directly (second update), the following boot will crash. The problem is the 'Security update for the Linux kernel' !!! (see attachment) Updating the kernel of Leap 15.3 on a raspberry PI4 will destroy any system!!!