On 28-Jul-2003 Kris Kennaway wrote:
> One of the alpha package machines just died with the following:
>
> panic: sleeping thread owns a mutex
> panic() at panic+0x160
> propagate_priority() at propagate_priority+0x148
> _mtx_lock_sleep() at _mtx_lock_sleep+0x264
> _mtx_lock_flags() at _mtx_lock_f
--On Wednesday, November 20, 2002 10:12 PM -0800 Steve Kargl
<[EMAIL PROTECTED]> wrote:
On Wed, Nov 20, 2002 at 09:59:32PM -0800, Joel M. Baldwin wrote:
--On Wednesday, November 20, 2002 9:47 PM -0800 Nate Lawson
<[EMAIL PROTECTED]> wrote:
> Wow, I haven't seen so many panics from one person b
On Wed, Nov 20, 2002 at 09:59:32PM -0800, Joel M. Baldwin wrote:
>
> --On Wednesday, November 20, 2002 9:47 PM -0800 Nate Lawson
> <[EMAIL PROTECTED]> wrote:
>
> >Wow, I haven't seen so many panics from one person before. Tried
> >memtest86.com yet?
> >
>
> yes, LONG before I posted the first t
yes, LONG before I posted the first time. I've even swaped
the memory from another system. The problem ISN'T the memory.
--On Wednesday, November 20, 2002 9:47 PM -0800 Nate Lawson
<[EMAIL PROTECTED]> wrote:
Wow, I haven't seen so many panics from one person before. Tried
memtest86.com yet?
Wow, I haven't seen so many panics from one person before. Tried
memtest86.com yet?
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--On Wednesday, November 20, 2002 2:27 PM -0500 John Baldwin
<[EMAIL PROTECTED]> wrote:
On 20-Nov-2002 Joel M. Baldwin wrote:
--On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson
<[EMAIL PROTECTED]> wrote:
On Wed, 20 Nov 2002, Robert Watson wrote:
Hmm. Another thread has decided to
--On Wednesday, November 20, 2002 2:27 PM -0500 John Baldwin
<[EMAIL PROTECTED]> wrote:
On 20-Nov-2002 Joel M. Baldwin wrote:
--On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson
<[EMAIL PROTECTED]> wrote:
On Wed, 20 Nov 2002, Robert Watson wrote:
Hmm. Another thread has decide
On Wed, 20 Nov 2002, John Baldwin wrote:
> Erm. Did you manage to look at dmesg then? If so, you would have seen
> warnings from WITNESS earlier about the locks messing up. If you can
> reproduce this and are letting it sit unattended, a better plan might be
> to turn on witness_ddb (it's a ke
On 20-Nov-2002 Joel M. Baldwin wrote:
> --On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson
> <[EMAIL PROTECTED]> wrote:
>
>> On Wed, 20 Nov 2002, Robert Watson wrote:
>>
>>> Hmm. Another thread has decided to sleep while holding an inpcb
>>> mutex. Any chance this can be reproduced
On Wed, 20 Nov 2002, Joel M. Baldwin wrote:
> --On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson
> <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 20 Nov 2002, Robert Watson wrote:
> >
> >> Hmm. Another thread has decided to sleep while holding an inpcb
> >> mutex. Any chance this can be
--On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson
<[EMAIL PROTECTED]> wrote:
On Wed, 20 Nov 2002, Robert Watson wrote:
Hmm. Another thread has decided to sleep while holding an inpcb
mutex. Any chance this can be reproduced while running WITNESS? If
so, you should get a panic ea
On Wed, 20 Nov 2002, Robert Watson wrote:
> Hmm. Another thread has decided to sleep while holding an inpcb mutex.
> Any chance this can be reproduced while running WITNESS? If so, you
> should get a panic earlier when the other thread sleeps in the first
> place. The easiest way to do that is
Hmm. Another thread has decided to sleep while holding an inpcb mutex.
Any chance this can be reproduced while running WITNESS? If so, you
should get a panic earlier when the other thread sleeps in the first
place. The easiest way to do that is if you can reproduce the panic with
WITNESS. If y
On 20-Nov-2002 Joel M. Baldwin wrote:
>
> Under heavy system load and heavy swapping I had the following
> panic occur.
Unfortunately with this panic by the time you get to it it is too
late to see what the original cause was. If you use WITNESS then
WITNESS will catch the original problem and
On 11-Nov-2002 Kris Kennaway wrote:
> I just got this on a Nov 1 current kernel:
>
> panic: sleeping thread owns a mutex
> Debugger("panic")
> Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
> db> bt
> No such command
> db> trace
> Debugger(c04038ad,c047e2c0,c0402a36,d928bb80,1) at Deb
15 matches
Mail list logo