This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM335X: Beaglebone Black PRU - Issue reading ADC in long run

Part Number: PROCESSOR-SDK-AM335X


In Beaglebone Black, The development is made as ADC is disabled by the Linux ARM core. It is initialized and controlled by the PRU. PRU read the analog values continuously in a loop and send to the host program in linux via RPMsg channel using shared memory. We read the analog values continuously around 5 days, then 6th day analog values read as 0. We checked both host program and PRU is working fine. But PRU sends only zero and same zero is read by the host program. We terminated host program as well as PRU and started them again. The result is same. After rebooting the Beaglebone Black, PRU started sending the analog value and same read by the host program in linux. Dont why it stops reading the analog value on the 6th day.
Please suggest solution if any. Thank you for your time and consideration.
Attaching syslog for reference:
Nov 3 17:18:03 bbbdevice kernel: [ 110.682131] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:19:14 bbbdevice kernel: [ 115.074691] IPv6: ADDRCONF(NETDEV_UP): SoftAp0: link is not ready
Jul 23 17:19:14 bbbdevice kernel: [ 115.341990] IPv6: ADDRCONF(NETDEV_CHANGE): SoftAp0: link becomes ready
Jul 23 17:24:00 bbbdevice kernel: [ 401.126242] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:24:00 bbbdevice kernel: [ 401.126264] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 17:24:00 bbbdevice kernel: [ 401.126320] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 17:24:00 bbbdevice kernel: [ 401.126648] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 17:24:00 bbbdevice kernel: [ 401.134738] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 17:24:00 bbbdevice kernel: [ 401.144351] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:24:00 bbbdevice kernel: [ 401.144372] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 17:24:00 bbbdevice kernel: [ 401.158034] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 17:24:00 bbbdevice kernel: [ 401.159143] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:24:00 bbbdevice kernel: [ 401.161133] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 17:24:00 bbbdevice kernel: [ 401.170442] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 17:24:00 bbbdevice kernel: [ 401.170463] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 17:25:56 bbbdevice kernel: [ 516.858054] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:25:56 bbbdevice kernel: [ 516.858074] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 17:25:56 bbbdevice kernel: [ 516.858121] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 17:25:56 bbbdevice kernel: [ 516.858465] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 17:25:56 bbbdevice kernel: [ 516.866585] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 17:25:56 bbbdevice kernel: [ 516.877390] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:25:56 bbbdevice kernel: [ 516.877412] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 17:25:56 bbbdevice kernel: [ 516.892590] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 17:25:56 bbbdevice kernel: [ 516.893987] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:25:56 bbbdevice kernel: [ 516.898092] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 17:25:56 bbbdevice kernel: [ 516.902793] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 17:25:56 bbbdevice kernel: [ 516.902814] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 17:26:20 bbbdevice kernel: [ 541.131577] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 204
Jul 23 17:26:20 bbbdevice kernel: [ 541.133469] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 204
Jul 23 17:26:23 bbbdevice kernel: [ 544.407967] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 23 17:30:47 bbbdevice kernel: [ 808.399390] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:30:47 bbbdevice kernel: [ 808.399411] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 17:30:47 bbbdevice kernel: [ 808.399461] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 17:30:47 bbbdevice kernel: [ 808.399807] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 17:30:47 bbbdevice kernel: [ 808.400638] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 17:30:47 bbbdevice kernel: [ 808.415648] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:30:47 bbbdevice kernel: [ 808.415670] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 17:30:47 bbbdevice kernel: [ 808.436542] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 17:30:47 bbbdevice kernel: [ 808.437770] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:30:47 bbbdevice kernel: [ 808.439981] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 17:30:47 bbbdevice kernel: [ 808.442745] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 17:30:47 bbbdevice kernel: [ 808.442765] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 17:33:13 bbbdevice kernel: [ 954.173638] hrtimer: interrupt took 141875 ns
Jul 23 17:36:39 bbbdevice kernel: [ 1160.601494] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:36:39 bbbdevice kernel: [ 1160.601516] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 17:36:39 bbbdevice kernel: [ 1160.609494] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 17:36:39 bbbdevice kernel: [ 1160.612331] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 17:36:39 bbbdevice kernel: [ 1160.615699] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 17:36:39 bbbdevice kernel: [ 1160.624783] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:36:39 bbbdevice kernel: [ 1160.624805] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 17:36:39 bbbdevice kernel: [ 1160.646011] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 17:36:39 bbbdevice kernel: [ 1160.647169] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:36:39 bbbdevice kernel: [ 1160.647579] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 17:36:39 bbbdevice kernel: [ 1160.647712] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 17:36:39 bbbdevice kernel: [ 1160.647722] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 17:43:51 bbbdevice kernel: [ 1591.934603] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:43:51 bbbdevice kernel: [ 1591.934626] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 17:43:51 bbbdevice kernel: [ 1591.934681] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 17:43:51 bbbdevice kernel: [ 1591.935013] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 17:43:51 bbbdevice kernel: [ 1591.946283] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 17:43:51 bbbdevice kernel: [ 1591.952266] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:43:51 bbbdevice kernel: [ 1591.952289] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 17:43:51 bbbdevice kernel: [ 1591.974474] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 17:43:51 bbbdevice kernel: [ 1591.975653] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:43:51 bbbdevice kernel: [ 1591.978780] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 17:43:51 bbbdevice kernel: [ 1591.979006] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 17:43:51 bbbdevice kernel: [ 1591.979018] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 17:47:42 bbbdevice kernel: [ 1822.797764] rpmsg_pru virtio1.rpmsg-pru.-1.31: Not enough space on the FIFO
Jul 23 17:47:42 bbbdevice kernel: [ 1822.818505] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:47:42 bbbdevice kernel: [ 1822.818527] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 17:47:42 bbbdevice kernel: [ 1822.818580] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 17:47:42 bbbdevice kernel: [ 1822.826250] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 17:47:42 bbbdevice kernel: [ 1822.826921] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 17:47:42 bbbdevice kernel: [ 1822.837478] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:47:42 bbbdevice kernel: [ 1822.837501] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 17:47:42 bbbdevice kernel: [ 1822.850785] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 17:47:42 bbbdevice kernel: [ 1822.851856] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:47:42 bbbdevice kernel: [ 1822.860274] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 17:47:42 bbbdevice kernel: [ 1822.860506] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 17:47:42 bbbdevice kernel: [ 1822.860518] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 17:58:22 bbbdevice kernel: [ 2462.842717] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.00030000
Jul 23 17:58:22 bbbdevice kernel: [ 2462.842739] pruss 4a300000.pruss: unconfigured host_intr = 0x00000005
Jul 23 17:58:22 bbbdevice kernel: [ 2462.842780] remoteproc remoteproc1: stopped remote processor 4a334000.pru
Jul 23 17:58:22 bbbdevice kernel: [ 2462.843111] remoteproc remoteproc1: powering up 4a334000.pru
Jul 23 17:58:22 bbbdevice kernel: [ 2462.843847] remoteproc remoteproc1: Booting fw image am335x-pru0-fw, size 100988
Jul 23 17:58:22 bbbdevice kernel: [ 2462.844599] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.00030000
Jul 23 17:58:22 bbbdevice kernel: [ 2462.844613] pruss 4a300000.pruss: configured intr_channels = 0x00000005 host_intr = 0x00000005
Jul 23 17:58:22 bbbdevice kernel: [ 2462.854931] virtio_rpmsg_bus virtio0: creating channel rpmsg-pru addr 0x1e
Jul 23 17:58:22 bbbdevice kernel: [ 2462.855751] rpmsg_pru virtio0.rpmsg-pru.-1.30: new rpmsg_pru device: /dev/rpmsg_pru30
Jul 23 17:58:22 bbbdevice kernel: [ 2462.855924] virtio_rpmsg_bus virtio0: rpmsg host is online
Jul 23 17:58:22 bbbdevice kernel: [ 2462.856023] remoteproc remoteproc1: registered virtio0 (type 7)
Jul 23 17:58:22 bbbdevice kernel: [ 2462.856034] remoteproc remoteproc1: remote processor 4a334000.pru is now up
Jul 23 17:58:22 bbbdevice kernel: [ 2462.864534] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:58:22 bbbdevice kernel: [ 2462.864556] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 17:58:22 bbbdevice kernel: [ 2462.864611] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 17:58:22 bbbdevice kernel: [ 2462.864946] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 17:58:22 bbbdevice kernel: [ 2462.870008] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 17:58:22 bbbdevice kernel: [ 2462.871076] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 17:58:22 bbbdevice kernel: [ 2462.871091] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 17:58:22 bbbdevice kernel: [ 2462.876287] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 17:58:22 bbbdevice kernel: [ 2462.877184] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 17:58:22 bbbdevice kernel: [ 2462.877348] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 17:58:22 bbbdevice kernel: [ 2462.877446] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 17:58:22 bbbdevice kernel: [ 2462.877456] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 18:00:57 bbbdevice kernel: [ 2618.613304] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:00:57 bbbdevice kernel: [ 2618.613327] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 18:00:57 bbbdevice kernel: [ 2618.613385] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 18:00:57 bbbdevice kernel: [ 2618.620463] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 18:00:57 bbbdevice kernel: [ 2618.629191] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 18:00:57 bbbdevice kernel: [ 2618.642946] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:00:57 bbbdevice kernel: [ 2618.642967] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 18:00:57 bbbdevice kernel: [ 2618.658099] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 18:00:57 bbbdevice kernel: [ 2618.659336] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 18:00:57 bbbdevice kernel: [ 2618.660023] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 18:00:57 bbbdevice kernel: [ 2618.665503] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 18:00:57 bbbdevice kernel: [ 2618.665524] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 18:04:13 bbbdevice kernel: [ 2814.092020] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:04:13 bbbdevice kernel: [ 2814.092043] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 18:04:13 bbbdevice kernel: [ 2814.092097] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 18:04:13 bbbdevice kernel: [ 2814.092646] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 18:04:13 bbbdevice kernel: [ 2814.093256] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 18:04:13 bbbdevice kernel: [ 2814.112410] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:04:13 bbbdevice kernel: [ 2814.112431] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 18:04:13 bbbdevice kernel: [ 2814.126072] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 18:04:13 bbbdevice kernel: [ 2814.127260] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 18:04:13 bbbdevice kernel: [ 2814.130403] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 18:04:13 bbbdevice kernel: [ 2814.130671] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 18:04:13 bbbdevice kernel: [ 2814.130683] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 18:06:16 bbbdevice kernel: [ 2936.831641] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:06:16 bbbdevice kernel: [ 2936.831663] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 18:06:16 bbbdevice kernel: [ 2936.831714] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 18:06:16 bbbdevice kernel: [ 2936.832052] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 18:06:16 bbbdevice kernel: [ 2936.838669] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 18:06:16 bbbdevice kernel: [ 2936.850189] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:06:16 bbbdevice kernel: [ 2936.850211] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 18:06:16 bbbdevice kernel: [ 2936.870313] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 18:06:16 bbbdevice kernel: [ 2936.871493] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 18:06:16 bbbdevice kernel: [ 2936.874877] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 18:06:16 bbbdevice kernel: [ 2936.875099] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 18:06:16 bbbdevice kernel: [ 2936.875110] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 18:11:07 bbbdevice kernel: [ 3228.294819] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:11:07 bbbdevice kernel: [ 3228.294840] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 18:11:07 bbbdevice kernel: [ 3228.294884] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 18:11:07 bbbdevice kernel: [ 3228.295222] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 18:11:07 bbbdevice kernel: [ 3228.314842] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 18:11:07 bbbdevice kernel: [ 3228.331951] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:11:07 bbbdevice kernel: [ 3228.331973] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 18:11:07 bbbdevice kernel: [ 3228.354622] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 18:11:07 bbbdevice kernel: [ 3228.355690] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 18:11:07 bbbdevice kernel: [ 3228.363152] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 18:11:07 bbbdevice kernel: [ 3228.368531] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 18:11:07 bbbdevice kernel: [ 3228.368552] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 23 18:14:24 bbbdevice kernel: [ 3425.162500] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:14:24 bbbdevice kernel: [ 3425.162522] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 23 18:14:24 bbbdevice kernel: [ 3425.162578] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 23 18:14:24 bbbdevice kernel: [ 3425.162922] remoteproc remoteproc2: powering up 4a338000.pru
Jul 23 18:14:24 bbbdevice kernel: [ 3425.163713] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 23 18:14:24 bbbdevice kernel: [ 3425.174728] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 23 18:14:24 bbbdevice kernel: [ 3425.174750] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 23 18:14:24 bbbdevice kernel: [ 3425.188711] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 23 18:14:24 bbbdevice kernel: [ 3425.190055] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 23 18:14:24 bbbdevice kernel: [ 3425.190992] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 23 18:14:24 bbbdevice kernel: [ 3425.198179] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 23 18:14:24 bbbdevice kernel: [ 3425.198200] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 24 00:00:02 bbbdevice kernel: [24163.800911] sh (5152): drop_caches: 3
Jul 25 00:00:01 bbbdevice kernel: [110566.506647] sh (6527): drop_caches: 3
Jul 26 00:00:02 bbbdevice kernel: [196970.140779] sh (7903): drop_caches: 3
Jul 26 13:42:05 bbbdevice kernel: [246295.004865] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery
Jul 26 13:42:05 bbbdevice kernel: [246295.012744] ------------[ cut here ]------------
Jul 26 13:42:05 bbbdevice kernel: [246295.013040] WARNING: CPU: 0 PID: 7274 at drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore]
Jul 26 13:42:05 bbbdevice kernel: [246295.013049] Modules linked in: rpmsg_pru virtio_rpmsg_bus rpmsg_core aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 cfg80211 pruss_soc_bus wlcore_sdio evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite ip6table_filter ip6_tables xt_tcpudp xt_conntrack iptable_filter iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack spidev pru_rproc pruss pruss_intc ip_tables x_tables
Jul 26 13:42:05 bbbdevice kernel: [246295.013236] CPU: 0 PID: 7274 Comm: kworker/u2:1 Not tainted 4.14.71-ti-r80 #1
Jul 26 13:42:05 bbbdevice kernel: [246295.013243] Hardware name: Generic AM33XX (Flattened Device Tree)
Jul 26 13:42:05 bbbdevice kernel: [246295.013363] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore]
Jul 26 13:42:05 bbbdevice kernel: [246295.013414] [<c0113910>] (unwind_backtrace) from [<c010debc>] (show_stack+0x20/0x24)
Jul 26 13:42:05 bbbdevice kernel: [246295.013434] [<c010debc>] (show_stack) from [<c0d9ca74>] (dump_stack+0x80/0x94)
Jul 26 13:42:05 bbbdevice kernel: [246295.013462] [<c0d9ca74>] (dump_stack) from [<c013f8e8>] (__warn+0xf8/0x110)
Jul 26 13:42:05 bbbdevice kernel: [246295.013479] [<c013f8e8>] (__warn) from [<c013fa18>] (warn_slowpath_null+0x30/0x38)
Jul 26 13:42:05 bbbdevice kernel: [246295.013590] [<c013fa18>] (warn_slowpath_null) from [<bf358f6c>] (wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore])
Jul 26 13:42:05 bbbdevice kernel: [246295.013801] [<bf358f6c>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf3590c0>] (wl12xx_tx_watchdog_work+0x150/0x160 [wlcore])
Jul 26 13:42:05 bbbdevice kernel: [246295.013897] [<bf3590c0>] (wl12xx_tx_watchdog_work [wlcore]) from [<c015d30c>] (process_one_work+0x19c/0x518)
Jul 26 13:42:05 bbbdevice kernel: [246295.013911] [<c015d30c>] (process_one_work) from [<c015e244>] (worker_thread+0x60/0x540)
Jul 26 13:42:05 bbbdevice kernel: [246295.013928] [<c015e244>] (worker_thread) from [<c0163e54>] (kthread+0x144/0x174)
Jul 26 13:42:05 bbbdevice kernel: [246295.013950] [<c0163e54>] (kthread) from [<c0108fe8>] (ret_from_fork+0x14/0x2c)
Jul 26 13:42:05 bbbdevice kernel: [246295.014106] ---[ end trace ebf647b7e196b615 ]---
Jul 26 13:42:05 bbbdevice kernel: [246295.014216] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.69
Jul 26 13:42:05 bbbdevice kernel: [246295.014816] wlcore: pc: 0x0, hint_sts: 0x00000040 count: 1
Jul 26 13:42:05 bbbdevice kernel: [246295.015364] wlcore: down
Jul 26 13:42:05 bbbdevice kernel: [246295.015411] wlcore: down
Jul 26 13:42:05 bbbdevice kernel: [246295.015426] wlcore: down
Jul 26 13:42:05 bbbdevice kernel: [246295.029251] ieee80211 phy0: Hardware restart was requested
Jul 26 13:42:05 bbbdevice kernel: [246295.484426] wlcore: PHY firmware version: Rev 8.2.0.0.236
Jul 26 13:42:06 bbbdevice kernel: [246295.524801] wlcore: firmware booted (Rev 8.9.0.0.69)
Jul 26 13:42:06 bbbdevice kernel: [246295.562450] wlcore: Association completed.
Jul 26 14:33:07 bbbdevice kernel: [249356.764706] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery
Jul 26 14:33:07 bbbdevice kernel: [249356.772358] ------------[ cut here ]------------
Jul 26 14:33:07 bbbdevice kernel: [249356.772653] WARNING: CPU: 0 PID: 8776 at drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore]
Jul 26 14:33:07 bbbdevice kernel: [249356.775854] Modules linked in: rpmsg_pru virtio_rpmsg_bus rpmsg_core aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 cfg80211 pruss_soc_bus wlcore_sdio evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite ip6table_filter ip6_tables xt_tcpudp xt_conntrack iptable_filter iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack spidev pru_rproc pruss pruss_intc ip_tables x_tables
Jul 26 14:33:07 bbbdevice kernel: [249356.776041] CPU: 0 PID: 8776 Comm: kworker/u2:2 Tainted: G W 4.14.71-ti-r80 #1
Jul 26 14:33:07 bbbdevice kernel: [249356.776048] Hardware name: Generic AM33XX (Flattened Device Tree)
Jul 26 14:33:07 bbbdevice kernel: [249356.776314] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore]
Jul 26 14:33:07 bbbdevice kernel: [249356.776365] [<c0113910>] (unwind_backtrace) from [<c010debc>] (show_stack+0x20/0x24)
Jul 26 14:33:07 bbbdevice kernel: [249356.776386] [<c010debc>] (show_stack) from [<c0d9ca74>] (dump_stack+0x80/0x94)
Jul 26 14:33:07 bbbdevice kernel: [249356.776415] [<c0d9ca74>] (dump_stack) from [<c013f8e8>] (__warn+0xf8/0x110)
Jul 26 14:33:07 bbbdevice kernel: [249356.776430] [<c013f8e8>] (__warn) from [<c013fa18>] (warn_slowpath_null+0x30/0x38)
Jul 26 14:33:07 bbbdevice kernel: [249356.776561] [<c013fa18>] (warn_slowpath_null) from [<bf358f6c>] (wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore])
Jul 26 14:33:07 bbbdevice kernel: [249356.776748] [<bf358f6c>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf3590c0>] (wl12xx_tx_watchdog_work+0x150/0x160 [wlcore])
Jul 26 14:33:07 bbbdevice kernel: [249356.776843] [<bf3590c0>] (wl12xx_tx_watchdog_work [wlcore]) from [<c015d30c>] (process_one_work+0x19c/0x518)
Jul 26 14:33:07 bbbdevice kernel: [249356.776857] [<c015d30c>] (process_one_work) from [<c015e244>] (worker_thread+0x60/0x540)
Jul 26 14:33:07 bbbdevice kernel: [249356.776874] [<c015e244>] (worker_thread) from [<c0163e54>] (kthread+0x144/0x174)
Jul 26 14:33:07 bbbdevice kernel: [249356.776895] [<c0163e54>] (kthread) from [<c0108fe8>] (ret_from_fork+0x14/0x2c)
Jul 26 14:33:07 bbbdevice kernel: [249356.782030] ---[ end trace ebf647b7e196b616 ]---
Jul 26 14:33:07 bbbdevice kernel: [249356.783286] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.69
Jul 26 14:33:07 bbbdevice kernel: [249356.786790] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 2
Jul 26 14:33:07 bbbdevice kernel: [249356.787209] wlcore: down
Jul 26 14:33:07 bbbdevice kernel: [249356.787257] wlcore: down
Jul 26 14:33:07 bbbdevice kernel: [249356.787272] wlcore: down
Jul 26 14:33:07 bbbdevice kernel: [249356.790214] ieee80211 phy0: Hardware restart was requested
Jul 26 14:33:07 bbbdevice kernel: [249357.240419] wlcore: PHY firmware version: Rev 8.2.0.0.236
Jul 26 14:33:07 bbbdevice kernel: [249357.285595] wlcore: firmware booted (Rev 8.9.0.0.69)
Jul 26 14:33:07 bbbdevice kernel: [249357.334366] wlcore: Association completed.
Jul 26 14:34:44 bbbdevice kernel: [249453.532906] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery
Jul 26 14:34:44 bbbdevice kernel: [249453.540531] ------------[ cut here ]------------
Jul 26 14:34:44 bbbdevice kernel: [249453.540826] WARNING: CPU: 0 PID: 8785 at drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore]
Jul 26 14:34:44 bbbdevice kernel: [249453.543275] Modules linked in: rpmsg_pru virtio_rpmsg_bus rpmsg_core aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 cfg80211 pruss_soc_bus wlcore_sdio evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite ip6table_filter ip6_tables xt_tcpudp xt_conntrack iptable_filter iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack spidev pru_rproc pruss pruss_intc ip_tables x_tables
Jul 26 14:34:44 bbbdevice kernel: [249453.543464] CPU: 0 PID: 8785 Comm: kworker/u2:1 Tainted: G W 4.14.71-ti-r80 #1
Jul 26 14:34:44 bbbdevice kernel: [249453.543470] Hardware name: Generic AM33XX (Flattened Device Tree)
Jul 26 14:34:44 bbbdevice kernel: [249453.543718] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore]
Jul 26 14:34:44 bbbdevice kernel: [249453.543770] [<c0113910>] (unwind_backtrace) from [<c010debc>] (show_stack+0x20/0x24)
Jul 26 14:34:44 bbbdevice kernel: [249453.543791] [<c010debc>] (show_stack) from [<c0d9ca74>] (dump_stack+0x80/0x94)
Jul 26 14:34:44 bbbdevice kernel: [249453.543819] [<c0d9ca74>] (dump_stack) from [<c013f8e8>] (__warn+0xf8/0x110)
Jul 26 14:34:44 bbbdevice kernel: [249453.543836] [<c013f8e8>] (__warn) from [<c013fa18>] (warn_slowpath_null+0x30/0x38)
Jul 26 14:34:44 bbbdevice kernel: [249453.543963] [<c013fa18>] (warn_slowpath_null) from [<bf358f6c>] (wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore])
Jul 26 14:34:44 bbbdevice kernel: [249453.544153] [<bf358f6c>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf3590c0>] (wl12xx_tx_watchdog_work+0x150/0x160 [wlcore])
Jul 26 14:34:44 bbbdevice kernel: [249453.544250] [<bf3590c0>] (wl12xx_tx_watchdog_work [wlcore]) from [<c015d30c>] (process_one_work+0x19c/0x518)
Jul 26 14:34:44 bbbdevice kernel: [249453.544264] [<c015d30c>] (process_one_work) from [<c015e244>] (worker_thread+0x60/0x540)
Jul 26 14:34:44 bbbdevice kernel: [249453.544282] [<c015e244>] (worker_thread) from [<c0163e54>] (kthread+0x144/0x174)
Jul 26 14:34:44 bbbdevice kernel: [249453.544303] [<c0163e54>] (kthread) from [<c0108fe8>] (ret_from_fork+0x14/0x2c)
Jul 26 14:34:44 bbbdevice kernel: [249453.544498] ---[ end trace ebf647b7e196b617 ]---
Jul 26 14:34:44 bbbdevice kernel: [249453.555292] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.69
Jul 26 14:34:44 bbbdevice kernel: [249453.560275] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 3
Jul 26 14:34:44 bbbdevice kernel: [249453.562565] wlcore: down
Jul 26 14:34:44 bbbdevice kernel: [249453.562924] wlcore: down
Jul 26 14:34:44 bbbdevice kernel: [249453.562942] wlcore: down
Jul 26 14:34:44 bbbdevice kernel: [249453.565776] ieee80211 phy0: Hardware restart was requested
Jul 26 14:34:44 bbbdevice kernel: [249454.021662] wlcore: PHY firmware version: Rev 8.2.0.0.236
Jul 26 14:34:44 bbbdevice kernel: [249454.070798] wlcore: firmware booted (Rev 8.9.0.0.69)
Jul 26 14:34:44 bbbdevice kernel: [249454.116347] wlcore: Association completed.
Jul 26 17:22:54 bbbdevice kernel: [259543.982097] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 26 17:22:54 bbbdevice kernel: [259543.982119] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 26 17:22:54 bbbdevice kernel: [259543.982159] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 26 17:22:54 bbbdevice kernel: [259543.982502] remoteproc remoteproc2: powering up 4a338000.pru
Jul 26 17:22:54 bbbdevice kernel: [259544.010363] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 26 17:22:54 bbbdevice kernel: [259544.023794] alloc_contig_range: [9c905, 9c906) PFNs busy
Jul 26 17:22:54 bbbdevice kernel: [259544.026806] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 26 17:22:54 bbbdevice kernel: [259544.026826] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 26 17:22:54 bbbdevice kernel: [259544.059505] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 26 17:22:54 bbbdevice kernel: [259544.060902] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 26 17:22:54 bbbdevice kernel: [259544.067445] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 26 17:22:54 bbbdevice kernel: [259544.067689] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 26 17:22:54 bbbdevice kernel: [259544.067701] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 26 17:41:47 bbbdevice kernel: [260677.245147] pruss 4a300000.pruss: unconfigured system_events[63-0] = 0x00000000.000c0000
Jul 26 17:41:47 bbbdevice kernel: [260677.245170] pruss 4a300000.pruss: unconfigured host_intr = 0x0000000a
Jul 26 17:41:47 bbbdevice kernel: [260677.245223] remoteproc remoteproc2: stopped remote processor 4a338000.pru
Jul 26 17:41:47 bbbdevice kernel: [260677.245576] remoteproc remoteproc2: powering up 4a338000.pru
Jul 26 17:41:47 bbbdevice kernel: [260677.257780] remoteproc remoteproc2: Booting fw image am335x-pru1-fw, size 118264
Jul 26 17:41:47 bbbdevice kernel: [260677.264089] pruss 4a300000.pruss: configured system_events[63-0] = 0x00000000.000c0000
Jul 26 17:41:47 bbbdevice kernel: [260677.264110] pruss 4a300000.pruss: configured intr_channels = 0x0000000a host_intr = 0x0000000a
Jul 26 17:41:47 bbbdevice kernel: [260677.278956] virtio_rpmsg_bus virtio1: creating channel rpmsg-pru addr 0x1f
Jul 26 17:41:47 bbbdevice kernel: [260677.280053] rpmsg_pru virtio1.rpmsg-pru.-1.31: new rpmsg_pru device: /dev/rpmsg_pru31
Jul 26 17:41:47 bbbdevice kernel: [260677.282841] virtio_rpmsg_bus virtio1: rpmsg host is online
Jul 26 17:41:47 bbbdevice kernel: [260677.283068] remoteproc remoteproc2: registered virtio1 (type 7)
Jul 26 17:41:47 bbbdevice kernel: [260677.283079] remoteproc remoteproc2: remote processor 4a338000.pru is now up
Jul 27 00:00:02 bbbdevice kernel: [283373.085418] sh (9539): drop_caches: 3
Jul 27 13:48:06 bbbdevice kernel: [333058.729535] wlcore: Beacon loss detected. roles:0x1
Jul 27 13:48:11 bbbdevice kernel: [333063.644817] wlcore: Connection loss work (role_id: 0).
Jul 27 13:48:11 bbbdevice kernel: [333063.644893] wlan0: Connection to AP dc:ef:09:ad:5d:56 lost
Jul 27 13:48:11 bbbdevice kernel: [333064.156681] wlcore: WARNING Unable to flush all TX buffers, timed out (timeout 500 ms
Jul 27 13:48:12 bbbdevice kernel: [333064.660546] wlcore: WARNING Unable to flush all TX buffers, timed out (timeout 500 ms
Jul 27 13:48:12 bbbdevice kernel: [333064.731040] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 27 13:48:14 bbbdevice kernel: [333066.699672] wlan0: authenticate with dc:ef:09:ad:5d:56
Jul 27 13:48:14 bbbdevice kernel: [333066.706339] wlan0: send auth to dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 13:48:14 bbbdevice kernel: [333066.880460] wlan0: send auth to dc:ef:09:ad:5d:56 (try 2/3)
Jul 27 13:48:14 bbbdevice kernel: [333066.891132] wlan0: authenticated
Jul 27 13:48:14 bbbdevice kernel: [333066.896555] wlan0: associate with dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 13:48:14 bbbdevice kernel: [333066.950550] wlan0: associate with dc:ef:09:ad:5d:56 (try 2/3)
Jul 27 13:48:14 bbbdevice kernel: [333067.042505] wlan0: associate with dc:ef:09:ad:5d:56 (try 3/3)
Jul 27 13:48:14 bbbdevice kernel: [333067.117250] wlan0: RX AssocResp from dc:ef:09:ad:5d:56 (capab=0x411 status=0 aid=2)
Jul 27 13:48:14 bbbdevice kernel: [333067.117310] wlan0: AP has invalid WMM params (AIFSN=1 for ACI 2), will use 2
Jul 27 13:48:14 bbbdevice kernel: [333067.117317] wlan0: AP has invalid WMM params (AIFSN=1 for ACI 3), will use 2
Jul 27 13:48:14 bbbdevice kernel: [333067.132509] wlan0: associated
Jul 27 13:48:14 bbbdevice kernel: [333067.193200] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by dc:ef:09:ad:5d:56
Jul 27 13:48:14 bbbdevice kernel: [333067.267738] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 27 13:48:14 bbbdevice kernel: [333067.284117] wlcore: Association completed.
Jul 27 13:48:27 bbbdevice kernel: [333080.033672] wlcore: Beacon loss detected. roles:0x1
Jul 27 13:48:32 bbbdevice kernel: [333084.892512] wlcore: Connection loss work (role_id: 0).
Jul 27 13:48:32 bbbdevice kernel: [333084.892587] wlan0: Connection to AP dc:ef:09:ad:5d:56 lost
Jul 27 13:48:32 bbbdevice kernel: [333085.273168] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 27 13:49:06 bbbdevice kernel: [333119.451076] wlan0: authenticate with dc:ef:09:ad:5d:56
Jul 27 13:49:06 bbbdevice kernel: [333119.463020] wlan0: send auth to dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 13:49:06 bbbdevice kernel: [333119.573596] wlan0: authenticated
Jul 27 13:49:06 bbbdevice kernel: [333119.577427] wlan0: associate with dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 13:49:06 bbbdevice kernel: [333119.581933] wlan0: RX AssocResp from dc:ef:09:ad:5d:56 (capab=0x411 status=0 aid=2)
Jul 27 13:49:06 bbbdevice kernel: [333119.581997] wlan0: AP has invalid WMM params (AIFSN=1 for ACI 2), will use 2
Jul 27 13:49:06 bbbdevice kernel: [333119.582004] wlan0: AP has invalid WMM params (AIFSN=1 for ACI 3), will use 2
Jul 27 13:49:07 bbbdevice kernel: [333119.604474] wlan0: associated
Jul 27 13:49:07 bbbdevice kernel: [333119.620587] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by dc:ef:09:ad:5d:56
Jul 27 13:49:07 bbbdevice kernel: [333119.657368] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 27 13:49:07 bbbdevice kernel: [333119.682684] wlcore: Association completed.
Jul 27 14:30:00 bbbdevice kernel: [335572.966634] wlcore: Beacon loss detected. roles:0x1
Jul 27 14:30:05 bbbdevice kernel: [335577.820448] wlcore: Connection loss work (role_id: 0).
Jul 27 14:30:05 bbbdevice kernel: [335577.820497] wlan0: Connection to AP dc:ef:09:ad:5d:56 lost
Jul 27 14:30:05 bbbdevice kernel: [335578.336326] wlcore: WARNING Unable to flush all TX buffers, timed out (timeout 500 ms
Jul 27 14:30:06 bbbdevice kernel: [335578.840542] wlcore: WARNING Unable to flush all TX buffers, timed out (timeout 500 ms
Jul 27 14:30:06 bbbdevice kernel: [335578.908904] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 27 14:30:07 bbbdevice kernel: [335580.110344] wlan0: authenticate with dc:ef:09:ad:5d:56
Jul 27 14:30:07 bbbdevice kernel: [335580.117710] wlan0: send auth to dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 14:30:07 bbbdevice kernel: [335580.235139] wlan0: authenticated
Jul 27 14:30:07 bbbdevice kernel: [335580.244415] wlan0: associate with dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 14:30:07 bbbdevice kernel: [335580.366086] wlan0: associate with dc:ef:09:ad:5d:56 (try 2/3)
Jul 27 14:30:07 bbbdevice kernel: [335580.462536] wlan0: associate with dc:ef:09:ad:5d:56 (try 3/3)
Jul 27 14:30:08 bbbdevice kernel: [335580.596064] wlan0: association with dc:ef:09:ad:5d:56 timed out
Jul 27 14:34:15 bbbdevice kernel: [335828.065117] wlan0: authenticate with dc:ef:09:ad:5d:56
Jul 27 14:34:15 bbbdevice kernel: [335828.082372] wlan0: send auth to dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 14:34:15 bbbdevice kernel: [335828.242242] wlan0: authenticated
Jul 27 14:34:15 bbbdevice kernel: [335828.247589] wlan0: associate with dc:ef:09:ad:5d:56 (try 1/3)
Jul 27 14:34:15 bbbdevice kernel: [335828.252798] wlan0: RX AssocResp from dc:ef:09:ad:5d:56 (capab=0x411 status=0 aid=2)
Jul 27 14:34:15 bbbdevice kernel: [335828.252861] wlan0: AP has invalid WMM params (AIFSN=1 for ACI 2), will use 2
Jul 27 14:34:15 bbbdevice kernel: [335828.252905] wlan0: AP has invalid WMM params (AIFSN=1 for ACI 3), will use 2
Jul 27 14:34:15 bbbdevice kernel: [335828.273433] wlan0: associated
Jul 27 14:34:15 bbbdevice kernel: [335828.327804] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 27 14:34:15 bbbdevice kernel: [335828.364637] wlcore: Association completed.
Jul 27 14:34:15 bbbdevice kernel: [335828.411336] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by dc:ef:09:ad:5d:56
Jul 27 22:31:40 bbbdevice kernel: [364474.181798] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 64
Jul 28 00:00:02 bbbdevice kernel: [369776.371109] sh (10955): drop_caches: 3
Jul 28 00:53:03 bbbdevice kernel: [372957.148369] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery
Jul 28 00:53:03 bbbdevice kernel: [372957.156124] ------------[ cut here ]------------
Jul 28 00:53:03 bbbdevice kernel: [372957.156419] WARNING: CPU: 0 PID: 10462 at drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore]
Jul 28 00:53:03 bbbdevice kernel: [372957.156427] Modules linked in: rpmsg_pru virtio_rpmsg_bus rpmsg_core aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 cfg80211 pruss_soc_bus wlcore_sdio evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite ip6table_filter ip6_tables xt_tcpudp xt_conntrack iptable_filter iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack spidev pru_rproc pruss pruss_intc ip_tables x_tables
Jul 28 00:53:03 bbbdevice kernel: [372957.156609] CPU: 0 PID: 10462 Comm: kworker/u2:3 Tainted: G W 4.14.71-ti-r80 #1
Jul 28 00:53:03 bbbdevice kernel: [372957.156615] Hardware name: Generic AM33XX (Flattened Device Tree)
Jul 28 00:53:03 bbbdevice kernel: [372957.156737] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore]
Jul 28 00:53:03 bbbdevice kernel: [372957.156786] [<c0113910>] (unwind_backtrace) from [<c010debc>] (show_stack+0x20/0x24)
Jul 28 00:53:03 bbbdevice kernel: [372957.156807] [<c010debc>] (show_stack) from [<c0d9ca74>] (dump_stack+0x80/0x94)
Jul 28 00:53:03 bbbdevice kernel: [372957.156835] [<c0d9ca74>] (dump_stack) from [<c013f8e8>] (__warn+0xf8/0x110)
Jul 28 00:53:03 bbbdevice kernel: [372957.156850] [<c013f8e8>] (__warn) from [<c013fa18>] (warn_slowpath_null+0x30/0x38)
Jul 28 00:53:03 bbbdevice kernel: [372957.156960] [<c013fa18>] (warn_slowpath_null) from [<bf358f6c>] (wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore])
Jul 28 00:53:03 bbbdevice kernel: [372957.157144] [<bf358f6c>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf3590c0>] (wl12xx_tx_watchdog_work+0x150/0x160 [wlcore])
Jul 28 00:53:03 bbbdevice kernel: [372957.157239] [<bf3590c0>] (wl12xx_tx_watchdog_work [wlcore]) from [<c015d30c>] (process_one_work+0x19c/0x518)
Jul 28 00:53:03 bbbdevice kernel: [372957.157253] [<c015d30c>] (process_one_work) from [<c015e244>] (worker_thread+0x60/0x540)
Jul 28 00:53:03 bbbdevice kernel: [372957.157270] [<c015e244>] (worker_thread) from [<c0163e54>] (kthread+0x144/0x174)
Jul 28 00:53:03 bbbdevice kernel: [372957.157292] [<c0163e54>] (kthread) from [<c0108fe8>] (ret_from_fork+0x14/0x2c)
Jul 28 00:53:03 bbbdevice kernel: [372957.157441] ---[ end trace ebf647b7e196b618 ]---
Jul 28 00:53:03 bbbdevice kernel: [372957.157757] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.69
Jul 28 00:53:03 bbbdevice kernel: [372957.158388] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 4
Jul 28 00:53:03 bbbdevice kernel: [372957.158884] wlcore: down
Jul 28 00:53:03 bbbdevice kernel: [372957.158929] wlcore: down
Jul 28 00:53:03 bbbdevice kernel: [372957.158944] wlcore: down
Jul 28 00:53:03 bbbdevice kernel: [372957.167449] ieee80211 phy0: Hardware restart was requested
Jul 28 00:53:03 bbbdevice kernel: [372957.617406] wlcore: PHY firmware version: Rev 8.2.0.0.236
Jul 28 00:53:03 bbbdevice kernel: [372957.677366] wlcore: firmware booted (Rev 8.9.0.0.69)
Jul 28 00:53:03 bbbdevice kernel: [372957.724431] wlcore: Association completed.
Jul 28 03:25:47 bbbdevice kernel: [382122.129369] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 03:25:47 bbbdevice kernel: [382122.129803] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 03:25:48 bbbdevice kernel: [382122.948437] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 03:25:49 bbbdevice kernel: [382124.177397] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 03:25:51 bbbdevice kernel: [382125.406174] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 03:25:51 bbbdevice kernel: [382126.225538] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 09:51:01 bbbdevice kernel: [405236.835449] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 09:51:02 bbbdevice kernel: [405237.655077] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 60
Jul 28 09:51:09 bbbdevice kernel: [405244.208586] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 64
Jul 28 09:51:12 bbbdevice kernel: [405247.084472] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 104
Jul 29 00:00:02 bbbdevice kernel: [456179.336671] sh (12324): drop_caches: 3
Jul 29 09:35:17 bbbdevice kernel: [490695.387794] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery
Jul 29 09:35:17 bbbdevice kernel: [490695.400698] ------------[ cut here ]------------
Jul 29 09:35:17 bbbdevice kernel: [490695.401004] WARNING: CPU: 0 PID: 11879 at drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore]
Jul 29 09:35:17 bbbdevice kernel: [490695.401013] Modules linked in: rpmsg_pru virtio_rpmsg_bus rpmsg_core aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 cfg80211 pruss_soc_bus wlcore_sdio evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite ip6table_filter ip6_tables xt_tcpudp xt_conntrack iptable_filter iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack spidev pru_rproc pruss pruss_intc ip_tables x_tables
Jul 29 09:35:17 bbbdevice kernel: [490695.401196] CPU: 0 PID: 11879 Comm: kworker/u2:4 Tainted: G W 4.14.71-ti-r80 #1
Jul 29 09:35:17 bbbdevice kernel: [490695.401202] Hardware name: Generic AM33XX (Flattened Device Tree)
Jul 29 09:35:17 bbbdevice kernel: [490695.401331] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore]
Jul 29 09:35:17 bbbdevice kernel: [490695.401381] [<c0113910>] (unwind_backtrace) from [<c010debc>] (show_stack+0x20/0x24)
Jul 29 09:35:17 bbbdevice kernel: [490695.401402] [<c010debc>] (show_stack) from [<c0d9ca74>] (dump_stack+0x80/0x94)
Jul 29 09:35:17 bbbdevice kernel: [490695.401430] [<c0d9ca74>] (dump_stack) from [<c013f8e8>] (__warn+0xf8/0x110)
Jul 29 09:35:17 bbbdevice kernel: [490695.401446] [<c013f8e8>] (__warn) from [<c013fa18>] (warn_slowpath_null+0x30/0x38)
Jul 29 09:35:17 bbbdevice kernel: [490695.401560] [<c013fa18>] (warn_slowpath_null) from [<bf358f6c>] (wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore])
Jul 29 09:35:17 bbbdevice kernel: [490695.401746] [<bf358f6c>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf3590c0>] (wl12xx_tx_watchdog_work+0x150/0x160 [wlcore])
Jul 29 09:35:17 bbbdevice kernel: [490695.401840] [<bf3590c0>] (wl12xx_tx_watchdog_work [wlcore]) from [<c015d30c>] (process_one_work+0x19c/0x518)
Jul 29 09:35:17 bbbdevice kernel: [490695.401855] [<c015d30c>] (process_one_work) from [<c015e244>] (worker_thread+0x60/0x540)
Jul 29 09:35:17 bbbdevice kernel: [490695.401873] [<c015e244>] (worker_thread) from [<c0163e54>] (kthread+0x144/0x174)
Jul 29 09:35:17 bbbdevice kernel: [490695.401893] [<c0163e54>] (kthread) from [<c0108fe8>] (ret_from_fork+0x14/0x2c)
Jul 29 09:35:17 bbbdevice kernel: [490695.410556] ---[ end trace ebf647b7e196b619 ]---
Jul 29 09:35:17 bbbdevice kernel: [490695.410647] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.69
Jul 29 09:35:17 bbbdevice kernel: [490695.414061] wlcore: pc: 0x0, hint_sts: 0x00000000 count: 5
Jul 29 09:35:17 bbbdevice kernel: [490695.416462] wlcore: down
Jul 29 09:35:17 bbbdevice kernel: [490695.416518] wlcore: down
Jul 29 09:35:17 bbbdevice kernel: [490695.416534] wlcore: down
Jul 29 09:35:17 bbbdevice kernel: [490695.421255] ieee80211 phy0: Hardware restart was requested
Jul 29 09:35:17 bbbdevice kernel: [490695.878557] wlcore: PHY firmware version: Rev 8.2.0.0.236
Jul 29 09:35:17 bbbdevice kernel: [490695.928797] wlcore: firmware booted (Rev 8.9.0.0.69)
Jul 29 09:35:17 bbbdevice kernel: [490695.967399] wlcore: Association completed.
Jul 29 20:53:39 bbbdevice kernel: [531398.986650] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 78
Jul 29 20:53:39 bbbdevice kernel: [531399.398239] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 280
Jul 29 20:53:40 bbbdevice kernel: [531399.806042] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 78
Jul 29 20:53:40 bbbdevice kernel: [531400.625098] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 78
Jul 29 20:53:42 bbbdevice kernel: [531402.278710] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 104
Jul 30 00:00:01 bbbdevice kernel: [542581.956925] sh (13694): drop_caches: 3
  • Raajeshwar,

    Apologize for the delay in responding to this issue. Our PRU Linux expert is out of office currently so please expect some delays in our responses. We will try to respond back to you by Wednesday next week. Feel free to ping us if you don`t see a response. 

    Thank you for your understanding

    Regards,

    Rahul 

  • Hello,

    Did you verify that nothing strange happened with the ADC? e.g.,

    1) the value the ADC was reading in did not go to 0?

    2) The ADC peripheral was still clocked, and all of its registers were still set as expected?

    3) The ADC was still putting valid data in its FIFOs for the PRU to access?

    Regards,

    Nick

  • Hi Nick,

    1) The supply voltage we have provided to analog pin is 1.8V and it did not go to 0. But the value we got from PRU was 0. We are not sure that the PRU read the ADC value internally.
    2) We restarted the pru firmware, hence ADC peripheral was expected to be clocked and its registers was expected to be set.
    3) We were reading from FIFO and sending it via Rpmsg and it was 0. So it may not be valid data.

    From the syslog does the following lines make sense? Whether this affects ADC?

    Modules linked in: rpmsg_pru virtio_rpmsg_bus rpmsg_core aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 cfg80211 pruss_soc_bus wlcore_sdio evdev uio_pdrv_genirq uio usb_f_acm u_serial usb_f_ecm usb_f_rndis u_ether libcomposite ip6table_filter ip6_tables xt_tcpudp xt_conntrack iptable_filter iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack spidev pru_rproc pruss pruss_intc ip_tables x_tables

    Do you think whether ADC is not reinitialized after restarting PRU firmware?

    Thanks in advance.

    Regards,

    Raajeshwar Elangovan.

  • Hello Raajeshwar,

    Once the PRU initializes the ADC, you should be able to use devmem2 to read the ADC memory space from your Linux core. If you are not able to access the ADC memory space, that likely means the ADC is no longer clocked. If you are able to read the memory space, you can check the key registers are still set the way you expect them to be.

    FYI, I created an example of using the PRU to initialize and control the ADC at https://git.ti.com/cgit/pru-software-support-package/ under examples/am335x/PRU_ADC_onChip. That should also give you ideas about which registers you want to read to verify they have the expected values.

    Regards,

    Nick

  • Hi Nick,

    Thank you for your suggestion. We tried different ways to replicate the issue we faced. It didn't happen again. Even after running it for long days, it looks good. I will get back to the discussion once I face similar problem again. For now I don't have enough inputs to discuss as everything is working fine. If you find anything weird from the log I have attached (which was the only clue left) please do suggest. Otherwise we can close this thread.

    Thanks and regards,

    Raajeshwar Elangovan.