Beaglebone Blue Read-Only Filesystem Error

[me661]

Hi,

I recently ordered two (2) BeagleBone Blues from you, and both it seems are dead-on-arrival. While they do boot up, and work when connected via USB, as soon as WiFi is enabled and files are updated in any way, the operating system has a kernel panic and makes the file system read-only.

I have tried the following operating systems/distributions:

• Stock pre-installed (ie. from factory, dated 2017 from memory)
• [AM3358 Debian 10.3 2020-04-06 4GB SD IoT]
• [AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher]
• [Debian 9.5 2018-10-07 4GB eMMC IoT Flasher]
• [Ubuntu 18.04.4]

I have tried the following power supplies:

• Micro USB from BBB to Host PC (two different cables)
  

• Micro USB to phone charger (USB-A / 15W) and then over wifi only
  

• Micro USB from Official Raspberry Pi Charger (5V 2.5A) and then over wifi only
  

• 12V 5A Switch-Mode PSU
  

I have tried this on both beaglebones and both fail being in a read-only mode. I’ve attached screenshots, as well as dumps from journalctrl, so you can have a look. I am 99% sure this is a hardware issue, as this only occurs when:

1. The WiFi is on and connected to a modem/router
2. Happens on both the internal eMMC card as well as external microSD card (it does not matter)
3. Even happens when you fiddle around with kernel parameters such as vm.min_free_kbytes, which you really shouldn’t have to!!

I’ve also posted here for some guidance: https://groups.google.com/forum/#!msg/beagleboard/qCvgm9Rl50Y/nNOwMrJqAwAJ but as you can see nothing has really helped.

As such I would like a refund for my order for the two BeagleBone blues, and have am only posting here because your colleage from the customer service department, told me to post here.

[Baozhu]

@me661 Is that the same for both boards? Does it boot properly from SD card? Can you send the dmesg log of SD card startup?

[me661]

Yes it’s the same for both boards, I have tested it using:

• internal eMMC (on both)
• 64gb sandisk class 10 A1 microSD Ultra
• Generic 8GB microSD

It’s the same error for all of them (including, as I said above, even with a change in operating system).
This is a hardware fault.

dmesg screenshot:

dmesg text output (I cut the first few lines off, because this site has a 32k character limit and you can’t attach text files):

