kernel panic on Rpi3B

[rhagu]

Hello,

today I ran my raspberry pi b3 for the first time as a logging device with adb logcat and two android devices attached. htop showed cpu usage at approximately 5%. When I came back after an hour all I could see was a kernel panic message in the command line. I would like to find out what caused the kernel panic (maybe the amount of data piped from usb to sd card?).

How can I search journalctl for the necessary logs?

kind regards,
rhagu

[rhagu]

I found the kernel panic:
$this->bbcode_second_pass_code('', '
Jun 02 23:23:10 alarm kernel: Unable to handle kernel paging request at virtual address 00302033302d3630
Jun 02 23:23:10 alarm kernel: Mem abort info:
Jun 02 23:23:10 alarm kernel: ESR = 0x96000004
Jun 02 23:23:10 alarm kernel: Exception class = DABT (current EL), IL = 32 bits
Jun 02 23:23:10 alarm kernel: SET = 0, FnV = 0
Jun 02 23:23:10 alarm kernel: EA = 0, S1PTW = 0
Jun 02 23:23:10 alarm kernel: Data abort info:
Jun 02 23:23:10 alarm kernel: ISV = 0, ISS = 0x00000004
Jun 02 23:23:10 alarm kernel: CM = 0, WnR = 0
Jun 02 23:23:10 alarm kernel: [00302033302d3630] address between user and kernel address ranges
Jun 02 23:23:10 alarm kernel: Internal error: Oops: 96000004 [#1] SMP
Jun 02 23:23:10 alarm kernel: Modules linked in: vc4 microchip btsdio brcmfmac cec rc_core lan78xx brcmutil drm_kms_helper drm hci_uart btqca drm_panel_orientation_quirks syscopyarea sysfillrect sysimgbl>
Jun 02 23:23:10 alarm kernel: Process <-111231d4eacb4 (pid: 1183, stack limit = 0x0000000004400ad8)
Jun 02 23:23:10 alarm kernel: CPU: 1 PID: 1183 Comm: <-111231d4eacb4 Tainted: G C 5.1.5-2-ARCH #1
Jun 02 23:23:10 alarm kernel: Hardware name: Raspberry Pi 3 Model B+ (DT)
Jun 02 23:23:10 alarm kernel: pstate: 40000005 (nZcv daif -PAN -UAO)
Jun 02 23:23:10 alarm kernel: pc : __kmalloc+0xac/0x290
Jun 02 23:23:10 alarm kernel: lr : __kmalloc+0x1e4/0x290
Jun 02 23:23:10 alarm kernel: sp : ffff000012b2bba0
Jun 02 23:23:10 alarm kernel: x29: ffff000012b2bba0 x28: 0000000000000000
Jun 02 23:23:11 alarm kernel: x27: ffff000012b2bd40 x26: ffff800035804c00
Jun 02 23:23:11 alarm kernel: x25: 0000ffffa8010c58 x24: ffff800035803980
Jun 02 23:23:11 alarm kernel: x23: ffff800035803980 x22: ffff0000109c4cd4
Jun 02 23:23:11 alarm kernel: x21: 0000000000000200 x20: 0000000000000cc0
Jun 02 23:23:11 alarm kernel: x19: 38302033302d3630 x18: 0000000000000000
Jun 02 23:23:11 alarm kernel: x17: 0000000000000000 x16: 0000000000000000
Jun 02 23:23:11 alarm kernel: x15: 0000000000000000 x14: 0000000000000000
Jun 02 23:23:11 alarm kernel: x13: 0000000000000000 x12: 0000000000000000
Jun 02 23:23:11 alarm kernel: x11: 0000000000000000 x10: 0000000000000000
Jun 02 23:23:11 alarm kernel: x9 : 0000000000000000 x8 : ffff800035804c80
Jun 02 23:23:11 alarm kernel: x7 : 0000000000000000 x6 : ffff80002b020720
Jun 02 23:23:11 alarm kernel: x5 : 0000000000000000 x4 : ffff0000119978d0
Jun 02 23:23:11 alarm kernel: x3 : ffff800035fc8da0 x2 : 000000000003bc8e
Jun 02 23:23:11 alarm kernel: x1 : 0000000000000000 x0 : ffff000011689da0
Jun 02 23:23:11 alarm kernel: Call trace:
Jun 02 23:23:11 alarm kernel: __kmalloc+0xac/0x290
Jun 02 23:23:11 alarm kernel: proc_do_submiturb+0xd0c/0xed8
Jun 02 23:23:11 alarm kernel: usbdev_do_ioctl+0xc20/0x18e8
Jun 02 23:23:11 alarm kernel: usbdev_ioctl+0x34/0x48
Jun 02 23:23:11 alarm kernel: do_vfs_ioctl+0xc4/0x880
Jun 02 23:23:11 alarm kernel: ksys_ioctl+0x84/0xb8
Jun 02 23:23:11 alarm kernel: __arm64_sys_ioctl+0x28/0x38
Jun 02 23:23:11 alarm kernel: el0_svc_handler+0x90/0x118
Jun 02 23:23:11 alarm kernel: el0_svc+0x8/0xc
Jun 02 23:23:11 alarm kernel: Code: f94002e0 b94022e1 f2400c1f 54000b81 (f8616a63)
Jun 02 23:23:11 alarm kernel: ---[ end trace d66749b6caf4d86b ]---
')

Does someone have an idea what might have caused it?

kind regards,
rhagu

[lategoodbye]

Maybe you should try to figure out:
- which Android device trigger this panic (try to reduce your setup)
- is there a specific action on the Android device which triggers the panic
- are you able to trigger this panic with an older kernel 5.0.x