System unresponsive

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

System unresponsive

Post by johnvick »

Got up today the cloudshell display on my XU4 gave a number of error messages that were hard to decipher on the small screen.

Couldn't log in by SSH. A power cycle got it going.

An email from Wordpress Jetpack told me a site running on the device went down at 4:39.

This is the first time I have had a crash on a dieti system - any idea why this occurred?

Here is an excerpt from syslog:

Jul 28 04:34:42 Odroid kernel: [153832.061030] [c0] ------------[ cut here ]------------
Jul 28 04:34:42 Odroid kernel: [153832.063548] [c0] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x25c/0x27c()
Jul 28 04:34:42 Odroid kernel: [153832.065836] [c0] NETDEV WATCHDOG: eth1 (r8152): transmit queue 0 timed out
Jul 28 04:34:42 Odroid kernel: [153832.067769] [c0] Modules linked in: xt_multiport iptable_filter ip_tables nfsv3 nfsd nfs_acl rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 nfs lockd sunrpc dns_resolver cdc_ether usbnet r8152 ina231_sensor i2c_s3c2410 fb_ili9340 fbtft_device fbtft syscopyarea sysfillrect sysimgblt fb_sys_fops ads7846 spidev spi_s3c64xx fuse
Jul 28 04:34:42 Odroid kernel: [153832.076083] [c0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.96+ #1
Jul 28 04:34:42 Odroid kernel: [153832.077912] [c0] Backtrace:
Jul 28 04:34:42 Odroid kernel: [153832.079024] [c0] [<c0012bf0>] (dump_backtrace+0x0/0x114) from [<c0012f10>] (show_stack+0x20/0x24)
Jul 28 04:34:42 Odroid kernel: [153832.081347] [c0] r6:c05277ec r5:00000009 r4:c0903ce0 r3:00000000
Jul 28 04:34:42 Odroid kernel: [153832.084625] [c0] [<c0012ef0>] (show_stack+0x0/0x24) from [<c0610a94>] (dump_stack+0x20/0x28)
Jul 28 04:34:42 Odroid kernel: [153832.090408] [c0] [<c0610a74>] (dump_stack+0x0/0x28) from [<c002ddd4>] (warn_slowpath_common+0x5c/0x7c)
Jul 28 04:34:42 Odroid kernel: [153832.097523] [c0] [<c002dd78>] (warn_slowpath_common+0x0/0x7c) from [<c002deb0>] (warn_slowpath_fmt+0x40/0x48)
Jul 28 04:34:42 Odroid kernel: [153832.104548] [c0] r8:c09040c0 r7:dc502214 r6:dd276b00 r5:dc502000 r4:00000000
Jul 28 04:34:42 Odroid kernel: [153832.104548] r3:00000009
Jul 28 04:34:42 Odroid kernel: [153832.107491] [c0] [<c002de70>] (warn_slowpath_fmt+0x0/0x48) from [<c05277ec>] (dev_watchdog+0x25c/0x27c)
Jul 28 04:34:42 Odroid kernel: [153832.110095] [c0] r3:dc502000 r2:c0856fa4
Jul 28 04:34:42 Odroid kernel: [153832.111267] [c0] [<c0527590>] (dev_watchdog+0x0/0x27c) from [<c003dd24>] (call_timer_fn+0x84/0x1b4)
Jul 28 04:34:42 Odroid kernel: [153832.113578] [c0] [<c003dca0>] (call_timer_fn+0x0/0x1b4) from [<c003ea54>] (run_timer_softirq+0x1a8/0x280)
Jul 28 04:34:42 Odroid kernel: [153832.116405] [c0] [<c003e8ac>] (run_timer_softirq+0x0/0x280) from [<c0036a7c>] (__do_softirq+0xf0/0x2a0)
Jul 28 04:34:42 Odroid kernel: [153832.119208] [c0] [<c003698c>] (__do_softirq+0x0/0x2a0) from [<c0036d08>] (do_softirq+0x5c/0x68)
Jul 28 04:34:42 Odroid kernel: [153832.121513] [c0] [<c0036cac>] (do_softirq+0x0/0x68) from [<c0036fc0>] (irq_exit+0xa4/0xdc)
Jul 28 04:34:42 Odroid kernel: [153832.123769] [c0] r4:c0902000 r3:00000002
Jul 28 04:34:42 Odroid kernel: [153832.124978] [c0] [<c0036f1c>] (irq_exit+0x0/0xdc) from [<c000f294>] (handle_IRQ+0x4c/0xa4)
Jul 28 04:34:42 Odroid kernel: [153832.125997] [c3] fb_ili9340 spi1.0: I/O Error: rx-0 tx-1 res:rx-p tx-f len-4096
Jul 28 04:34:42 Odroid kernel: [153832.126069] [c3] fb_ili9340 spi1.0: fbtft_update_display: write_vmem failed to update display buffer
Jul 28 04:34:42 Odroid kernel: [153832.131663] [c0] r4:c08ff2ec r3:00000217
Jul 28 04:34:42 Odroid kernel: [153832.132884] [c0] [<c000f248>] (handle_IRQ+0x0/0xa4) from [<c0008558>] (gic_handle_irq+0x38/0x6c)
Jul 28 04:34:42 Odroid kernel: [153832.135161] [c0] r6:c0903e90 r5:c090b31c r4:f000200c r3:00000010
Jul 28 04:34:42 Odroid kernel: [153832.136989] [c0] [<c0008520>] (gic_handle_irq+0x0/0x6c) from [<c000e4c0>] (__irq_svc+0x40/0x70)
Jul 28 04:34:42 Odroid kernel: [153832.139213] [c0] Exception stack(0xc0903e90 to 0xc0903ed8)
Jul 28 04:34:42 Odroid kernel: [153832.140848] [c0] 3e80: 00000000 5798e2a2 01cf4cec 00073d33
Jul 28 04:34:42 Odroid kernel: [153832.143095] [c0] 3ea0: c1df1480 00000000 c1df1480 c0913418 c0dba668 c0913418 00000000 c0903efc
Jul 28 04:34:42 Odroid kernel: [153832.145279] [c0] 3ec0: 00000000 c0903ed8 c0082d74 c0026a54 60000013 ffffffff
Jul 28 04:34:42 Odroid kernel: [153832.147461] [c0] r7:c0903ec4 r6:ffffffff r5:60000013 r4:c0026a54
Jul 28 04:34:42 Odroid kernel: [153832.149231] [c0] [<c0026a18>] (exynos_enter_idle+0x0/0x70) from [<c0460cec>] (cpuidle_enter_state+0x4c/0x100)
Jul 28 04:34:42 Odroid kernel: [153832.152052] [c0] r5:00008be8 r4:ce433233
Jul 28 04:34:42 Odroid kernel: [153832.153235] [c0] [<c0460ca0>] (cpuidle_enter_state+0x0/0x100) from [<c0460e64>] (cpuidle_idle_call+0xc4/0x244)
Jul 28 04:34:42 Odroid kernel: [153832.156123] [c0] r7:00000000 r6:c0902000 r5:00000000 r4:c1df1480
Jul 28 04:34:42 Odroid kernel: [153832.157864] [c0] [<c0460da0>] (cpuidle_idle_call+0x0/0x244) from [<c000f794>] (arch_cpu_idle+0x18/0x48)
Jul 28 04:34:42 Odroid kernel: [153832.160552] [c0] [<c000f77c>] (arch_cpu_idle+0x0/0x48) from [<c0081fd8>] (cpu_startup_entry+0x74/0x240)
Jul 28 04:34:42 Odroid kernel: [153832.163349] [c0] [<c0081f64>] (cpu_startup_entry+0x0/0x240) from [<c06086ac>] (rest_init+0xc4/0xec)
Jul 28 04:34:42 Odroid kernel: [153832.165624] [c0] r7:ffffffff r3:c0902000
Jul 28 04:34:42 Odroid kernel: [153832.166854] [c0] [<c06085e8>] (rest_init+0x0/0xec) from [<c0897aec>] (start_kernel+0x2dc/0x338)
Jul 28 04:34:42 Odroid kernel: [153832.169087] [c0] r6:c08d5af8 r5:00000000 r4:c090ae00
Jul 28 04:34:42 Odroid kernel: [153832.170766] [c0] [<c0897810>] (start_kernel+0x0/0x338) from [<40008074>] (0x40008074)
Jul 28 04:34:42 Odroid kernel: [153832.173032] [c0] ---[ end trace e2a916c89f0622f0 ]---
Jul 28 04:34:42 Odroid kernel: [153832.174703] [c0] r8152 6-1:1.0 eth1: Tx timeout
Jul 28 04:34:42 Odroid kernel: [153832.316214] [c0] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
Jul 28 04:34:42 Odroid kernel: [153832.331369] [c0] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
Jul 28 04:34:42 Odroid kernel: [153832.334484] [c0] xhci-hcd xhci-hcd.5.auto: xHCI xhci_drop_endpoint called with disabled ep ddcf6f00
Jul 28 04:34:42 Odroid kernel: [153832.336797] [c0] xhci-hcd xhci-hcd.5.auto: xHCI xhci_drop_endpoint called with disabled ep ddcf6f2c
Jul 28 04:34:42 Odroid kernel: [153832.339166] [c0] xhci-hcd xhci-hcd.5.auto: xHCI xhci_drop_endpoint called with disabled ep ddcf6f58
Jul 28 04:39:01 Odroid CRON[3727]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Jul 28 04:39:01 Odroid CRON[3729]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Jul 28 05:09:01 Odroid CRON[4272]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Jul 28 05:09:01 Odroid CRON[4273]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
User avatar
Fourdee
Site Admin
Posts: 2787
Joined: Tue Feb 06, 2007 1:36 pm

Re: System unresponsive

Post by Fourdee »

johnvick wrote:Got up today the cloudshell display on my XU4 gave a number of error messages that were hard to decipher on the small screen.

Couldn't log in by SSH. A power cycle got it going.
Hi John,

I've not experienced a hard lockup on my XU4 yet, it runs 24/7. So its most likely hardware related (eg: PSU/SD). If this occurs again, take a picture of the screen. Although its small, it should give us the last error before the lock up and clues.
This is the first time I have had a crash on a dieti system - any idea why this occurred?
The main points are:

3.2 panel failed to update. I/O and/or memory issue (bad connection from ribbon cable etc)

Code: Select all

Jul 28 04:34:42 Odroid kernel: [153832.125997] [c3] fb_ili9340 spi1.0: I/O Error: rx-0 tx-1 res:rx-p tx-f len-4096
Jul 28 04:34:42 Odroid kernel: [153832.126069] [c3] fb_ili9340 spi1.0: fbtft_update_display: write_vmem failed to update display buffer
Not sure if this is normal for USB devices, but could indicate a temporary disconnect.

Code: Select all

Jul 28 04:34:42 Odroid kernel: [153832.316214] [c0] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
If i remember correctly:
- You have both USB3 ports on the device connected? I'am just wondering if they are hitting above 900ma and not getting enough power.
- Did you also upgrade your PSU?
- Which SDcard or EMMC are you using?
If you find our project or support useful, then we’d really appreciate it if you’d consider contributing to the project however you can.
Donating is the easiest – you can use PayPal or become a DietPi patron.
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

Re: System unresponsive

Post by johnvick »

Hi Fourdee,

I use an old 2GB SD to boot from, the FS is on an intel 120 GB SSD and the second USB 3 port has a USB 3 16 GB flash drive that receives a daily FS backup y rsync. I have an aftermarket 6A PSU.

Thanks again for your assistance.
Post Reply