+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: General Discussion on ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=86)
+--- Thread: Kernel Panic on Rock64 linux (/showthread.php?tid=5011)
Pages:
1
2
RE: Kernel Panic on Rock64 linux - tanisou - 08-25-2017
Ok,Thank you!
RE: Kernel Panic on Rock64 linux - xshunin - 08-26-2017
Hi,
I also get kernel panics on every distribution I tried (and I tried nearly all), I tried two different SD cards (only have two).
I could get to run an Android build though. I checked for solder bridges but I coudn't find any. Anything else I can try? (I have the 4gb model)
RE: Kernel Panic on Rock64 linux - ayufan - 08-29-2017
Try different SD card, it is likely that your SD is just broken.
RE: Kernel Panic on Rock64 linux - polartx - 09-01-2017
getting the same error. Rock64 4gig version. Multiple memory cards, multiple build OSes
RE: Kernel Panic on Rock64 linux - tllim - 09-03-2017
(09-01-2017, 07:45 AM)polartx Wrote: getting the same error. Rock64 4gig version. Multiple memory cards, multiple build OSes
Please check whether stock Android build also has the memory crash issue. If still getting Kernel Panic, please file a support ticket at support.pine64.org
RE: Kernel Panic on Rock64 linux - rmbusy - 09-09-2017
I saw a kernel panic w/ xenial-minimal-rock64-0.4.17-85-arm64.img after I unplugged a USB 3.0 hard disk (nothing was mounted on it). Seems like the OS thought it was still connected.
[ 7800.498794] INFO: task parted:5470 blocked for more than 120 seconds.
[ 7800.499779] Not tainted 4.4.70-rockchip-ayufan-85 #1
[ 7800.500569] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 7800.502124] Kernel panic - not syncing: hung_task: blocked tasks
[ 7800.502998] CPU: 3 PID: 29 Comm: khungtaskd Not tainted 4.4.70-rockchip-ayufan-85 #1
[ 7800.504105] Hardware name: PINE64 ROCK64 (DT)
Playing with jessie-minimal-rock64-0.5.7-101-arm64.img now, and don't see the same issue. It does take several seconds for it to decide the USB device is no longer available when I unplugged the cable. Nothing was active when the cable was unplugged, it just spewed the following to the console :
[ 873.393783] usb usb5-port1: Cannot enable. Maybe the USB cable is bad?
[ 873.394805] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ 873.395754] usb usb5-port1: cannot disable (err = -32)
[ 875.910788] usb usb5-port1: Cannot enable. Maybe the USB cable is bad?
[ 875.911801] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ 875.912735] usb usb5-port1: cannot disable (err = -32)
[ 878.426774] usb usb5-port1: Cannot enable. Maybe the USB cable is bad?
[ 878.427787] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ 878.428729] usb usb5-port1: cannot disable (err = -32)
[ 880.943791] usb usb5-port1: Cannot enable. Maybe the USB cable is bad?
[ 880.944809] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ 880.945741] usb usb5-port1: cannot disable (err = -32)
[ 880.946543] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[ 880.947492] usb usb5-port1: cannot disable (err = -32)
[ 880.948328] scsi host0: uas_post_reset: alloc streams error -19 after reset
[ 880.952607] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Edit: Looks like the latest jessie minimal also panics after disconnecting USB 3.0 device. Filed a issue on github, with ayufan (not sure if it was the right project page though).