On Thu, Sep 02, 2004 at 05:21:03PM +0100, Nick Barr wrote: > Nick Barr wrote: > > >I filed a bug report back in June and wondered if .... > >------ > >Getting the following trace on the console of a freshly installed > >Fedora Core 2 box. > > > >Badness in interruptible_sleep_on_timeout at kernel/sched.c:2533 .... > >kernel-2.6.6-1.435 .... > >Do I need to upgrade the kernel further. If so where would I find such > >a kernel? .... > I have since upgraded the kernel to kernel-2.6.8-1.521 and I still get > the notice up on the console. > > Badness in interruptible_sleep_on_timeout at kernel/sched.c:2545 > [<022f47ef>] interruptible_sleep_on_timeout+0x5d/0x23a .... > Any more ideas anyone? Or can people point me to a place to look for > information? Do I need to get in contact with the kernel developers at all? You should do a simple "add information" to the existing bug that you are running a new kernel (what ever it is) and still see the problem. Also be clear if this causes you a problem or if you are only seeing the console message. My guess is that a driver or other module is behaving badly once and a failsafe timeout is putting things right. Since failsafe code should never run that might be the 'Badness' that the message is reporting. You can look at kernel source to verify my speculation. Perhaps this is happening when kudzu and friends are inspecting hardware to see if something has changed. Is kudzu running? Check by: $ chkconfig --list | grep kud kudzu 0:off 1:off 2:off 3:on 4:on 5:on 6:off Does the error go away if you $ chkconfig kudzu off $ reboot Does it return if you $ chkconfig kudzu on $ reboot i.e. try and isolate the bootstrap and boot step where this happens. You can also offer to add specific information as requested to the bug. Stuff like hardware inventory, kernel modules inventory. -- T o m M i t c h e l l Just say no to 74LS73 in 2004
