Bug 1226302

Summary: Leap 15.6 cannot boot up successfully on RPi 4
Product: [openSUSE] openSUSE Distribution Reporter: Zaoliang Luo <zluo>
Component: InstallationAssignee: openSUSE Kernel Bugs <kernel-bugs>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: arm-bugs, ddavis, ivan.ivanov, kanderssen, tiwai, zluo
Version: Leap 15.6   
Target Milestone: ---   
Hardware: aarch64   
OS: openSUSE Leap 15.5   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: boot output
boot output
boot output

Description Zaoliang Luo 2024-06-13 15:17:29 UTC
compared with https://openqa.opensuse.org/tests/4268701 and I used openSUSE-Leap-15.6-ARM-JeOS-raspberrypi.aarch64-2024.05.03-Build13.251.raw.xz to install Leap 15.6 on my RPi 4 model B.


it starts up with Grub menu and later I got black screen only, no signal output to display.

I tried this with various SD cards and 2 USB cards, Leap has no chance to reach to login prompt.
Comment 1 Knut Alejandro Anderssen González 2024-06-14 08:38:11 UTC
Assigning it to kernel as looks it is not related to the installer at all.

In Slack channel it was also mentioned that could be related to (https://bugzilla.suse.com/show_bug.cgi?id=1225352)
Comment 2 Ivan Ivanov 2024-06-17 07:40:43 UTC
Hi Zaoliang Luo, could you attach serial console to device and 
capture boot log? Or even if you don't see login promt on display
could you try to SSH to device?
Comment 3 Zaoliang Luo 2024-06-17 08:46:50 UTC
Created attachment 875513 [details]
boot output
Comment 4 Zaoliang Luo 2024-06-17 08:49:25 UTC
(In reply to Ivan Ivanov from comment #2)
> Hi Zaoliang Luo, could you attach serial console to device and 
> capture boot log? Or even if you don't see login promt on display
> could you try to SSH to device?

seriously? ssh to device? 

It cannot boot up to login prompt. The system is not ready yet, no networking etc at all.

Please see attached serial console output from booting to the stage where it stopped.
Comment 5 Ivan Ivanov 2024-06-18 07:01:16 UTC
Yes, seriously. "Login prompt" and network setup are runing in parallel.
From serial log I see that system has switched from initrd to main rootfs
and the serial log breaks.
Comment 6 Ivan Ivanov 2024-06-18 07:11:13 UTC
I am asking because latest [1] image is working fine on my RPi4B.

I am little bit confused from where [2] image is comming and why build 
number is higher than officially published here [3] and what is the differnce
between JeOS and Minimal 

[1] openSUSE-Leap-15.6-Minimal-Image.aarch64-15.6.0-RaspberryPi-Build13.236.raw.xz
[2] openSUSE-Leap-15.6-ARM-JeOS-raspberrypi.aarch64-2024.05.03-Build13.251.raw.xz 
[3] https://download.opensuse.org/distribution/leap/15.6/appliances/
Comment 7 Zaoliang Luo 2024-06-18 07:19:53 UTC
(In reply to Ivan Ivanov from comment #6)
> I am asking because latest [1] image is working fine on my RPi4B.
> 
> I am little bit confused from where [2] image is comming and why build 
> number is higher than officially published here [3] and what is the differnce
> between JeOS and Minimal 
> 
> [1]
> openSUSE-Leap-15.6-Minimal-Image.aarch64-15.6.0-RaspberryPi-Build13.236.raw.
> xz
> [2]
> openSUSE-Leap-15.6-ARM-JeOS-raspberrypi.aarch64-2024.05.03-Build13.251.raw.
> xz 
> [3] https://download.opensuse.org/distribution/leap/15.6/appliances/

https://openqa.opensuse.org/tests/4268701#downloads

shows the latest build, this is because O3 always uses the newest build, no official released build(at least not yet).

build13.251 is newer than build13.236 of course if you ask me :)
Comment 8 Ivan Ivanov 2024-06-18 07:23:17 UTC
Should I care about 'Minimal' vs 'JoS', genuine question?
Comment 9 Ivan Ivanov 2024-06-18 08:07:03 UTC
I see following in your console log, which do not look right.

---

Starting dracut pre-mount hook...
[    9.017613] dracut-pre-mount[503]: Created symlink /etc/systemd/system/systemd-fsck-root.service → /dev/null.
[   11.988843] dracut-pre-mount[493]: Warning: Requested OEM systemsize exceeds free space on the disk:
[   12.008556] dracut-pre-mount[493]: Warning: Disk won't be re-partitioned !
[   12.024312] dracut-pre-mount[493]: Warning: Requested size(s): root:(keep)
[   12.040318] dracut-pre-mount[493]: Warning: ==> Free Space on disk: 4 MB
---

Could you replace kernel command line, in Grub2 menu, from 
'log_level=3' to 'ignore_loglevel' and add 'earlycon' parameter, please?
Comment 10 Zaoliang Luo 2024-06-18 13:00:38 UTC
(In reply to Ivan Ivanov from comment #9)
> I see following in your console log, which do not look right.
> 
> ---
> 
> Starting dracut pre-mount hook...
> [    9.017613] dracut-pre-mount[503]: Created symlink
> /etc/systemd/system/systemd-fsck-root.service → /dev/null.
> [   11.988843] dracut-pre-mount[493]: Warning: Requested OEM systemsize
> exceeds free space on the disk:
> [   12.008556] dracut-pre-mount[493]: Warning: Disk won't be re-partitioned !
> [   12.024312] dracut-pre-mount[493]: Warning: Requested size(s): root:(keep)
> [   12.040318] dracut-pre-mount[493]: Warning: ==> Free Space on disk: 4 MB
> ---
> 
> Could you replace kernel command line, in Grub2 menu, from 
> 'log_level=3' to 'ignore_loglevel' and add 'earlycon' parameter, please?

please see requested new log.
Comment 11 Zaoliang Luo 2024-06-18 13:01:01 UTC
Created attachment 875553 [details]
boot output
Comment 12 Ivan Ivanov 2024-06-18 14:07:40 UTC
There is something wrong with the filesystems on the card or the card itself.

...
[   14.129083] dracut-pre-mount[488]: Warning: Requested OEM systemsize exceeds free space on the disk:
[   14.148523] dracut-pre-mount[488]: Warning: Disk won't be re-partitioned !
[   14.164265] dracut-pre-mount[488]: Warning: Requested size(s): root:(keep)
[   14.180266] dracut-pre-mount[488]: Warning: ==> Free Space on disk: 4 MB

...
[   26.616826][ T1044] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
...


Could you use another card? 

I tried this image (Build13.251) on my RPi4 and it boot fine.
Comment 13 Zaoliang Luo 2024-06-18 18:35:33 UTC
(In reply to Ivan Ivanov from comment #12)
> There is something wrong with the filesystems on the card or the card itself.
> 
> ...
> [   14.129083] dracut-pre-mount[488]: Warning: Requested OEM systemsize
> exceeds free space on the disk:
> [   14.148523] dracut-pre-mount[488]: Warning: Disk won't be re-partitioned !
> [   14.164265] dracut-pre-mount[488]: Warning: Requested size(s): root:(keep)
> [   14.180266] dracut-pre-mount[488]: Warning: ==> Free Space on disk: 4 MB
> 
> ...
> [   26.616826][ T1044] FAT-fs (mmcblk0p1): Volume was not properly
> unmounted. Some data may be corrupt. Please run fsck.
> ...
> 
> 
> Could you use another card? 
> 
> I tried this image (Build13.251) on my RPi4 and it boot fine.

I tried with 2 different SD cards, again and again. Same issue on my device RPi 4 model B.

Now I tried with newer image: https://openqa.opensuse.org/tests/4268701/asset/hdd/openSUSE-Leap-15.6-ARM-JeOS-raspberrypi.aarch64-2024.05.03-Build13.251.raw.xz

I found call trace in console log, please check at end of attached log.

Which RPi 4 device do you use?

I tried also with RPi 400, same issue with booting.
Comment 14 Zaoliang Luo 2024-06-18 18:35:53 UTC
Created attachment 875561 [details]
boot output
Comment 15 Zaoliang Luo 2024-06-18 18:57:31 UTC
now I found the cause of this issue. comparing with Tumbleweed boot I got warning about low voltage. The adapter used might be broken, so I use a different one and Leap can boots up.