), sentence "if (td->td_flags & TDF_TIMEOUT) {...}"
> > is to check this race condition.
> >
> > -David Xu
> >
> > - Original Message -
> > From: "Matthew Dillon" <[EMAIL PROTECTED]>
> > To: "Julian Elisch
an Elischer" <[EMAIL PROTECTED]>
> Cc: "Steve Kargl" <[EMAIL PROTECTED]>; "walt"
> <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Monday, July 01, 2002 4:43 AM
> Subject: KSE / interrupt panic
>
>
> >Got another one.
t; <[EMAIL PROTECTED]>; "walt"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 01, 2002 4:43 AM
Subject: KSE / interrupt panic
>Got another one. Different panic, same place.
>
> panic: setrunqueue: bad thread state
> cpuid = 0; lapic.id = 01
Got a weird one. No backtrace. gdb got confused and wouldn't attach
properly.
-Matt
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 0100
fault virtual address = 0xd0c45a
fault code = supervisor write, page
On Sun, 30 Jun 2002, Matthew Dillon wrote:
>Got another one. Different panic, same place.
>
> panic: setrunqueue: bad thread state
> cpuid = 0; lapic.id = 0100
> Debugger("panic")
> Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0
> db> trace
> Debugger(c02ec2ba) at Debugger
:others have seen this one too
:and the common element is that it's always in
:setrunqueue() called from an interrupt.
:it is also often via cv_*SOMETHING*()
:
:I Thought we had cleared these up but apparently not :-/
:
There are a bunch of wakeup race conditions in the CV code where
the
others have seen this one too
and the common element is that it's always in
setrunqueue() called from an interrupt.
it is also often via cv_*SOMETHING*()
I Thought we had cleared these up but apparently not :-/
On Sun, 30 Jun 2002, Matthew Dillon wrote:
>Got another one. Different panic,
Got another one. Different panic, same place.
panic: setrunqueue: bad thread state
cpuid = 0; lapic.id = 0100
Debugger("panic")
Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c02ec2ba) at Debugger+0x46
panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at p
