lkml.org 
[lkml]   [2000]   [Feb]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: One more boobytrap needed for 2.2.15pre ?
Date
On Wed, 16 Feb 2000, Manfred Spraul wrote:
>
> Alan Cox wrote:
> >
> > > Ok, but now the question is: which interrupt changes current->state? Perhaps
> > > a special boobytrap in the interrupt handlers could detect that?
> >
> > Numerous interrupt handlers change task->state. Every interrupt handler that
> > does a wake_up_interruptible() for example. It could easily be 'current'
> >
> I've written such a bobbytrap, it's attached. I'm using it right now,
> but as I've expected, I receive no messages. Either a specific hardware
> driver calls "__set_current_state()/ set_current_state()/
> current->state==NULL", or my theory is wrong.
>
> Andris, could you apply my patch, and check if it reports any messages?
>
> --
> Manfred

Applied patch, built kernel and got error messages
'do_IRQ: bad state change in bh'
in average once per minute in first about 10 minutes minutes uptime:

Andris


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.104 / U:0.560 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site