On Tue, Oct 22, 2013 at 09:15:45PM -0400, Keith White wrote:
> On Wed, 23 Oct 2013, Mateusz Guzik wrote:
>
> >On Tue, Oct 22, 2013 at 07:59:29PM -0400, Keith White wrote:
> >>I get a "gnop lock" panic when trying to create a gnop device:
> >>
> >># gnop create -S 4k ada3
> >>
> >>panic: lock "
On Wed, 23 Oct 2013, Mateusz Guzik wrote:
On Tue, Oct 22, 2013 at 07:59:29PM -0400, Keith White wrote:
I get a "gnop lock" panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock "gnop lock" 0xf80002566640 already initialized
# kgdb /boot/kernel.r256923/k
On Tue, Oct 22, 2013 at 07:59:29PM -0400, Keith White wrote:
> I get a "gnop lock" panic when trying to create a gnop device:
>
> # gnop create -S 4k ada3
>
> panic: lock "gnop lock" 0xf80002566640 already initialized
>
>
> # kgdb /boot/kernel.r256923/kernel /var/crash/vmcore.last
> .
I get a "gnop lock" panic when trying to create a gnop device:
# gnop create -S 4k ada3
panic: lock "gnop lock" 0xf80002566640 already initialized
# kgdb /boot/kernel.r256923/kernel /var/crash/vmcore.last
...
Unread portion of the kernel message buffer:
panic: lock "gnop lock" 0xff
The box itself is a dual P2-450, and I was attempting to rebuild a KDE
library (ah the joys of doing that), and monitoring stuff with top. The
first odd thing I noticed was that some of the processes showed up with an
state field (namely sed, and a few others I think). Eventually the box
panic'd
