Date: Sun, 18 Feb 2001 14:12:53 -0600 From: Mike Meyer <mwm@mired.org> To: Matt Dillon <dillon@earth.backplane.com> Cc: stable@FreeBSD.ORG Subject: Re: Suggestions for diagnosing lockups Message-ID: <14992.11461.884930.102242@guru.mired.org> In-Reply-To: <200102182008.f1IK87k31550@earth.backplane.com> References: <14991.58225.783986.487533@guru.mired.org> <200102181936.f1IJanm31380@earth.backplane.com> <14992.9931.334001.521780@guru.mired.org> <200102182008.f1IK87k31550@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matt Dillon <dillon@earth.backplane.com> types: > I dunno. I think we won't know until you manage to get the broken > into DDB. From there you should be able to do a 'trace' and a 'ps' > to hopefully see where things have locked up. If you have setup a > dump device & swap, you should also be able to 'panic' the kernel from DDB > and get a core dump. I'm looking for hints on how to do that. The first freeze - with X left running - didn't respond to Control-Alt-Escape. That's why I asked if X had known interactions with DDB. On further thought, it might be a problem with stealing the console. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14992.11461.884930.102242>