From owner-freebsd-bugs Tue Feb 22 12:30: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 29D9137B705 for ; Tue, 22 Feb 2000 12:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA06777; Tue, 22 Feb 2000 12:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 22 Feb 2000 12:30:03 -0800 (PST) Message-Id: <200002222030.MAA06777@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Lew Payne Subject: Re: kern/16890: Fatal trap 12: page fault while in kernel mode (panic: sbdrop) Reply-To: Lew Payne Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/16890; it has been noted by GNATS. From: Lew Payne To: freebsd-gnats-submit@FreeBSD.org, lew@persiankitty.com Cc: Subject: Re: kern/16890: Fatal trap 12: page fault while in kernel mode (panic: sbdrop) Date: Tue, 22 Feb 2000 12:25:48 -0800 (old): --- special victim's note --- Spoke with Chris of cdrom.com, and learned about the "triple curse" involving our Intel chipset, the built-in DE0 and NCR controller. We've eliminated the DE0, and installed a TX0. Problem persists. (Correction): I meant to say "FXP0" instead of "DE0". (Addition): Problem persists, even after recompiling the kernel with "fxp0" commented out (so the driver is completely removed). Out of desperation, I tried that this morning. Still crash city, and a lot of screwed up disk structures (using soft updates). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message