Note: I also "piggybacked"/ "pork bellied" this issue onto the TI E2E thread referenced above, but disclosing the fact that I'm running a beagleboard distro I.P.V. the TI SDK.
Thanks and FYI, On Tuesday, March 20, 2018 at 11:09:31 AM UTC-5, Jeff Andich wrote: > > > Hi, > > We just got our re-worked custom boards back from the fab house with the > 5728, and on one of the boards on 1/6 power-ups, I got ".. Unable to handle > kernel paging request at virtual address 00002248 ... and at ffffffec." I > THINK this occurs when Debian is being mounted as we normally see Debian > messages after the vpe: couldn't get firmware in the case of a successful > boot. I'm not sure if this is a kernel crash, kernel panic, or a "kernel > OOPS." > > Following is the console log: > > > > Starting kernel ... > > [ 0.064925] /cpus/cpu@0 missing clock-frequency property > [ 0.064945] /cpus/cpu@1 missing clock-frequency property > [ 1.233031] dra7-pcie 51000000.pcie_rc: link is not up > [ 1.599305] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode > [ 1.605719] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode > [ 1.701868] omap_voltage_late_init: Voltage driver support not added > [ 2.008531] rtc-ds1307 2-006f: hctosys: unable to read the hardware > clock > Loading, please wait... > [ 2.792302] mmc2: error -22 whilst initialising SDIO card > [ 3.231127] remoteproc0: failed to load am57xx-pru1_0-fw > [ 3.242998] remoteproc0: request_firmware failed: -2 > [ 3.248093] pru-rproc 4b234000.pru0: rproc_boot failed > [ 3.258661] remoteproc0: failed to load am57xx-pru1_1-fw > [ 3.264779] remoteproc0: request_firmware failed: -2 > [ 3.269886] pru-rproc 4b238000.pru1: rproc_boot failed > [ 3.291919] remoteproc0: failed to load am57xx-pru2_0-fw > [ 3.299798] remoteproc0: request_firmware failed: -2 > [ 3.304910] pru-rproc 4b2b4000.pru0: rproc_boot failed > [ 3.328397] remoteproc0: failed to load am57xx-pru2_1-fw > [ 3.339743] remoteproc0: request_firmware failed: -2 > [ 3.344842] pru-rproc 4b2b8000.pru1: rproc_boot failed > rootfs: clean, 43747/232320 files, 390493/967040 blocks > [ 6.063694] remoteproc0: failed to load dra7-ipu1-fw.xem4 > [ 6.069850] remoteproc1: failed to load dra7-ipu2-fw.xem4 > [ 6.075464] remoteproc2: failed to load dra7-dsp1-fw.xe66 > [ 6.081735] remoteproc3: failed to load dra7-dsp2-fw.xe66 > [ 6.730836] pixcir_ts 4-005c: pixcir_set_power_mode: can't read reg > 0x33 : -121 > [ 6.738239] pixcir_ts 4-005c: Failed to set IDLE mode > [ 7.021310] vpe 489d0000.vpe: couldn't get firmware > > ************************************** LOOK HERE > ********************************************************************************* > [ 9.999478] Unable to handle kernel paging request at virtual address > 00002248 > > [ 0.006772] pgd = c0004000 > > [ 10.009402] [00002248] *pgd=00000000 > > [ 10.013025] Internal error: Oops: 17 [#1] SMP ARM > > [ 10.017747] Modules linked in: snd_soc_simple_card etnaviv > snd_soc_omap_hdmi_audio ftdi_sio usbseris > > [ 10.057143] CPU: 1 PID: 6 Comm: kworker/u4:0 Not tainted > 4.4.110-ti-r142 #9 > [ 10.064128] Hardware name: Generic DRA74X (Flattened Device Tree) > [ 10.070251] Workqueue: events_unbound flush_to_ldisc > [ 10.075238] task: ee16a080 ti: ee188000 task.ti: ee188000 > > [ 10.080657] PC is at n_tty_receive_buf_common+0x84/0xa68 > > [ 10.085991] LR is at down_read+0x1c/0x4c > [ 10.089926] pc : [<c0676368>] lr : [<c0aaef50>] psr: 200f0013 > [ 10.089926] sp : ee189e18 ip : ee189e00 fp : ee189e84 > [ 10.101449] r10: ed4b7c00 r9 : ee03d000 r8 : ee03d014 > [ 10.106691] r7 : ed4b7c00 r6 : ed4b7d84 r5 : ed4b7c80 r4 : c0af0c30 > [ 10.113241] r3 : 00002000 r2 : 00000000 r1 : ee69e0a0 r0 : 00000000 > [ 10.119793] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM > Segment none > [ 10.126954] Control: 10c5387d Table: ad53c06a DAC: 00000051 > [ 10.132720] Process kworker/u4:0 (pid: 6, stack limit = 0xee188218) > [ 10.139009] Stack: (0xee189e18 to 0xee18a000) > [ 10.143380] 9e00: > ed4b7c80 ee189e28 > [ 10.151589] 9e20: c00867a4 00020001 ed4b7d84 55555556 ee16a44c c1011a48 > c0af0c30 c100d300 > [ 10.159798] 9e40: 00002000 00000000 00000000 ee69e0a0 00000003 00000000 > ee189e8c ee69e000 > [ 10.168008] 9e60: 00000001 ee03d004 ed4b7c00 ee03d014 ee03d000 c0676d4c > ee189e9c ee189e88 > [ 10.184425] 9ea0: c0aac9a0 ee5b09c0 ee189ed4 ee03d004 ee0b5f80 ee03fc00 > 00000000 ee022b00 > [ 10.192635] 9ec0: c10e5fd8 ee022b05 ee189f14 ee189ed8 c005fee4 c067a968 > ee188000 c0061030 > [ 10.200846] 9ee0: ee189efc 00000000 c0061030 ee0b5f80 ee0b5f98 ee03fc00 > 00000088 ee03fc14 > [ 10.209055] 9f00: ee188000 ee03fc00 ee189f54 ee189f18 c0060284 c005fd9c > c1033e04 c0d48010 > [ 10.217264] 9f20: ee188000 c10e5bb9 00000000 00000000 ee0b7400 ee188000 > ee0b5f80 c0060224 > [ 10.225473] 9f40: 00000000 00000000 ee189fac ee189f58 c00664a8 c0060230 > 00000000 2dd1a000 > [ 10.233683] 9f60: ee0b5f80 00000000 00000000 ee189f6c ee189f6c 00000000 > 00000000 ee189f7c > [ 10.241892] 9f80: ee189f7c dc8ba66e c00747b4 ee0b7400 c0066390 00000000 > 00000000 00000000 > [ 10.250101] 9fa0: 00000000 ee189fb0 c0010ef8 c006639c 00000000 00000000 > 00000000 00000000 > [ 10.258310] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 00000000 > [ 10.266518] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 > 00000000 08000000 > [ 10.274732] [<c0676368>] (n_tty_receive_buf_common) from [<c0676d70>] > (n_tty_receive_buf2+0x24/0x2c) > [ 10.283903] [<c0676d70>] (n_tty_receive_buf2) from [<c067aa4c>] > (flush_to_ldisc+0xf0/0x13c) > [ 10.292290] [<c067aa4c>] (flush_to_ldisc) from [<c005fee4>] > (process_one_work+0x154/0x494) > [ 10.300588] [<c005fee4>] (process_one_work) from [<c0060284>] > (worker_thread+0x60/0x548) > [ 10.308712] [<c0060284>] (worker_thread) from [<c00664a8>] > (kthread+0x118/0x130) > [ 10.316140] [<c00664a8>] (kthread) from [<c0010ef8>] > (ret_from_fork+0x14/0x3c) > [ 10.323392] Code: e50b2030 e50b3034 eb10e2f3 e51b3044 (e5930248) > [ 10.329557] ---[ end trace 406ed7c803d6bcc7 ]--- > > [ 10.335007] Unable to handle kernel paging request at virtual address > ffffffec > > > Somebody reported a similar issue here: > > > https://e2e.ti.com/support/arm/sitara_arm/f/791/t/657207. > > In reading this thread from E2E, TI had suggested to upgrade to a later > SDK, and I wasn't 100% clear on whether the person who posted the post > actually tried upgrading. One of the TI employees suggested that upgrading > from the 4.4.32 kernel to the 4.9.59 kernel could be related to the crash. > > > Our console image consists of the following: > > debian@BeagleBoard-X15:/$ uname -r > 4.4.110-ti-r142 > > debian@BeagleBoard-X15:/$ cat /etc/debian_version > 8.10 > > debian@BeagleBoard-X15:/$ cat /etc/dogtag > BeagleBoard.org Debian Image 2018-01-01 > > > > I have some basic questions related to this issue: > > > 1) Have you seen this before on the BB-X15? Was it an intermittent > problem? If you've seen this, what's the cause and resolution? > > 2) Does the kernel message, [ 10.017747] Modules linked in: > snd_soc_simple_card etnaviv snd_soc_omap_hdmi_audio ftdi_sio usbseris, > mean that the problem is contained or enountered in only these modules? > > 3) Once my kernel crashes/panics/OOPS's, is there a good way to get > further information about the crash, post-mortem? For instance, does the > kernel still update files in the filesystem which can be examined on the SD > card after the crash? > > > Thanks in advance! > > Jeff > -- 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/1712b038-bfda-4827-a489-a48b48da47f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
