After yesterday compiling app-misc/byobu-5.5 today i got oops in dmesg. Reproducible: Always Steps to Reproduce: 1. emerge byobu 2. run byobu 3. dmesg after few hours Actual Results: INFO: task byobu-status:17613 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. byobu-status D c05a1d73 0 17613 17611 0x00000000 ddc039b0 00000086 cf12c3c0 c05a1d73 00800000 c88f0c70 d3e844c0 000044c0 ddc03d20 bdcf2c24 0000220c 000044c0 000044c0 ddc03d20 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Call Trace: [<c05a1d73>] ? selinux_inode_permission+0xf3/0x150 [<c085e966>] ? __mutex_lock_slowpath+0xa6/0x100 [<c085e59d>] ? mutex_lock+0x1d/0x40 [<c0532799>] ? do_lookup+0x249/0x360 [<c05338c9>] ? path_lookupat+0xa9/0x700 [<c0533f4a>] ? do_path_lookup+0x2a/0xf0 [<c0534fd3>] ? user_path_at_empty+0x43/0x80 [<c0503465>] ? handle_mm_fault+0x125/0x1e0 [<c0535028>] ? user_path_at+0x18/0x20 [<c052b164>] ? vfs_fstatat+0x44/0x80 [<c052b1d8>] ? vfs_stat+0x18/0x20 [<c052b5df>] ? sys_stat64+0xf/0x30 [<c0862880>] ? vmalloc_fault+0x1d0/0x1d0 [<c0866270>] ? sysenter_do_call+0x12/0x28 Expected Results: No oops in dmesg
Looks like a kernel problem.
Hello I got this kernel for 2 weeks on 12 servers and working with no problem Mon Jan 9 07:06:25 2012 >>> sys-kernel/hardened-sources-3.1.5 But like i say after yesterday compiling Mon Jan 23 10:01:04 2012 >>> app-misc/byobu-5.5 got this information in dmesg... I know this is oops... but strange for 2 weeks working with no problem and after yesterday compiling new version of byobu got information: INFO: task byobu-status:17613 blocked for more than 120 seconds. For me looks strange ;-)
Can't do anything with this info