This happened to a box I left running fuzz tests over the holidays.
schedule_timeout: wrong timeout value fffffffffffffff0 Pid: 6606, comm: trinity-child1 Not tainted 3.8.0-rc1+ #43 Call Trace: [<ffffffff81698415>] schedule_timeout+0x305/0x340 [<ffffffff8169ae82>] ? preempt_schedule+0x42/0x60 [<ffffffff8169cb65>] ? _raw_spin_unlock_irqrestore+0x75/0x80 [<ffffffff810dc461>] audit_log_start+0x311/0x470 [<ffffffff8106c62c>] ? __rcu_read_unlock+0x5c/0xa0 [<ffffffff81086120>] ? try_to_wake_up+0x320/0x320 [<ffffffff810e0d0b>] audit_log_exit+0x4b/0xfb0 [<ffffffff81156e1b>] ? vm_mmap_pgoff+0x8b/0xb0 [<ffffffff810b2342>] ? get_lock_stats+0x22/0x70 [<ffffffff810b27ae>] ? put_lock_stats.isra.23+0xe/0x40 [<ffffffff810b2ecb>] ? lock_release_holdtime.part.24+0xcb/0x130 [<ffffffff81075f93>] ? up_write+0x23/0x40 [<ffffffff81156e1b>] ? vm_mmap_pgoff+0x8b/0xb0 [<ffffffff816a4afc>] ? sysret_signal+0x5/0x47 [<ffffffff810e3d3f>] __audit_syscall_exit+0x25f/0x2c0 [<ffffffff816a4bad>] sysret_audit+0x17/0x21 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
