[Bug 1205777] New: Pine64: Intermittent boot errors with "../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x3786d40 from `hd1'."
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 Bug ID: 1205777 Summary: Pine64: Intermittent boot errors with "../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x3786d40 from `hd1'." Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: opensuse_buildservice@ojkastl.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Pine64 (Hardware version is 2016) openSUSE MicroOS (the one based on Tumbleweed) Every once in a while the boot fails after grub2 loaded the kernel and the initrd: ``` Booting `openSUSE MicroOS' Loading Linux 6.0.8-1-default ... Loading initial ramdisk ... error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x3786d40 from `hd1'. Press any key to continue... ``` Rebooting solves the issue most of the times. A normal boot looks like this: ``` Booting `openSUSE MicroOS' Loading Linux 6.0.8-1-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... [ 0.000000][ T0] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000][ T0] Linux version 6.0.8-1-default (geeko@buildhost) (gcc (SUSE Linux) 12.2.1 20221020 [revision 0aaef83351473e8f4eb774f8f999bbe87a4866d7], GNU ld (GNU Binutils; openSUSE) [...] ``` Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c1
--- Comment #1 from Johannes Kastl
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c2
--- Comment #2 from Johannes Kastl
U-Boot 2022.10 (Oct 04 2022 - 00:00:00 +0000) Allwinner Technology
CPU: Allwinner A64 (SUN50I) Model: Pine64+ DRAM: 2 GiB Core: 68 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... OK In: serial Out: serial Err: serial Net: eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 => Typing "reset" reboots the device and suddenly the microSDXC card is found again and the device boots....
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c3
--- Comment #3 from Michal Suchanek
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c4
--- Comment #4 from Johannes Kastl
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c5
--- Comment #5 from Michal Suchanek
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c6
--- Comment #6 from Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c7
--- Comment #7 from Michal Suchanek
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c8
--- Comment #8 from Johannes Kastl
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c9
--- Comment #9 from Johannes Kastl
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c10
--- Comment #10 from Michal Suchanek
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c11
--- Comment #11 from Johannes Kastl
Indeed, the situation is very much similar on rk3399 - the u-boot driver is likely missing a step in initializing the mmc bus or card.
This means there are two problems: - u-boot failing to detect the sdcard it was booted from - grub2 being loaded but failing to detect the root device or boot device or load the kernel or anything like that. The latter one is the one, that I cannot solve even if the u-boot watchdog were working. A grub2 hanging with "Press any key to continue" makes the device unreachable and useless. Any idea how to tackle that? Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c12
--- Comment #12 from Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c13
--- Comment #13 from Johannes Kastl
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c14
--- Comment #14 from Johannes Kastl
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c15
--- Comment #15 from Matthias Brugger
What I fail to understand this far:
The board does not have a SPI flash (as far as I found out, so it needs to read the u-boot code from the sdcard (that for whatever reason is called mmc).
So the steps are: - board resets - board reads from sdcard from some offset - board boots into u-boot - u-boot fails to detect the sdcard OR u-boot is able to start grub, but grub fails to find the root device ("error: ../../grub-core/commands/search.c:296:no such device: e590f1c9-3c90-4d9e-a0df-ff6e17559cf8.") OR grub uses the wrong device ("failure reading sector 0x3786d40 from `hd1'.", which seems to have disappeared now that I removed the USB stick
If u-boot is booted, at least the board itself seems to find the sdcard. But u-boot does not? This would point to a bug in u-boot?
Yes, Grub usese the EFI implementation of U-Boot to access the HW. And if U-Boot access to the SD card is buggy, so will be the access from Grub. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777
http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c16
--- Comment #16 from Johannes Kastl
Yes, Grub usese the EFI implementation of U-Boot to access the HW. And if U-Boot access to the SD card is buggy, so will be the access from Grub.
Aaaah, that explains it. In the meantime Seife's grub workaround allowed the board to build multiple times, but just half an hour ago it dropped into the grub shell. ``` grub > ``` And there it sat waiting for some command... Johannes -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com