debian@beaglebone:~$ dmesg
[ … other boot up lines … ]
[ 1.157090] am335x-phy-driver 47401b00.usb-phy: Linked as a consumer to regulator.0
[ 1.160537] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[ 1.160580] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[ 1.160916] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 1.160927] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.160934] usb usb1: Product: MUSB HDRC host driver
[ 1.160941] usb usb1: Manufacturer: Linux 4.19.94-ti-r42 musb-hcd
[ 1.160948] usb usb1: SerialNumber: musb-hdrc.1
[ 1.161760] hub 1-0:1.0: USB hub found
[ 1.161823] hub 1-0:1.0: 1 port detected
[ 1.173710] omap_rtc 44e3e000.rtc: registered as rtc0
[ 1.175023] i2c /dev entries driver
[ 1.178236] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ 1.178808] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
[ 1.183639] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.184299] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[ 1.184637] omap-aes 53500000.aes: will run requests pump with realtime priority
[ 1.187090] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[ 1.190791] hidraw: raw HID events driver © Jiri Kosina
[ 1.197771] gnss: GNSS driver registered with major 242
[ 1.204460] NET: Registered protocol family 10
[ 1.275821] Segment Routing with IPv6
[ 1.276120] mip6: Mobile IPv6
[ 1.276286] NET: Registered protocol family 17
[ 1.276317] can: controller area network core (rev 20170425 abi 9)
[ 1.276416] NET: Registered protocol family 29
[ 1.276500] 8021q: 802.1Q VLAN Support v1.8
[ 1.276578] Key type dns_resolver registered
[ 1.276585] mpls_gso: MPLS GSO support
[ 1.276894] ThumbEE CPU extension supported.
[ 1.276909] Registering SWP/SWPB emulation handler
[ 1.276919] omap_voltage_late_init: Voltage driver support not added
[ 1.285248] registered taskstats version 1
[ 1.285259] Loading compiled-in X.509 certificates
[ 1.285389] zswap: loaded using pool lzo/zbud
[ 1.288876] Btrfs loaded, crc32c=crc32c-generic
[ 1.288988] AppArmor: AppArmor sha1 policy hashing enabled
[ 1.341517] tps6521x_pwrbutton tps65217-pwrbutton: DMA mask not set
[ 1.342368] input: tps65217_pwr_but as /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
[ 1.343319] tps65217 0-0024: TPS65217 ID 0xe version 1.2
[ 1.344336] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.344447] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[ 1.346298] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 400 kHz
[ 1.348116] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
[ 1.352718] cpu cpu0: Linked as a consumer to regulator.4
[ 1.352825] cpu cpu0: Dropping the link to regulator.4
[ 1.353319] cpu cpu0: Linked as a consumer to regulator.4
[ 1.355388] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 1.356861] ALSA device list:
[ 1.356872] No soundcards found.
[ 1.363105] Freeing unused kernel memory: 1024K
[ 1.363828] Run /init as init process
[ 5.997308] EXT4-fs (mmcblk1p1): INFO: recovery required on readonly filesystem
[ 5.997323] EXT4-fs (mmcblk1p1): write access will be enabled during recovery
[ 6.338100] EXT4-fs (mmcblk1p1): recovery complete
[ 6.341463] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
[ 6.858452] systemd[1]: System time before build time, advancing clock.
[ 6.892186] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 6.892941] systemd[1]: Detected architecture arm.
[ 6.911410] systemd[1]: Set hostname to .
[ 8.168566] systemd[1]: /lib/systemd/system/rc_battery_monitor.service:5: PIDFile= references path below legacy directory /var/run/, updating /var/run/rc_battery_monitor.pid → /run/rc_battery_monitor.pid; please update the unit file accordingly.
[ 8.290684] systemd[1]: Listening on fsck to fsckd communication Socket.
[ 8.292351] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 8.293784] systemd[1]: Listening on Journal Audit Socket.
[ 8.293953] systemd[1]: Reached target Remote File Systems.
[ 8.294100] systemd[1]: Reached target Swap.
[ 8.296315] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 9.617789] remoteproc remoteproc0: 4a334000.pru is available
[ 9.617976] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[ 9.621870] remoteproc remoteproc1: 4a338000.pru is available
[ 9.622039] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
[ 9.636278] EXT4-fs (mmcblk1p1): re-mounted. Opts: errors=remount-ro
[ 10.590219] systemd-journald[486]: Received request to flush runtime journal from PID 1
[ 21.713054] using random self ethernet address
[ 21.713073] using random host ethernet address
[ 22.294714] Mass Storage Function, version: 2009/09/11
[ 22.294738] LUN: removable file: (no medium)
[ 22.662779] using random self ethernet address
[ 22.662798] using random host ethernet address
[ 22.888310] usb0: HOST MAC f4:5e:ab:54:70:7a
[ 22.892740] usb0: MAC f4:5e:ab:54:70:79
[ 22.904065] usb1: HOST MAC f4:5e:ab:54:70:7c
[ 22.904508] usb1: MAC f4:5e:ab:54:70:7d
[ 23.156206] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[ 23.358963] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[ 23.396765] configfs-gadget gadget: high-speed config #1: c
[ 23.397097] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[ 23.422772] IPv6: ADDRCONF(NETDEV_CHANGE): usb1: link becomes ready
[ 31.720120] wlan-en-regulator: disabling
[ 46.642444] remoteproc remoteproc2: wkup_m3 is available
[ 46.850053] remoteproc remoteproc2: powering up wkup_m3
[ 46.850086] remoteproc remoteproc2: Booting fw image am335x-pm-firmware.elf, size 217168
[ 46.850553] remoteproc remoteproc2: remote processor wkup_m3 is now up
[ 46.850575] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x193
[ 47.031270] PM: bootloader does not support rtc-only!
[ 52.636340] Bluetooth: Core ver 2.22
[ 52.636574] NET: Registered protocol family 31
[ 52.636582] Bluetooth: HCI device and connection manager initialized
[ 52.636611] Bluetooth: HCI socket layer initialized
[ 52.636624] Bluetooth: L2CAP socket layer initialized
[ 52.636691] Bluetooth: SCO socket layer initialized
[ 52.712120] Bluetooth: HCI UART driver ver 2.3
[ 52.712140] Bluetooth: HCI UART protocol H4 registered
[ 52.712443] Bluetooth: HCI UART protocol LL registered
[ 52.712453] Bluetooth: HCI UART protocol ATH3K registered
[ 52.712585] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 53.640646] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 53.676815] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
[ 53.677205] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 53.677227] cfg80211: failed to load regulatory.db
[ 53.947175] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 53.947191] Bluetooth: BNEP filters: protocol multicast
[ 53.947224] Bluetooth: BNEP socket layer initialized
[ 54.408199] Bluetooth: RFCOMM TTY layer initialized
[ 54.408240] Bluetooth: RFCOMM socket layer initialized
[ 54.408297] Bluetooth: RFCOMM ver 1.11
[ 55.605226] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[ 55.634247] wlcore: loaded
[ 56.201078] wlcore: PHY firmware version: Rev 8.2.0.0.242
[ 56.239431] wlcore: firmware booted (Rev 8.9.0.0.79)
[ 56.255590] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 57.212405] wlan0: authenticate with 10:0d:7f:d8:f2:f0
[ 57.222701] wlan0: send auth to 10:0d:7f:d8:f2:f0 (try 1/3)
[ 57.252683] wlan0: authenticated
[ 57.264083] wlan0: associate with 10:0d:7f:d8:f2:f0 (try 1/3)
[ 57.268423] wlan0: RX AssocResp from 10:0d:7f:d8:f2:f0 (capab=0x411 status=0 aid=5)
[ 57.285542] wlan0: associated
[ 57.414076] cryptd: max_cpu_qlen set to 1000
[ 57.466473] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 57.484755] wlcore: Association completed.
[ 59.504234] IPv6: ADDRCONF(NETDEV_UP): SoftAp0: link is not ready
[ 60.744935] wlcore: down
[ 60.808689] IPv6: ADDRCONF(NETDEV_CHANGE): SoftAp0: link becomes ready
[ 64.427992] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 67.873267] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 67.879454] mmcblk1: recovery failed!
[ 67.884042] print_req_error: I/O error, dev mmcblk1, sector 3417088
[ 68.181333] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 68.187510] mmcblk1: recovery failed!
[ 68.191823] print_req_error: I/O error, dev mmcblk1, sector 5251136
[ 68.198238] EXT4-fs warning (device mmcblk1p1): ext4_end_bio:323: I/O error 10 writing to inode 50466 (offset 0 size 4096 starting block 656393)
[ 68.198257] Buffer I/O error on device mmcblk1p1, logical block 655368
[ 68.204979] JBD2: Detected IO errors while flushing file data on mmcblk1p1-8
[ 68.205037] Aborting journal on device mmcblk1p1-8.
[ 68.216854] EXT4-fs error (device mmcblk1p1) in __ext4_new_inode:933: Readonly filesystem
[ 68.542462] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 68.548707] mmcblk1: recovery failed!
[ 68.552475] print_req_error: I/O error, dev mmcblk1, sector 3416064
[ 68.558869] Buffer I/O error on dev mmcblk1p1, logical block 425984, lost sync page write
[ 68.567226] JBD2: Error -5 detected when updating journal superblock for mmcblk1p1-8.
[ 68.866726] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 68.872902] mmcblk1: recovery failed!
[ 68.876631] print_req_error: I/O error, dev mmcblk1, sector 8192
[ 68.882786] Buffer I/O error on dev mmcblk1p1, logical block 0, lost sync page write
[ 68.891302] EXT4-fs (mmcblk1p1): I/O error while writing superblock
[ 68.897768] EXT4-fs (mmcblk1p1): previous I/O error to superblock detected
[ 68.904877] EXT4-fs error (device mmcblk1p1): ext4_journal_check_start:61: Detected aborted journal
[ 69.204500] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 69.210675] mmcblk1: recovery failed!
[ 69.214400] print_req_error: I/O error, dev mmcblk1, sector 8192
[ 69.220475] Buffer I/O error on dev mmcblk1p1, logical block 0, lost sync page write
[ 69.233284] EXT4-fs (mmcblk1p1): I/O error while writing superblock
[ 69.244414] EXT4-fs (mmcblk1p1): Remounting filesystem read-only
[ 69.250633] EXT4-fs (mmcblk1p1): Remounting filesystem read-only
[ 69.555378] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 69.561574] mmcblk1: recovery failed!
[ 69.565816] print_req_error: I/O error, dev mmcblk1, sector 8192
[ 69.571919] Buffer I/O error on dev mmcblk1p1, logical block 0, lost sync page write
[ 69.580269] EXT4-fs (mmcblk1p1): I/O error while writing superblock
[ 71.508969] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 71.998556] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 81.718815] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 91.627565] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 92.073393] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 97.834305] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_bcon (89, <AValid), retry #1, port1 00000104
[ 97.881694] ------------[ cut here ]------------
[ 97.881757] WARNING: CPU: 0 PID: 1323 at drivers/net/wireless/ti/wlcore/sdio.c:100 wl12xx_sdio_raw_read+0x14c/0x1b0 [wlcore_sdio]
[ 97.881764] Modules linked in: xt_state xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nft_compat aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 rfcomm bnep cfg80211 hci_uart bluetooth ecdh_generic pm33xx wkup_m3_ipc wkup_m3_rproc wlcore_sdio usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether libcomposite uio_pdrv_genirq uio pruss_soc_bus pru_rproc pruss irq_pruss_intc remoteproc virtio virtio_ring spidev
[ 97.881863] CPU: 0 PID: 1323 Comm: irq/85-wl18xx Not tainted 4.19.94-ti-r42 #1buster
[ 97.881868] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 97.881913] [] (unwind_backtrace) from [] (show_stack+0x20/0x24)
[ 97.881938] [] (show_stack) from [] (dump_stack+0x8c/0xa0)
[ 97.881956] [] (dump_stack) from [] (__warn.part.3+0xcc/0xe8)
[ 97.881969] [] (__warn.part.3) from [] (warn_slowpath_null+0x54/0x5c)
[ 97.881987] [] (warn_slowpath_null) from [] (wl12xx_sdio_raw_read+0x14c/0x1b0 [wlcore_sdio])
[ 97.882293] [] (wl12xx_sdio_raw_read [wlcore_sdio]) from [] (wlcore_irq_locked+0x100/0x79c [wlcore])
[ 97.882506] [] (wlcore_irq_locked [wlcore]) from [] (wlcore_irq+0x94/0x188 [wlcore])
[ 97.882616] [] (wlcore_irq [wlcore]) from [] (irq_thread_fn+0x2c/0x88)
[ 97.882632] [] (irq_thread_fn) from [] (irq_thread+0x164/0x234)
[ 97.882643] [] (irq_thread) from [] (kthread+0x16c/0x174)
[ 97.882658] [] (kthread) from [] (ret_from_fork+0x14/0x2c)
[ 97.882665] Exception stack(0xd5411fb0 to 0xd5411ff8)
[ 97.882675] 1fa0: 00000000 00000000 00000000 00000000
[ 97.882686] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 97.882695] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 97.882703] —[ end trace fe58a0b92171d6e9 ]—
[ 97.882721] wl1271_sdio mmc2:0001:2: sdio read failed (-110)
[ 97.888581] ------------[ cut here ]------------
[ 97.888720] WARNING: CPU: 0 PID: 1323 at drivers/net/wireless/ti/wlcore/main.c:808 wl12xx_queue_recovery_work+0x64/0x68 [wlcore]
[ 97.888728] Modules linked in: xt_state xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nft_compat aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 rfcomm bnep cfg80211 hci_uart bluetooth ecdh_generic pm33xx wkup_m3_ipc wkup_m3_rproc wlcore_sdio usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether libcomposite uio_pdrv_genirq uio pruss_soc_bus pru_rproc pruss irq_pruss_intc remoteproc virtio virtio_ring spidev
[ 97.888810] CPU: 0 PID: 1323 Comm: irq/85-wl18xx Tainted: G W 4.19.94-ti-r42 #1buster
[ 97.888816] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 97.888841] [] (unwind_backtrace) from [] (show_stack+0x20/0x24)
[ 97.888860] [] (show_stack) from [] (dump_stack+0x8c/0xa0)
[ 97.888874] [] (dump_stack) from [] (__warn.part.3+0xcc/0xe8)
[ 97.888887] [] (__warn.part.3) from [] (warn_slowpath_null+0x54/0x5c)
[ 97.888999] [] (warn_slowpath_null) from [] (wl12xx_queue_recovery_work+0x64/0x68 [wlcore])
[ 97.889174] [] (wl12xx_queue_recovery_work [wlcore]) from [] (wlcore_irq+0x118/0x188 [wlcore])
[ 97.889272] [] (wlcore_irq [wlcore]) from [] (irq_thread_fn+0x2c/0x88)
[ 97.889285] [] (irq_thread_fn) from [] (irq_thread+0x164/0x234)
[ 97.889296] [] (irq_thread) from [] (kthread+0x16c/0x174)
[ 97.889307] [] (kthread) from [] (ret_from_fork+0x14/0x2c)
[ 97.889314] Exception stack(0xd5411fb0 to 0xd5411ff8)
[ 97.889324] 1fa0: 00000000 00000000 00000000 00000000
[ 97.889334] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 97.889344] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 97.889350] —[ end trace fe58a0b92171d6ea ]—
[ 97.889526] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.79
[ 97.889552] wlcore: down
[ 97.889596] wlcore: down
[ 97.889611] wlcore: down
[ 97.889904] ieee80211 phy0: Hardware restart was requested
[ 97.902412] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <AValid), retry #2, port1 00000104
[ 98.324642] wlcore: PHY firmware version: Rev 8.2.0.0.242
[ 98.372783] wlcore: firmware booted (Rev 8.9.0.0.79)
[ 98.427547] wlcore: Association completed.
[ 98.593981] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <AValid), retry #3, port1 00000104
[ 104.700879] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 110.466611] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 111.269054] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_bcon (88, <AValid), retry #3, port1 0008010c
[ 113.676782] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 115.779535] omap_hsmmc 481d8000.mmc: error -110 requesting status
[ 120.647356] ------------[ cut here ]------------
[ 120.647412] WARNING: CPU: 0 PID: 1457 at drivers/net/wireless/ti/wlcore/sdio.c:145 wl12xx_sdio_raw_write+0x148/0x1b4 [wlcore_sdio]
[ 120.647418] Modules linked in: xt_state xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nft_compat aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 rfcomm bnep cfg80211 hci_uart bluetooth ecdh_generic pm33xx wkup_m3_ipc wkup_m3_rproc wlcore_sdio usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether libcomposite uio_pdrv_genirq uio pruss_soc_bus pru_rproc pruss irq_pruss_intc remoteproc virtio virtio_ring spidev
[ 120.647518] CPU: 0 PID: 1457 Comm: kworker/u2:3 Tainted: G W 4.19.94-ti-r42 #1buster
[ 120.647523] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 120.647813] Workqueue: phy0 wl1271_tx_work [wlcore]
[ 120.647861] [] (unwind_backtrace) from [] (show_stack+0x20/0x24)
[ 120.647887] [] (show_stack) from [] (dump_stack+0x8c/0xa0)
[ 120.647906] [] (dump_stack) from [] (__warn.part.3+0xcc/0xe8)
[ 120.647918] [] (__warn.part.3) from [] (warn_slowpath_null+0x54/0x5c)
[ 120.647938] [] (warn_slowpath_null) from [] (wl12xx_sdio_raw_write+0x148/0x1b4 [wlcore_sdio])
[ 120.648080] [] (wl12xx_sdio_raw_write [wlcore_sdio]) from [] (wlcore_tx_work_locked+0x750/0xf30 [wlcore])
[ 120.648262] [] (wlcore_tx_work_locked [wlcore]) from [] (wl1271_tx_work+0x44/0xc8 [wlcore])
[ 120.648362] [] (wl1271_tx_work [wlcore]) from [] (process_one_work+0x1b4/0x504)
[ 120.648378] [] (process_one_work) from [] (worker_thread+0x60/0x508)
[ 120.648390] [] (worker_thread) from [] (kthread+0x16c/0x174)
[ 120.648403] [] (kthread) from [] (ret_from_fork+0x14/0x2c)
[ 120.648411] Exception stack(0xdc5d9fb0 to 0xdc5d9ff8)
[ 120.648422] 9fa0: 00000000 00000000 00000000 00000000
[ 120.648433] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 120.648442] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 120.648451] —[ end trace fe58a0b92171d6eb ]—
[ 120.648468] wl1271_sdio mmc2:0001:2: sdio write failed (-110)
[ 120.679293] ------------[ cut here ]------------
[ 120.679605] WARNING: CPU: 0 PID: 1457 at drivers/net/wireless/ti/wlcore/main.c:808 wl12xx_queue_recovery_work+0x64/0x68 [wlcore]
[ 120.679615] Modules linked in: xt_state xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nft_compat aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 rfcomm bnep cfg80211 hci_uart bluetooth ecdh_generic pm33xx wkup_m3_ipc wkup_m3_rproc wlcore_sdio usb_f_acm u_serial usb_f_ecm usb_f_mass_storage usb_f_rndis u_ether libcomposite uio_pdrv_genirq uio pruss_soc_bus pru_rproc pruss irq_pruss_intc remoteproc virtio virtio_ring spidev
[ 120.679714] CPU: 0 PID: 1457 Comm: kworker/u2:3 Tainted: G W 4.19.94-ti-r42 #1buster
[ 120.679720] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 120.679846] Workqueue: phy0 wl1271_tx_work [wlcore]
[ 120.679891] [] (unwind_backtrace) from [] (show_stack+0x20/0x24)
[ 120.679916] [] (show_stack) from [] (dump_stack+0x8c/0xa0)
[ 120.679934] [] (dump_stack) from [] (__warn.part.3+0xcc/0xe8)
[ 120.679946] [] (__warn.part.3) from [] (warn_slowpath_null+0x54/0x5c)
[ 120.680057] [] (warn_slowpath_null) from [] (wl12xx_queue_recovery_work+0x64/0x68 [wlcore])
[ 120.680237] [] (wl12xx_queue_recovery_work [wlcore]) from [] (wl1271_tx_work+0xc4/0xc8 [wlcore])
[ 120.680338] [] (wl1271_tx_work [wlcore]) from [] (process_one_work+0x1b4/0x504)
[ 120.680352] [] (process_one_work) from [] (worker_thread+0x60/0x508)
[ 120.680364] [] (worker_thread) from [] (kthread+0x16c/0x174)
[ 120.680377] [] (kthread) from [] (ret_from_fork+0x14/0x2c)
[ 120.680385] Exception stack(0xdc5d9fb0 to 0xdc5d9ff8)
[ 120.680396] 9fa0: 00000000 00000000 00000000 00000000
[ 120.680406] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 120.680416] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 120.680424] —[ end trace fe58a0b92171d6ec ]—
[ 120.687968] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.79
[ 120.688005] wlcore: down
[ 120.688048] wlcore: down
[ 120.688064] wlcore: down
[ 120.689140] ieee80211 phy0: Hardware restart was requested

