From owner-freebsd-bugs@FreeBSD.ORG Sat Mar 29 22:17:38 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E58A37B401 for ; Sat, 29 Mar 2003 22:17:38 -0800 (PST) Received: from web21106.mail.yahoo.com (web21106.mail.yahoo.com [216.136.227.108]) by mx1.FreeBSD.org (Postfix) with SMTP id E168643FB1 for ; Sat, 29 Mar 2003 22:17:37 -0800 (PST) (envelope-from materribile@yahoo.com) Message-ID: <20030330061737.33533.qmail@web21106.mail.yahoo.com> Received: from [165.247.29.125] by web21106.mail.yahoo.com via HTTP; Sat, 29 Mar 2003 22:17:37 PST Date: Sat, 29 Mar 2003 22:17:37 -0800 (PST) From: Mark Terribile To: freebsd-bugs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Incompatibility: FreeBSD 4.6 scroggs Abit kd7 mobo -- reproducible! X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2003 06:17:39 -0000 (Please note that I cannot use send-pr(1) because FreeBSD has scrogged my motherboard and I now have no FreeBSD system! Yes, the problem is reproducible, at about $100 the pop!) Originator: Mark Terribile Organization: Confidential: No Synopsis: FreeBSD 4.6 boot -c operations wipe Abit kd7 BIOS Severity: Medium Priority: Medium (as a code fix; should be High as a doc fix!) Category: i386 Class: sw-bug Release: 4.6 Environment: A new machine with a Abit Kd7 motherboard, an Athlon XP 2700+ processor (NOT overclocked) and 4x512 MB of memory. Also an Adaptec SCSI controller, which does not appear to be part of the problem (see below). Description: During the boot -c process, the kernel reports an interrupt conflict between three network interfaces. (The motherboard has one on it; I had no others installed.) With all three disabled, FreeBSD ran well for several days on the hardware. In attempting to find the right driver for the hardware I activated the one that looked likely (ie. not the StarLan!) (sorry, reproducing this costs $100 the trial, plus the time to order the new board) and the kernel reported an addressing error and panic'd. Attempting to reboot produced no result; the machine was unresponsive. It appeared that the motherboard BIOS was wiped or damaged. I followed the procedure Abit gives for resetting the CMOS configuration on the board, but there was no change in the board's behavior. How-to-repeat: As above. This procedure effectively destroys a motherboard! Mark Terribile __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com