Re: [PATCH] firmware/raspberrypi: raise timeout to 3s
From: Stefan Wahren
Date: Fri May 16 2025 - 07:17:53 EST
Am 16.05.25 um 00:27 schrieb Etienne Buira:
Hi Stefan
On Thu, May 15, 2025 at 07:48:04PM +0200, Stefan Wahren wrote:
Hi Etienne,
Am 15.05.25 um 13:48 schrieb Etienne Buira:
On Thu, May 15, 2025 at 12:31:38PM +0200, Stefan Wahren wrote:
Am 15.05.25 um 11:44 schrieb Etienne Buira:
Hi Stefan, and thank you for your interest.
On Thu, May 15, 2025 at 09:42:43AM +0200, Stefan Wahren wrote:
Hi Etienne,
Am 15.05.25 um 08:41 schrieb Etienne Buira:
On Wed, May 14, 2025 at 06:20:32PM +0200, Stefan Wahren wrote:
Hi Etienne,
Am 12.05.25 um 18:30 schrieb Etienne Buira:
../..
Out of curiosity and because i never saw this issue, could you please
provide more details?
There is nothing connected to HDMI 0 & 1 ?
Which firmware version are you running?
Please provide the dmesg output, so we can extract the firmware version.
Firmware version is 2025-02-17T20:03:07, i also attach the full gzipped
dmesg, as long as a patch of extra traces used.
I did not specifically test other firmware versions for the timeout
issue (but i did for video output).
Thanks, i'll try to reproduce.
Sorry, i forgot but is this reproducible with a recent stable 6.12.x kernel?
Just reproduced with pristine 6.12.28.
okay, i've update the firmware on my older Raspberry Pi 4 to the same
version as yours. But even with your configuration i don't see this kind
of fallout. So I think we shouldn't apply this patch until we really
know what's going on.
Ok, thank you, did you make sure a powered hdmi sink were connected? I
noticed there is no timeout if no hdmi is plugged (but there were when
monitor were powered off, maybe specific to my monitor).
Yes, HDMI monitor was connected to HDMI 0 and powered on. Raspberry Pi
OS started as expected.
The fact that your SDIO interface triggers a warning, which I also don't
get let me think this is not just related to HDMI interface.
[ 3.603736] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 3.603739] mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00009902
[ 3.646852] mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
[ 3.646856] mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[ 3.646859] mmc0: sdhci: Present: 0x01ff0001 | Host ctl: 0x00000000
[ 3.665697] mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000000
[ 3.672214] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x00003947
[ 3.678736] mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
[ 3.685254] mmc0: sdhci: Int enab: 0x00ff0003 | Sig enab: 0x00ff0003
[ 3.685257] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[ 3.685260] mmc0: sdhci: Caps: 0x00000000 | Caps_1: 0x00000000
[ 3.712672] mmc0: sdhci: Cmd: 0x00000000 | Max curr: 0x00000001
[ 3.719186] mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
[ 3.725708] mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
[ 3.732230] mmc0: sdhci: Host ctl2: 0x00000000
[ 3.736724] mmc0: sdhci: ============================================
[ 3.819205] mmc0: new high speed SDIO card at address 0001
You don't have another Raspberry Pi 4 by any chance?
No, i don't.
Another cause might be the toolchain. Currently I use a not so fresh gcc
11.3.1 from Linaro.
Previous tries were cross built. I tried a native build with (Gentoo
packages) gcc 14.2.1_p20241221, binutils 2.44, and glibc 2.40-r8; but
got same result.
Will do a software upgrade overnight to try with more up to date build
system.
I will try to update my toolchain, but this will take some time.
Except of this, I noticed that your configuration doesn't enable
DWC2_DUAL_ROLE and the LEDS_TRIGGER.
I have no use of them (and i have a lot of things to disable, but i
prefer to do that starting with a working system).
I this case you can disable DWC2 completely, because USB host is
provided by xhci driver. LEDS_TRIGGER is used for the ACT LED as heartbeat.
Regards.