Regression #14300
closed
Re: ``mmcsd0`` controller timeout/system hang on 1100
0%
Description
[the original issue is closed so I can no longer post to it!?!]
I'm still on 23.01, running my spare SG-1100, and hit the timeout again... I will say it's a little warmer today than it has been recently and about 80° F where the box is located. Still, this might be more evidence that the problem is a software regression and not a hardware issue.
I'll likely wait for 23.05 to be released before I run it.
sdhci_xenon1-slot0: Controller timeout sdhci_xenon1-slot0: ============== REGISTER DUMP ============== sdhci_xenon1-slot0: Sys addr: 0x08097a00 | Version: 0x00000002 sdhci_xenon1-slot0: Blk size: 0x00007200 | Blk cnt: 0x00000005 sdhci_xenon1-slot0: Argument: 0x00617c59 | Trn mode: 0x00000027 sdhci_xenon1-slot0: Present: 0x01e20106 | Host ctl: 0x00000025 sdhci_xenon1-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_xenon1-slot0: Wake-up: 0x00000000 | Clock: 0x00000407 sdhci_xenon1-slot0: Timeout: 0x0000000c | Int stat: 0x00000001 sdhci_xenon1-slot0: Int enab: 0x01ff003b | Sig enab: 0x01ff003a sdhci_xenon1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000 sdhci_xenon1-slot0: Caps: 0x25ec0099 | Caps2: 0x0000af77 sdhci_xenon1-slot0: Max curr: 0x00000000 | ADMA err: 0x00000000 sdhci_xenon1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 sdhci_xenon1-slot0: =========================================== mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout Solaris: WARNING: Pool 'pfSense' has encountered an uncorrectable I/O failure and has been suspended. Solaris: WARNING: Pool 'pfSense' has encountered an uncorrectable I/O failure and has been suspended. Solaris: WARNING: Pool 'pfSense' has encountered an uncorrectable I/O failure and has been suspended.
Related issues
Updated by Kris Phillips over 1 year ago
Typically these messages indicate eMMC controller or storage chip failure. It is unlikely to be a bug. Are you able to reproduce this on more than one 1100 appliance?
Updated by Jim Pingle over 1 year ago
- Status changed from New to Duplicate
The previous issue (#14181) is closed because it's either solved on 23.05 or it's hardware. So either it's already fixed or it's a hardware issue that cannot be fixed, so there is nothing actionable left to do. Additional reports on 23.01 are not necessary. We should have snapshots of 23.05 available soon for testing.
Updated by Jim Pingle over 1 year ago
- Is duplicate of Regression #14181: ``mmcsd0`` controller timeout/system hang on 1100 added