Date: Fri, 07 May 1999 15:00:48 -0700 From: David Greenman <dg@root.com> To: Cliff Skolnick <cliff@steam.com> Cc: Mike Tancsa <mike@sentex.net>, freebsd-stable@FreeBSD.ORG Subject: Re: Strange reboot saga Message-ID: <199905072200.PAA20019@implode.root.com> In-Reply-To: Your message of "Fri, 07 May 1999 14:39:43 PDT." <Pine.BSF.4.10.9905071429260.505-100000@lazlo.internal.steam.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>My deadlock problems started with a cvsup a little over a week ago, and many >others also noted that the problem started in april. Before that, my 3.1 >system was rock solid. It's either a VM problem or a CAM problem by how the >system responds to pings for a bit, but no disk acces can be done. No >console messages, the machine is a server and not running X. > >Perhaps something bad got checked in in April, this weekend I'm going to >spend some time looking a what actually changed that month. > >I'm also a little alarmed about how many people are rationalizing this and >attacking the posters of lockup problems. Many posters have stated that >there sysem was stable with 2.2 or an earlier version of 3.1, please don't >discount that. This is -stable, not -advocacy. > >QUESTION FOR THE GURUS > >I'd love to get a system snapshot or something while the kernel is still >running. Is there a way to do this once the disk system is out to lunch? >Hints? Put DDB into your kernel. When the system hangs, enter the debugger with ctrl-printsceen. You can then use the 'ps', 'trace', and 'panic' commands. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com 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?199905072200.PAA20019>