Re: deadc0de panic in unmount()

From: Kris Kennaway (kris_at_obsecurity.org)
Date: 12/26/04

  • Next message: Greg 'groggy' Lehey: "Re: deadc0de panic in unmount()" 
    Date: Sat, 25 Dec 2004 16:22:34 -0800
To: Greg 'groggy' Lehey <grog@FreeBSD.org>

    On Sun, Dec 26, 2004 at 10:45:50AM +1030, Greg 'groggy' Lehey wrote:
    > On Saturday, 25 December 2004 at 15:42:36 -0800, Kris Kennaway wrote:
    > > -current from a few days ago. It was probably unmounting a nullfs,
    > > devfs or linprocfs.
    > >
    > > panic(c06f100c,63676b70,c06efede,e4,c06f4bb5) at panic+0xac
    > > _mtx_lock_spin(deadc0de,0,c06efede,e4,c06f9e60) at _mtx_lock_spin
    > > lockmgr(c59df420,10007,c077c480,ca6e1000,379) at lockmgr+0x132
    > > dounmount(c59df400,8080000,ca6e1000,379,734ff58) at dounmount+0xa5
    > > unmount(ca6e1000,f13a6d14,8,e,2) at unmount+0x1f4
    > > syscall(2f,2f,2f,82ff704,8573911) at syscall+0x13b
    > > Xint0x80_syscall() at Xint0x80_syscall+0x1f
    > > --- syscall (22, FreeBSD ELF32, unmount), eip = 0x82a21df, esp = 0xbfbfe0ac, ebp = 0xbfbfe168 ---
    >
    > Do you have a dump?

    No, dumping is broken for me on this and some other machines (it
    starts with 'Dumping 2047 MB' but immediately returns).

    Kris

  • Next message: Greg 'groggy' Lehey: "Re: deadc0de panic in unmount()"

    Relevant Pages