Date: Tue, 18 Mar 1997 20:52:17 -0400 (AST) From: The Hermit Hacker <scrappy@hub.org> To: Bruce Evans <bde@zeta.org.au> Cc: imp@village.org, current@freebsd.org Subject: Re: 2.2 Kernel Unstable Message-ID: <Pine.BSF.3.95.970318204909.215k-100000@thelab.hub.org> In-Reply-To: <199703190029.LAA28501@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Mar 1997, Bruce Evans wrote: > Recursive panics became normal with the Lite2 merge. sync() in panic() > has never run in the quite the right context, and now that there is a > lot more locking in sync(), the panic sync() is likely to stumble over > a lock, especially if the first panic was for a lock. Panics aren't > much more common than before the merge. > Okay, but this doesn't quite explain why a kernel (2.2, not 3.0) from around Feb 7th causes a SegFault, while a kernel generated by the 2.2-RELEASE source tree causes a system reboot... I can live with the SegFault's, and know *why* those are happening, so I'm not suggesting that those are a result of a bug in the kernel...what I am wondering is what changed so that MemFaults(aka SegFaults) are causing a system reboot instead of just causing an error... That would be like a GPF in MicroSloth causing a reboot instead of a GPF, no?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970318204909.215k-100000>