SARPI on PI4B: kernel crash on cold boot with 5.4.18 from 08Feb2020
by fgsch370 from LinuxQuestions.org on (#4ZGX0)
Hi,
I recently installed SARPI slackware-current on my new PI4B. I used SARPI from 08Feb2020. Something strange happens on boot and disappears after a while.
The kernel seems to crash in bcm2835_clk_probe. I can only see the crash screen with a backtrace beginning in bcm2835_clk_probe. The rest happens too fast and as there is no USB brought up yet, I have no means to scroll back and see the first message of the crash. I compared the timestamp of the crash with the timestamps of a working bootup and looked for a "bcm2835" in the messages. This way I can guess it happens near bcm-power or in mmc initialization.
What is strange, after approx. 5 minutes, reboot succeeds and works. Stable and for hours. For me it seems that there is a timing parameter set too close to a limit. But what can it be?
It is the first time I use the 5.4.x kernel. With kernels of series 4 no problem arises.
Thanks,
fgsch
I recently installed SARPI slackware-current on my new PI4B. I used SARPI from 08Feb2020. Something strange happens on boot and disappears after a while.
The kernel seems to crash in bcm2835_clk_probe. I can only see the crash screen with a backtrace beginning in bcm2835_clk_probe. The rest happens too fast and as there is no USB brought up yet, I have no means to scroll back and see the first message of the crash. I compared the timestamp of the crash with the timestamps of a working bootup and looked for a "bcm2835" in the messages. This way I can guess it happens near bcm-power or in mmc initialization.
What is strange, after approx. 5 minutes, reboot succeeds and works. Stable and for hours. For me it seems that there is a timing parameter set too close to a limit. But what can it be?
It is the first time I use the 5.4.x kernel. With kernels of series 4 no problem arises.
Thanks,
fgsch