[Baozhu]

@me661 It seems that there is really something wrong with the hardware. Our after-sales engineer has sent an email to you. Please communicate about relevant after-sales matters in the email.

[Gabriel_C]

I received a BeagleBone Blue about a month and a half ago, around the same time this thread was opened and I have run into the same issues. When using the on-board WiFi capabilities, the kernel panics and reverts to a read-only mode. This issue did not allow me to update or install packages (apt-get) on any OS distribution that I tried. I used both the pre-installed OS, a more updated Debian, as well as Ubuntu 18.04 and still ran into the same issue. Just like @me661 I tested different power supplies.

This happens when the WiFi is enabled and writing to the internal eMMC as well as the microSD card. I believe this to be a hardware issue, perhaps with the batch of BeagleBones that @me661 and I received. I am hoping to get a replacement BeagleBone Blue that does not have this issue or a refund on my order.

Below is a copy of part of the errors I got following an apt-get upgrade on the BeagleBone. No commands, not even dmesg worked afterwords, so this is the best I can seem to get in terms of displaying the issue. This error message is pretty long, so I can also provide more screenshots if this is too abbreviated (new users can only use 1 image per post in this forum). Thanks.

[bmihalik]

We bought two BeagleBone Blue in last two weeks (I had no experience with this card before). Both card had the same problem, but it happened only when I connected BBBlue to the internet via local wifi network, after I connected my PC to BBBlue’s wifi (192.168.8.0) and I tried to access the internet via BBBlue. System dropped same error messages ad described above (this is how I found this page), and remounted the root filesystem as read-only.

After that I tried 5.4LTS kernel, but I got the same problem. Also I couldn’t access I2C peripherals, etc. I changed back to kernel version 4.19.94-ti-rt, but release “-r50”, and seems problem solved.

[elizabeth]

I am also having this problem as described by Gabriel C. How do I fix this problem? Can I reflash the image or is it toast? If it’s toast I want a refund.