Messages in this thread |  | | | Date | Fri, 30 Jan 2004 02:08:39 +0100 | | From | Daniel Andersen <> | | Subject | Re: 2.6.2-rc2-mm1 (Breakage?) |
| |
> > > Hello, Andrew, I've switched from 2.6.2-rc1-mm1 to 2.6.2-rc1-mm1, and I've > > > encountered this: > > > > > [snip] > > > > Decided to build my first kernel with preempt since the early 2.5 days. I'm > > seeing the same warnings in 2.6.2-rc2-mm1. > > > > gkrellm 0 waking gkrellm: 897 1485 > > Badness in try_to_wake_up at kernel/sched.c:722 > > Call Trace: > > [<c011a6a7>] try_to_wake_up+0x97/0x1d0 > > [<c011b0b0>] __wake_up_common+0x30/0x60 > > [<c011b109>] __wake_up+0x29/0x50 > > [<c0131f1b>] wake_futex+0x2b/0x70 > > [<c013259a>] do_futex+0x3fa/0x6e0 > > [<c011d9d0>] copy_process+0x7b0/0x10a0 > > [<c011e3a9>] do_fork+0xe9/0x179 > > [<c011a142>] schedule+0x1d2/0x640 > > [<c0132988>] sys_futex+0x108/0x130 > > [<c03e1b9e>] sysenter_past_esp+0x43/0x65 > > > > Every five seconds. This is when it reads the sensor information from /sys, I > > think. And during boot, similar messages to those already reported (from > > kern.log this time). > >
As Zephaniah E. Hull suggested earlier, the message will disappear by reverting this patch:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2.6.2-rc2-mm1/broken-out/futex-wakeup-debug.patch
Daniel Andersen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |