Two repeatable panics on CURRENT

[Andrew Duane]

It drops into KDB (with a mostly garbage backtrace). I think I will turn WITNESS off for now.... 


/Andrew
 

-----Original Message-----
From: juli at clockworksquid.com [mailto:juli at clockworksquid.com] On Behalf Of Juli Mallett
Sent: Friday, May 20, 2011 1:53 PM
To: Andrew Duane
Cc: mips at freebsd.org
Subject: Re: Two repeatable panics on CURRENT

On Fri, May 20, 2011 at 10:46, Andrew Duane <aduane at juniper.net> wrote:
> I'm almost finished bringing up -CURRENT on my octeon blade, but have two perfectly repeatable panics that I could use some help sorting out.
> [...]
> Also, when I halt the system:
>
>        Waiting (max 60 seconds) for system process `vnlru' to stop...done
>        Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
>        Waiting (max 60 seconds) for system process `syncer' to stop...
>        Syncing disks, vnodes remaining...0 0 timed out
>        All buffers synced.
>        2: lock order reversal:
>        0  1st 0x9800000001e23bd8 ufs (ufs) @ /aduane/FreeBSDCurrent/src/sys/kern/vfs_mount.c:1190 3
>        2nd 0x9800000001eaa458 devfs (devfs) @ /aduane/FreeBSDCurrent/src/sys/kern/vfs_subr.c:0 2134
>
> This is with WITNESS turned on. I may turn it off for now, but does someone know about this?

Does the system actually panic after that?  That reversal is, I think,
at least very close to being harmless.