Hey Guys
I have a strange problem with the handling of my custom cape on the BBB. My cape don't have a EEPROM because it's a prototype. The first error appears in the capemanager: [ 0.718342] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI) [ 0.727943] bone-capemgr bone_capemgr.9: slot #6: Failed verification After the boot and log in and after ~60sec, a new error message appears and the BBB is in a faultstate (it crashes and doing nothing): root@beaglebone:~# [ 120.521224] INFO: task kworker/u:1:21 blocked for more than 60 seconds. [ 120.528386] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 120.536854] Kernel panic - not syncing: hung_task: blocked tasks [ 120.543292] [<c00114f1>] (unwind_backtrace+0x1/0x9c) from [<c04c9cfd>] (panic+0x59/0x15c) [ 120.552003] [<c04c9cfd>] (panic+0x59/0x15c) from [<c0073955>] (watchdog+0x19d/0x1c0) [ 120.560262] [<c0073955>] (watchdog+0x19d/0x1c0) from [<c00454eb>] (kthread+0x6b/0x78) [ 120.568610] [<c00454eb>] (kthread+0x6b/0x78) from [<c000c8fd>] (ret_from_fork+0x11/0x34) *My questions are:* - what the trigger of the second error message is? - What is the kworker/u:1:21? - Is the first error message relevant? - How can I fix this trouble? - How does the BBB detecting Capes (to understand which Pin could interrupt)? Thanks for your help! Dave In the Picture (attachement) you can see the pinout of P8 and P9. <https://lh6.googleusercontent.com/-YiFo-Dd2K8k/VHiHhCT1BgI/AAAAAAAAB_I/kop5mQn7Qg8/s1600/SCH_Snip.JPG> -- 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/d/optout.
