Date: Mon, 31 May 2004 11:16:50 +1000 From: Tim Robbins <tim@robbins.dropbear.id.au> To: Don Bowman <don@sandvine.com> Cc: "'current@freebsd.org'" <current@freebsd.org> Subject: Re: sysctl lock, system lockup Message-ID: <20040531011650.GA12944@cat.robbins.dropbear.id.au> In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C85337051D8DEA@mail.sandvine.com> References: <FE045D4D9F7AED4CBFF1B3B813C85337051D8DEA@mail.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040531011650.GA12944>