the same here.. rev A5A with angstrom as provided by factory. using a stress program that read/write on the nand and is ok I leave the board running it for weeks.. and it is ok.. If I login to ssh and ask for something else .. bang.. let's see similar panic messages..
I stopped the porting of my application to the new BBB even if it is cheaper and has better performance because of this, can anyone help or anyone knows about some fix of this in newer kernels? On Saturday, November 2, 2013 7:19:13 AM UTC+1, Peedro A. Melendez (lazychino) wrote: > > I'm getting something like that on angstrom too, you guys have an idea of > how to fix it??? > > this is the error: > > [ 120.198907] INFO: task mmcqd/0:74 blocked for more than 60 seconds. > [ 120.205540] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables > this message. > [ 120.213773] Kernel panic - not syncing: hung_task: blocked tasks > [ 120.220067] [<c001051d>] (unwind_backtrace+0x1/0x8c) from [<c0373a01>] > (panic+0x55/0x14c) > [ 120.228631] [<c0373a01>] (panic+0x55/0x14c) from [<c00617b3>] > (watchdog+0x153/0x1a0) > [ 120.236740] [<c00617b3>] (watchdog+0x153/0x1a0) from [<c003ca4b>] > (kthread+0x61/0x72) > [ 120.244938] [<c003ca4b>] (kthread+0x61/0x72) from [<c000c6fd>] > (ret_from_fork+0x11/0x34) > > > On Sunday, May 5, 2013 1:58:36 PM UTC-4, ChuckM wrote: >> >> Robert, I don't know if you're reading but I love your work on getting >> Ubuntu running on the Beaglebone Black, I've been playing with the latest >> release and have discovered that when ever it gets significant disk load (I >> can do this reliably with an apt-get update) I get a panic like so: >> >> [ 900.821426] INFO: task mmcqd/0:69 blocked for more than 60 seconds. >> [ 900.828175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" >> disables this message.ot >> [ 900.837171] Kernel panic - not syncing: hung_task: blocked tasks >> [ 900.843545] [<c0013538>] (unwind_backtrace+0x0/0xe0) from [<c05a55ac>] >> (panic+0x84/0x1e0) >> [ 900.852182] [<c05a55ac>] (panic+0x84/0x1e0) from [<c00921b8>] >> (watchdog+0x1d4/0x234)yslog >> [ 900.860359] [<c00921b8>] (watchdog+0x1d4/0x234) from [<c0058728>] >> (kthread+0xa0/0xb0)ot >> [ 900.868629] [<c0058728>] (kthread+0xa0/0xb0) from [<c000d8f8>] >> (ret_from_fork+0x14/0x3c) >> [ 900.877152] drm_kms_helper: panic occurred, switching back to text >> console >> >> And well, it doesn't really switch back to a text console, perhaps it >> does but my debug port serial cable isn't having it switch back it goes >> dead. Reboot, it fixes up the root partition and crashes again, reboot >> again and it comes up multi user. >> >> Presumably it is deadlocking somewhere in the mmcq part of the world. I >> don't have a cross compilation environment up yet, its on my list. >> >> --Chuck >> >> >> -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
