I encountered the same issue with both 4.14 and 4.19 kernels. During and after boot there is a continuous stream of:
------------[ cut here ]------------ WARNING: CPU: 1 PID: 3908 at drivers/mmc/core/core.c:351 mmc_start_request+0xbc/0xc8 Modules linked in: btsdio(+) bluetooth ecdh_generic brcmfmac brcmutil cfg80211 uio_pdrv_genirq uio 8021q garp stp mrp llc iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter cmemk(O) spidev ip_tables x_tables CPU: 1 PID: 3908 Comm: irq/246-brcmf_o Tainted: G O 4.19.79-ti-rt-r30 #1stretch Hardware name: Generic DRA74X (Flattened Device Tree) [<c0114384>] (unwind_backtrace) from [<c010e4a0>] (show_stack+0x20/0x24) [<c010e4a0>] (show_stack) from [<c0d6a754>] (dump_stack+0x80/0x94) [<c0d6a754>] (dump_stack) from [<c013d084>] (__warn+0x104/0x11c) [<c013d084>] (__warn) from [<c013d1d4>] (warn_slowpath_null+0x50/0x58) [<c013d1d4>] (warn_slowpath_null) from [<c0aed7a0>] (mmc_start_request+0xbc/0xc8) [<c0aed7a0>] (mmc_start_request) from [<c0aed820>] (mmc_wait_for_req+0x74/0xe0) [<c0aed820>] (mmc_wait_for_req) from [<c0afa5bc>] (mmc_io_rw_extended+0x26c/0x32c) [<c0afa5bc>] (mmc_io_rw_extended) from [<c0afbf48>] (sdio_io_rw_ext_helper+0x14c/0x1c0) [<c0afbf48>] (sdio_io_rw_ext_helper) from [<c0afc090>] (sdio_readl+0x40/0x60) [<c0afc090>] (sdio_readl) from [<bf413e9c>] (brcmf_sdiod_request_data+0x150/0x1bc [brcmfmac]) [<bf413e9c>] (brcmf_sdiod_request_data [brcmfmac]) from [<bf414308>] (brcmf_sdiod_regrw_helper+0x8c/0x184 [brcmfmac]) [<bf414308>] (brcmf_sdiod_regrw_helper [brcmfmac]) from [<bf415194>] (brcmf_sdiod_regrl+0x88/0x94 [brcmfmac]) [<bf415194>] (brcmf_sdiod_regrl [brcmfmac]) from [<bf40e1c4>] (brcmf_sdio_intr_rstatus+0x50/0xe4 [brcmfmac]) [<bf40e1c4>] (brcmf_sdio_intr_rstatus [brcmfmac]) from [<bf40fea4>] (brcmf_sdio_isr+0x80/0xec [brcmfmac]) [<bf40fea4>] (brcmf_sdio_isr [brcmfmac]) from [<bf413d44>] (brcmf_sdiod_oob_irqhandler+0x3c/0x44 [brcmfmac]) [<bf413d44>] (brcmf_sdiod_oob_irqhandler [brcmfmac]) from [<c01b4a20>] (irq_forced_thread_fn+0x30/0xac) [<c01b4a20>] (irq_forced_thread_fn) from [<c01b4e18>] (irq_thread+0x138/0x22c) [<c01b4e18>] (irq_thread) from [<c01624b0>] (kthread+0x140/0x170) [<c01624b0>] (kthread) from [<c01010f0>] (ret_from_fork+0x14/0x24) Exception stack(0xcd80bfb0 to 0xcd80bff8) bfa0: 00000000 00000000 00000000 00000000 bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 ---[ end trace 0000000000000002 ]--- ------------[ cut here ]------------ which eventually leads to the other dump reported and console lock ups. The issue seems to be caused by brcmfmac. That driver may not be claiming the host using mmc_claim_host() as required. I ran: sudo sh -c 'echo "blacklist brcmfmac" > /etc/modprobe.d/brcmfmac-blacklist.conf' to disable loading the brcmfmac driver and the issue went away. HTH El jueves, 26 de septiembre de 2019, 11:17:14 (UTC+2), Bas de Bruijn escribió: > > > > On Tuesday, September 24, 2019 at 9:23:16 PM UTC+2, RobertCNelson wrote: >> >> On Tue, Sep 24, 2019 at 2:03 PM Bas de Bruijn <[email protected]> >> wrote: >> > >> > Hi, >> > >> > I received my BB AI yesterday, and when I arranged a proper USB-C cable >> and Raspberry PI adapter I was discovering the board today. Nice and snappy >> compared to the BB Black and co, like the X15 :) >> > After playing around (coming days) I'm planing to install some programs >> I use on the BB Black to try out. So I'd like to know if there are there >> any known RT kernels to (not) work? >> >> This one should work, it's the same kernel as the default install but >> with the RealTime patch applied and enabled.. >> >> cd /opt/scripts/tools/ >> sudo ./update_kernel.sh --ti-rt-channel --lts-4_14 >> > > Hi Robert, Installing was no problem, however I have trouble connecting to > the board via SSH. After a power down, Cloud9 works, connecting via the > debug connector works up to a point.. > > When connected via cloud9 I can create new terminals, but finding out > about the network (ip addr) for example hangs the (remote/debug) terminal. > > I've got a gist here with the serial debug output during startup: > https://gist.github.com/luminize/9c747b83bbda4c589a0b516edb122b96 > dmesg further periodically shows this: > > [ 242.872671] INFO: task systemd-udevd:494 blocked for more than 120 > seconds. > [ 242.880000] Tainted: G W O 4.14.108-ti-rt-r118 #1 > [ 242.886639] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables > this message. > [ 242.894547] systemd-udevd D 0 494 327 0x00000101 > [ 242.894610] [<c0cfac64>] (__schedule) from [<c0cfb0f0>] > (schedule+0x64/0x108) > [ 242.894644] [<c0cfb0f0>] (schedule) from [<c0cfc9c4>] > (__rt_mutex_slowlock+0xf8/0x184) > [ 242.894678] [<c0cfc9c4>] (__rt_mutex_slowlock) from [<c0cfcb34>] > (rt_mutex_slowlock_locked+0xe4/0x2e0) > [ 242.894712] [<c0cfcb34>] (rt_mutex_slowlock_locked) from [<c0cfcda8>] > (rt_mutex_slowlock.constprop.11+0x78/0xbc) > [ 242.894746] [<c0cfcda8>] (rt_mutex_slowlock.constprop.11) from > [<c0cfd244>] (__rt_mutex_lock_state+0x9c/0xc4) > [ 242.894780] [<c0cfd244>] (__rt_mutex_lock_state) from [<c0cff824>] > (_mutex_lock+0x1c/0x20) > [ 242.894810] [<c0cff824>] (_mutex_lock) from [<c0b88eb0>] > (rtnl_lock+0x20/0x24) > [ 242.894841] [<c0b88eb0>] (rtnl_lock) from [<c0b9a344>] > (dev_ioctl+0x774/0xa28) > [ 242.894875] [<c0b9a344>] (dev_ioctl) from [<c0b50428>] > (sock_ioctl+0x180/0x300) > [ 242.894907] [<c0b50428>] (sock_ioctl) from [<c031e100>] > (do_vfs_ioctl+0xc0/0x94c) > [ 242.894936] [<c031e100>] (do_vfs_ioctl) from [<c031ea08>] > (SyS_ioctl+0x7c/0x8c) > [ 242.894968] [<c031ea08>] (SyS_ioctl) from [<c0108e78>] > (__sys_trace_return+0x0/0x10) > > Best, > Bas > > > >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3df3bffc-cf03-4828-be03-407c097351d6%40googlegroups.com.
