Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2023-03-08 Thread Diederik de Haas
On Wednesday, 8 March 2023 15:49:03 CET Cyril Brulebois wrote: > This is definitely a blocking issue for booting on both Pi 4 (SD card) > and CM4 (SD card or internal eMMC). That's also seen with v6.1.15 > (annotating accordingly) and v6.2 (not annotating as we have no such > package in the

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2023-03-08 Thread Cyril Brulebois
Control: tag -1 fixed-upstream Control: found -1 6.1.15-1 Hi Bjørn and Hank, Bjørn Mork (2022-09-13): > Hank Barta writes: > > > ** Kernel log: > > [ 723.735217] mmc0: sdhci: Timeout: 0x | Int stat: 0x00018000 > > [ 723.741743] mmc0: sdhci: Int enab: 0x00ff1003 | Sig enab:

Bug#1019700: Info received (Fwd: Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.)

2023-02-19 Thread Cyril Brulebois
Cyril Brulebois (2023-02-19): > FWIW bisecting this issue with a CM4 (and eMMC, no external storage) has > been on my todo list for a long while… but results seem consistent with > my (now) vague recollection: regression in the late 5.1X versions. Sorry, that was with external storage, swapping

Bug#1019700: Info received (Fwd: Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.)

2023-02-19 Thread Cyril Brulebois
Hi, Hank Barta (2022-09-22): > I've gone through "git bisect" on the repo and results are at > https://paste.debian.net/1254605/ > > Each candidate was tested with 6 reboots (including 3 that involved power > cycling.) > > There were four stages that did not build and at which I executed 'git

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2022-12-07 Thread Hank Barta
Hi Diederik, This may not be the same bug. The one you referenced was provoked when the SD card slot was empty and could be suppressed by putting a card in the slot. Also that bug was fixed and the work around was no longer necessary. The one I experienced could happen with the SD card in place

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2022-12-06 Thread Diederik de Haas
Control: tag -1 moreinfo Hi Hank, On Tuesday, 13 September 2022 17:48:22 CET Hank Barta wrote: > Package: src:linux > Version: 5.19.6-1 > >* What led up to the situation? > > Apparent inability to initialize/connect to the SD card H/W. This leads to > the message below that is repeated

Bug#1019700: Info received (Fwd: Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.)

2022-09-22 Thread Hank Barta
I've gone through "git bisect" on the repo and results are at https://paste.debian.net/1254605/ Each candidate was tested with 6 reboots (including 3 that involved power cycling.) There were four stages that did not build and at which I executed 'git bisect skip' to get a buildable candidate.

Bug#1019700: Fwd: Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2022-09-13 Thread Hank Barta
-- Forwarded message - From: Hank Barta Date: Tue, Sep 13, 2022 at 12:54 PM Subject: Re: Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt. To: Bjørn Mork Hi Bjørn, Many thanks for the prompt reply. In the mean time I have done the following: * Reimaged my SD card

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2022-09-13 Thread Bjørn Mork
Hank Barta writes: > ** Kernel log: > [ 723.735217] mmc0: sdhci: Timeout: 0x | Int stat: 0x00018000 > [ 723.741743] mmc0: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003 > [ 723.748270] mmc0: sdhci: ACmd stat: 0x | Slot int: 0x0001 > [ 723.754797] mmc0: sdhci: Caps:

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2022-09-13 Thread Hank Barta
Behavior not seen before - panic during boot. https://photos.app.goo.gl/txcEsUCJuqMGmK1K6 -- Beautiful Sunny Winfield

Bug#1019700: mmc0: Timeout waiting for hardware cmd interrupt.

2022-09-13 Thread Hank Barta
Package: src:linux Version: 5.19.6-1 Severity: important X-Debbugs-Cc: hba...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Apparent inability to initialize/connect to the SD card H/W. This leads to