zbox ci323 sdhci_pci0-slot0 issue

[tortellini]

Reaching out to group since this is a new box and no issues booting and using; but, giving the following error (repeatedly during boot up; but, then goes away):

No major issues running opnsense 16.1.x. 

However, it is noticeable slower to upgrade from 16.1.x to 16.1.x+1 for example.

On zbox 321 for example, takes about 5 minutes for entire process to upgrade. on this new box, about 30 minutes. all settings are same.

seems like freebsd drives with the SD card reader.

sdhci_pci0-slot0:  Controller timeout
sdhci_pci0-slot0: ============== REGISTER DUMP ==============
sdhci_pci0-slot0: Sys addr: 0x00000000 | Version:  0x00001002
sdhci_pci0-slot0: Blk size: 0x00000000 | Blk cnt:  0x00000000
sdhci_pci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000000
sdhci_pci0-slot0: Present:  0x1fff0001 | Host ctl: 0x00000001
sdhci_pci0-slot0: Power:    0x00000000 | Blk gap:  0x00000080
sdhci_pci0-slot0: Wake-up:  0x00000000 | Clock:    0x0000fa07
sdhci_pci0-slot0: Timeout:  0x00000000 | Int stat: 0x00000000
sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb
sdhci_pci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000
sdhci_pci0-slot0: Caps:     0x446cc8b2 | Max curr: 0x00000000
sdhci_pci0-slot0: ===========================================

[franco]

It sounds like a hardware issue triggered by high IO load. Can you reach out to the manufacturer?

You could also try USB boot to see if that makes a difference (nano images work on USB too).

[brad]

I get the following 16 times before it eventually times out and continues to boot.  The Zotac Zbox is a great little machine and I hope the team at OPNSense can get it fully functional with its Intel Wifi card which is recognized "wlan: mac acl policy registered".  Any ideas on this sdhci controller timeout?

sdhci_pci0-slot0:  Controller timeout
sdhci_pci0-slot0: ============== REGISTER DUMP ==============
sdhci_pci0-slot0: Sys addr: 0x00000000 | Version:  0x00001002
sdhci_pci0-slot0: Blk size: 0x00000000 | Blk cnt:  0x00000000
sdhci_pci0-slot0: Argument: 0x00000000 | Trn mode: 0x00000000
sdhci_pci0-slot0: Present:  0x1fff0001 | Host ctl: 0x00000001
sdhci_pci0-slot0: Power:    0x00000000 | Blk gap:  0x00000080
sdhci_pci0-slot0: Wake-up:  0x00000000 | Clock:    0x0000fa07
sdhci_pci0-slot0: Timeout:  0x00000000 | Int stat: 0x00000000
sdhci_pci0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00fb
sdhci_pci0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000
sdhci_pci0-slot0: Caps:     0x446cc8b2 | Max curr: 0x00000000
sdhci_pci0-slot0: ===========================================

[brad]

Solved it.  Went into BIOS and shutdown Legacy USB support, USB Mass Storage Driver Support, Port 60/64 Emulation, turned off SATA port 0.  I rebooted and it came up just great.  I turned everything back on in the BIOS and it still continues to come up just great.

[brad]

My bad, when you are in Legacy boot mode, this fails.  You need to be in UEFI Win 8.x or UEFI Win 7.x.

[the-mk]

Confirmed on 17.1.8...
when switching from legacy to UEFI Win 8.x, this message went away (changing USB settings in BIOS did not affect the message).
but if you turned off the virtual terminal driver (system>settings>administration>console driver), the output on the screen stops at determining the screenresolution (?? just saw some numbers that match my screen resolution...), but booting continues and you can access the firewall via web...
when turned on, it looks good!