On Tue, Jun 19, 2012 at 09:30:59PM -0400, Steve Wills wrote:
Hi,
I just got a panic out of my r237195 system. The panic looks like:
Sleeping thread (tid 173153, pid 42034) owns a non-sleepable lock
KDB: stack backtrace of thread 173153:
sched_switch() at sched_switch+0x28a
mi_switch() at
On Tuesday, June 19, 2012 9:30:59 pm Steve Wills wrote:
Hi,
I just got a panic out of my r237195 system. The panic looks like:
Sleeping thread (tid 173153, pid 42034) owns a non-sleepable lock
KDB: stack backtrace of thread 173153:
sched_switch() at sched_switch+0x28a
mi_switch() at
On Wed, Jun 20, 2012 at 08:19:39AM -0400, John Baldwin wrote:
On Tuesday, June 19, 2012 9:30:59 pm Steve Wills wrote:
Hi,
I just got a panic out of my r237195 system. The panic looks like:
Sleeping thread (tid 173153, pid 42034) owns a non-sleepable lock
KDB: stack backtrace of
On 06/20/2012 08:25, Konstantin Belousov wrote:
On Wed, Jun 20, 2012 at 08:19:39AM -0400, John Baldwin wrote:
On Tuesday, June 19, 2012 9:30:59 pm Steve Wills wrote:
Hi,
I just got a panic out of my r237195 system. The panic looks like:
Sleeping thread (tid 173153, pid 42034) owns a
Hi,
I just got a panic out of my r237195 system. The panic looks like:
Sleeping thread (tid 173153, pid 42034) owns a non-sleepable lock
KDB: stack backtrace of thread 173153:
sched_switch() at sched_switch+0x28a
mi_switch() at mi_switch+0xdf
sleepq_timedwait() at sleepq_timedwait+0x3a
_sleep()