The following reply was made to PR kern/166568; it has been noted by GNATS.

From: Andriy Gapon <[email protected]>
To: Oliver Pinter <[email protected]>, [email protected]
Cc:  
Subject: Re: kern/166568: [sched_ule] intr stuck in WAIT state
Date: Mon, 02 Apr 2012 12:10:58 +0300

 on 02/04/2012 11:21 Oliver Pinter said the following:
 > Hi!
 > 
 > Today night have I more time to play with this issue (DDB, kgdb..) .
 > At this time the machine running on non-debug kernel, and the symptom
 > are only to see, that the [intr] kernel process stucked in WAIT state
 > and the load are constantly near 1.00 no others are visible.
 > The machine is a HP 5310m laptop with core2duo CPU - P9400.
 > 
 > The fast solution are reverting the commit, that I previously reported.
 > 
 > When you have some suggestion what must check, than feel free to say.
 
 Basically I don't understand what you mean by "stuck in WAIT state".
 What's so bad about the WAIT state in your opinion?  Why being in that state
 implies being "stuck"?
 As far as I understand it's a normal state for the interrupt threads when they
 are not servicing any interrupts.  Do you have a different understanding?
 
 
 > On 4/2/12, Andriy Gapon <[email protected]> wrote:
 >> The following reply was made to PR kern/166568; it has been noted by GNATS.
 >>
 >> From: Andriy Gapon <[email protected]>
 >> To: [email protected], [email protected]
 >> Cc:
 >> Subject: Re: kern/166568: [sched_ule] intr stuck in WAIT state
 >> Date: Mon, 02 Apr 2012 10:17:35 +0300
 >>
 >>  Apologies, but could you please be a little bit less terse in describing
 >> what
 >>  problem you are reporting?
 >>
 >>  --
 >>  Andriy Gapon
 >> _______________________________________________
 >> [email protected] mailing list
 >> http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 >> To unsubscribe, send any mail to "[email protected]"
 >>
 
 
 -- 
 Andriy Gapon
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[email protected]"

Reply via email to