Nightly: Unexpected kernel BRK exception at EL1
with reference to dwc_otg_hcd_init
#2780
Labels
🐛 bug-report
Something isn't working
platform/raspberrypi
RaspberryPi platform
👍 important
This is an important issue/ticket with high priority
🧠 unstable-snapshot
This ticket references the use of an unsupported unstable snapshot being used.
Milestone
Describe the issue you are experiencing
After upgrading to the latest nightly snapshot version (
3.77.2.20240618
) for the RaspberryPi3, the bootup hangs in an endless loop after the last U-BootStarting kernel...
output.After some investigation it seems the Linux kernel (6.6.31) runs into a
Kernel panic
mentioningUnexpected kernel BRK exception at EL1
and a pc pointing atdwc_otg_hcd_init
. This can be seen by changing the content of/boot/cmdline.txt
toconsole=tty1 loglevel=10
. Then the following kernel panic pops up:As a workaround to get the kernel booted again, the
/boot/config.txt
file can be changed anddtoverlay=dwc2
added so that the DWC2 USB controller support is used instead of the defaultdwc_otg
one.Describe the behavior you expected
The kernel should properly boot up.
Steps to reproduce the issue
/boot/cmdline.txt
and setconsole=tty1 loglevel=10
to see that the system now outputs the above mentiojnedKernel panic
./boot/config.txt
and adddtoverlay=dwc2
and note that now the kernel bootsup properly.What is the version this bug report is based on?
3.77.2.20240618
Which base platform are you running?
rpi3 (RaspberryPi3, ARM64/aarch64)
Which HomeMatic/homematicIP radio module are you using?
RPI-RF-MOD
Anything in the logs that might be useful for us?
Additional information
After some first investigation for the root cause it seems that with the introduction of the latest Buildroot 2024.05 the issue seem to have suddenly appeared. This seems to be related to the GCC v11 => GCC v13 upgrade which this buildroot version introduces. Downgrading GCC v13 to GCC v12 seem to recover/solve that issue point at some GCC related kernel compilation/setup issue.
The text was updated successfully, but these errors were encountered: