Bugzilla bug - No response

[Nick Barr]

Hi,

I filed a bug report back in June and wondered if any progress has been 
made in identifying the problem? Also what does the error message mean 
"Badness in interruptible_sleep_on_timeout at kernel/sched.c"? i.e. What 
does "Badness" mean?

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127018

------
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
  [<02281cc0>] interruptible_sleep_on_timeout+0x5d/0xb1
  [<02115e4e>] default_wake_function+0x0/0xc
  [<02239cd5>] netdev_run_todo+0x22/0x1ac
  [<06881d8f>] rtl8139_thread+0x38/0x134 [8139too]
  [<06881d57>] rtl8139_thread+0x0/0x134 [8139too]
  [<021041d9>] kernel_thread_helper+0x5/0xb

I already upgraded from the stock kernel from the CD distribution.

Version-Release number of selected component (if applicable):

kernel-utils-2.4-9.1.131
kernel-2.6.6-1.435

How reproducible:

Every minute. Every time I boot.

I have googled/searched bugzilla and found a couple of similar issues
but these were for a different module and different versions and I did
not think they were appropriate. These were for #116864 and #125482.

Do I need to upgrade the kernel further. If so where would I find such
a kernel?
------

Thanks

Nick

[Satish Balay]

On Thu, 19 Aug 2004, Nick Barr wrote:
> Hi,
>
> I filed a bug report back in June and wondered if any progress has been made
> in identifying the problem? Also what does the error message mean "Badness in
> interruptible_sleep_on_timeout at kernel/sched.c"? i.e. What does "Badness"
> mean?
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127018
>
> 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
>  [<02281cc0>] interruptible_sleep_on_timeout+0x5d/0xb1
>  [<02115e4e>] default_wake_function+0x0/0xc
>  [<02239cd5>] netdev_run_todo+0x22/0x1ac
>  [<06881d8f>] rtl8139_thread+0x38/0x134 [8139too]
>  [<06881d57>] rtl8139_thread+0x0/0x134 [8139too]
>  [<021041d9>] kernel_thread_helper+0x5/0xb
>
> I already upgraded from the stock kernel from the CD distribution.
>
> Version-Release number of selected component (if applicable):
>
> kernel-utils-2.4-9.1.131
> kernel-2.6.6-1.435
>
> How reproducible:
>
> Every minute. Every time I boot.
>
> I have googled/searched bugzilla and found a couple of similar issues
> but these were for a different module and different versions and I did
> not think they were appropriate. These were for #116864 and #125482.
>
> Do I need to upgrade the kernel further. If so where would I find such
> a kernel?

There is a testing kernel 521 - which you might want to try - and update
bugzilla with its results.

Satish

[Nick Barr]

Nick Barr wrote:
> Hi,
>
> I filed a bug report back in June and wondered if any progress has been 
> made in identifying the problem? Also what does the error message mean 
> "Badness in interruptible_sleep_on_timeout at kernel/sched.c"? i.e. What 
> does "Badness" mean?
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127018
>
> 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
>  [<02281cc0>] interruptible_sleep_on_timeout+0x5d/0xb1
>  [<02115e4e>] default_wake_function+0x0/0xc
>  [<02239cd5>] netdev_run_todo+0x22/0x1ac
>  [<06881d8f>] rtl8139_thread+0x38/0x134 [8139too]
>  [<06881d57>] rtl8139_thread+0x0/0x134 [8139too]
>  [<021041d9>] kernel_thread_helper+0x5/0xb
>
> I already upgraded from the stock kernel from the CD distribution.
>
> Version-Release number of selected component (if applicable):
>
> kernel-utils-2.4-9.1.131
> kernel-2.6.6-1.435
>
> How reproducible:
>
> Every minute. Every time I boot.
>
> I have googled/searched bugzilla and found a couple of similar issues
> but these were for a different module and different versions and I did
> not think they were appropriate. These were for #116864 and #125482.
>
> Do I need to upgrade the kernel further. If so where would I find such
> a kernel?
>
> Thanks
>
> Nick

Hi,

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
  [<0211a8ee>] default_wake_function+0x0/0xc
  [<022f4c1a>] __cond_resched+0x14/0x3b
  [<022a00ef>] netdev_run_todo+0x29/0x2c1
  [<06897e41>] rtl8139_thread+0x38/0x134 [8139too]
  [<06897e09>] rtl8139_thread+0x0/0x134 [8139too]
  [<021041d9>] kernel_thread_helper+0x5/0xb

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?

TIA

Nick

[Tom Mitchell]

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.