Re: sysctl lock, system lockup
From: Tim Robbins (tim_at_robbins.dropbear.id.au)
Date: 05/31/04
- Previous message: Peter Schuller: "config/kernel version mismatch after cvsup"
- In reply to: Don Bowman: "RE: sysctl lock, system lockup"
- Next in thread: Don Bowman: "RE: sysctl lock, system lockup"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 31 May 2004 11:16:50 +1000 To: Don Bowman <don@sandvine.com>
On Sun, May 30, 2004 at 04:35:55PM -0400, Don Bowman wrote:
> From: Don Bowman [mailto:don@sandvine.com]
> > On the console i ran 'top', but it wouldn't start,
> > giving:
> >
> > load: 0.00 cmd: top 4282 [sysctl lock] 0.00u 0.00s 0% 180k
> >
> > as the status. I can't ^C it, can't ssh in.
> > can still ping the device.
> >
> > It was doing a backgound fsck from an earlier hang.
> >
> > i have called panic from db, not sure if the core will
> > work properly or not.
>
> As a followup... i did get a vmcore, and matching kernel.debug,
> if someone can suggest what i might look @?
print sysctllock (or just sysctllock.sx_xholder if you don't have a
serial console set up.)
Tim
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Peter Schuller: "config/kernel version mismatch after cvsup"
- In reply to: Don Bowman: "RE: sysctl lock, system lockup"
- Next in thread: Don Bowman: "RE: sysctl lock, system lockup"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
