In message <[EMAIL PROTECTED]>, ryan beasley writes:
>
>panic: lockmgr: draining against myself
I've just checked in revision 1.426 of vfs_subr.c which may solve
this, but I was not able to reproduce it myself. Could you or anybody
else who has seen this panic try the above revi
s0: on dc0
ukphy0: on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: failed to force tx and rx to idle state
dc0: failed to force tx and rx to idle state
panic: lockmgr: draining against myself
panic: from debugger
Uptime: 1m30s
Dumping 64 MB
ata0: resetting devices ..
Got another panic with a Sat Dec 21 11:00 PST 2002 kernel:
GNU gdb 5.2.1 (FreeBSD)
This GDB was configured as "i386-undermydesk-freebsd"...
(kgdb) core-file /var/crash/vmcore.1
panic: lockmgr: draining against myself
panic messages:
---
panic: lockmgr: draining against myself
cpuid = 1
On Thu, Apr 18, 2002 at 11:25:10AM +0900, Jun Kuriyama wrote:
>
> This is today's kernel. Should I test with -DDEBUG_LOCKS?
I'm seeing this again
panic: lockmgr: draining against myself
syncing disks... panic: bwrite: buffer is not busy???
Uptime: 22m5s
I was doing a build
I just got the same panic on my -current box from yesterday, also:
crash1# panic: lockmgr: draining against myself
cpuid = 0; lapic.id =
Debugger("panic")
Stopped at Debugger+0x41: xorl%eax,%eax
db> trace
Debugger(c03dd41a) at Debugger+0x41
panic(c03dadc0,c9f35c30
This is today's kernel. Should I test with -DDEBUG_LOCKS?
-
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugger("panic")
Stopped at Debugger+0x41: xorl%eax,%eax
db> trace
Debugger(c029d1ba) at Debugger+0x41
panic(c029ae60,e908e78
heads up, was just able to recreate it with a simple 'make
> install' ... didn't need the -j16 to do it ...
>
> On Sat, 7 Apr 2001, The Hermit Hacker wrote:
>
> >
> > doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
>
just as a heads up, was just able to recreate it with a simple 'make
install' ... didn't need the -j16 to do it ...
On Sat, 7 Apr 2001, The Hermit Hacker wrote:
>
> doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
> with:
>
doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
with:
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugging("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Stopped at DEbuger+0x46: pushl %ebx
trace shows
