Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Assistance reading diagnostics after failure- 3.3

    Scheduled Pinned Locked Moved
    General Discussion
    5
    12
    449
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • oozeBotundefined
      oozeBot @jay_s_uk
      last edited by

      @jay_s_uk grabbing them now

      1 Reply Last reply Reply Quote 0
      • oozeBotundefined
        oozeBot
        last edited by oozeBot

        Here is the relevant section. SD Card failure?

        Aug 16 11:18:25 oozeBot kernel: [188744.509778] mmc1: Timeout waiting for hardware interrupt.
Aug 16 11:18:25 oozeBot kernel: [188744.509850] brcmfmac: mmc_submit_one: CMD53 sg block write failed -110
Aug 16 11:18:25 oozeBot kernel: [188744.509869] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
Aug 16 11:18:25 oozeBot kernel: [188744.510081] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
Aug 16 11:18:25 oozeBot kernel: [188744.511323] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Aug 16 11:18:25 oozeBot kernel: [188744.511338] brcmfmac: brcmf_sdio_rxfail: terminate frame
Aug 16 11:18:25 oozeBot kernel: [188744.512497] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Aug 16 11:18:25 oozeBot kernel: [188744.512512] brcmfmac: brcmf_sdio_rxfail: terminate frame
Aug 16 11:18:25 oozeBot kernel: [188744.512686] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Aug 16 11:18:25 oozeBot kernel: [188744.512714] brcmfmac: brcmf_sdio_rxfail: terminate frame
Aug 16 11:18:25 oozeBot kernel: [188744.512891] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Aug 16 11:18:25 oozeBot kernel: [188744.512905] brcmfmac: brcmf_sdio_rxfail: terminate frame
Aug 16 11:18:27 oozeBot DuetControlServer[1043]: [info] System time has been changed
Aug 16 11:18:27 oozeBot kernel: [188747.069866] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Aug 16 11:18:27 oozeBot kernel: [188747.070224] brcmfmac: brcmf_sdio_readshared: invalid sdpcm_shared address 0x00000000
Aug 16 11:18:27 oozeBot kernel: [188747.070241] brcmfmac: brcmf_sdio_readshared: unable to obtain sdpcm_shared info: rv=-22 (addr=0x0)
Aug 16 11:18:27 oozeBot kernel: [188747.070268] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Aug 16 11:18:27 oozeBot DuetControlServer[1043]: [warn] Controller has been reset
Aug 16 11:18:27 oozeBot DuetControlServer[1043]: [info] Aborted job file
Aug 16 11:18:27 oozeBot DuetControlServer[1043]: [warn] Trigger: Out-of-order reply: ''
Aug 16 11:18:31 oozeBot kernel: [188750.655249] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Aug 16 11:18:31 oozeBot kernel: [188750.655268] brcmfmac: brcmf_sdio_rxfail: terminate frame
Aug 16 11:18:34 oozeBot kernel: [188753.630009] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Aug 16 11:18:34 oozeBot kernel: [188753.630360] brcmfmac: brcmf_sdio_readshared: invalid sdpcm_shared address 0xFFB70048
Aug 16 11:18:34 oozeBot kernel: [188753.630377] brcmfmac: brcmf_sdio_readshared: unable to obtain sdpcm_shared info: rv=-22 (addr=0xffb70048)
Aug 16 11:18:36 oozeBot DuetControlServer[1043]: [info] System time has been changed
Aug 16 11:18:36 oozeBot kernel: [188756.190060] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Aug 16 11:18:36 oozeBot kernel: [188756.190424] brcmfmac: brcmf_sdio_readshared: invalid sdpcm_shared address 0xFFB70048
Aug 16 11:18:36 oozeBot kernel: [188756.190441] brcmfmac: brcmf_sdio_readshared: unable to obtain sdpcm_shared info: rv=-22 (addr=0xffb70048)
Aug 16 11:18:36 oozeBot kernel: [188756.190468] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
Aug 16 11:18:41 oozeBot kernel: [188760.659861] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Aug 16 11:18:41 oozeBot kernel: [188760.659879] brcmfmac: brcmf_sdio_rxfail: terminate frame
Aug 16 11:18:43 oozeBot kernel: [188762.760085] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
Aug 16 11:18:43 oozeBot kernel: [188762.766964] brcmfmac: brcmf_sdiod_ramrw: membytes transfer failed
Aug 16 11:18:43 oozeBot kernel: [188762.766974] brcmfmac: brcmf_sdio_readshared: unable to obtain sdpcm_shared info: rv=-84 (addr=0x20000010)
Aug 16 11:18:43 oozeBot kernel: [188762.767421] brcmfmac: brcmf_sdio_hdparse: HW header checksum error
Aug 16 11:18:43 oozeBot kernel: [188762.767428] brcmfmac: brcmf_sdio_rxfail: terminate frame
Aug 16 11:18:43 oozeBot kernel: [188762.775888] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -52
Aug 16 11:18:43 oozeBot dhcpcd[628]: wlan0: carrier lost
        1 Reply Last reply Reply Quote 0
        • oliofundefined
          oliof
          last edited by

          It's a bit confusing since brcmfmac is a wifi driver.

          <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

          oozeBotundefined 1 Reply Last reply Reply Quote 0
          • oozeBotundefined
            oozeBot @oliof
            last edited by

            @oliof agreed. The RPi did not reboot, we just lost connection to it through DWC for ~30 seconds. Once the connection was restored, the print was canceled. I wonder if the change in System time (line 13) had anything to do with it? That's the first thing reported by DuetControlServer.

            1 Reply Last reply Reply Quote 0
            • oliofundefined
              oliof
              last edited by oliof

              CMD53 is some kind of configuration command for a wifi chip; which is where some error was triggered. This seems to have blocked some subsystem for about 2 seconds, long enough for a realtime system to decide it is in an irrevocable state of de-sync.

              Sleuthing a bit, it could be related to an unfixed issue with the wifi chip and/or driver on the Raspberry Pi which has been around since 2018 ...

              I'd suggest moving to Ethernet if possible.

              <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

              dc42undefined 1 Reply Last reply Reply Quote 3
              • dc42undefined
                dc42 administrators @oliof
                last edited by

                @oliof I think CMD53 actually related to the SD card interface. It looks to me that there was a timeout waiting for an interrupt from the SD card subsystem.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                oliofundefined 1 Reply Last reply Reply Quote 0
                • oozeBotundefined
                  oozeBot
                  last edited by

                  @oozebot said in Assistance reading diagnostics after failure- 3.3:

                  brcmfmac: mmc_submit_one

                  Thank you both. Based on what we are finding, we are starting to think we overtaxed the wifi module with several webcam streams going at once.

                  1 Reply Last reply Reply Quote 0
                  • oliofundefined
                    oliof @dc42
                    last edited by oliof

                    @dc42 I'm confused why the wifi driver does SD card interface management, but that may be the vagaries of integrated electronics. It still seems to be resulting in a failure of the wifi interface twice (Aug 16 11:18:27 oozeBot kernel: [188747.070268] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 and again at 11:18:43).

                    <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                    alankilianundefined 1 Reply Last reply Reply Quote 0
                    • alankilianundefined
                      alankilian @oliof
                      last edited by alankilian

                      @oliof

                      If you look at the driver, it can support WiFi hardware on PCIe or SDIO interfaces.

                      I guess this Raspberry PI has the WiFi hardware attached to an SDIO interface (which is pretty common in the embedded-world)

                      Maybe this BCM43428.

                      SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

                      1 Reply Last reply Reply Quote 0
                      • oliofundefined
                        oliof
                        last edited by

                        on the RPi 3B it seems to be BCM43438 (on RPi4 a BCM4345/6) -- and you're right, they are connected via SDIO interface. I am less confused now.

                        <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA