From owner-freebsd-bugs Wed Oct 25 11:15:25 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9F06837B479; Wed, 25 Oct 2000 11:15:23 -0700 (PDT) Received: (from johan@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA39538; Wed, 25 Oct 2000 11:15:23 -0700 (PDT) (envelope-from johan@FreeBSD.org) Date: Wed, 25 Oct 2000 11:15:23 -0700 (PDT) From: Message-Id: <200010251815.LAA39538@freefall.freebsd.org> To: ahlberg@fairytale.se, johan@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/21970: Kernel panic when trying to access a UDMA100 harddisk Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: Kernel panic when trying to access a UDMA100 harddisk State-Changed-From-To: feedback->closed State-Changed-By: johan State-Changed-When: Wed Oct 25 11:12:56 PDT 2000 State-Changed-Why: The submitter says: From: "Daniel Ahlberg" To: Subject: Re: kern/21970: Kernel panic when trying to access a UDMA100 harddisk Date: Wed, 25 Oct 2000 10:06:29 +0200 > I also belive the output from a verbose boot will be good > to have. > This can be found in /var/run/dmesg.boot after a > verbose boot. I'd wish to cancel this bug, becuse I can't reproduce it. I had to use another computer for our fileserver, and the new one is working with the UDMA 100 controller. I'm almost sure that it is something wrong with the motherboard, the box began to crash after a couple of days uptime. Thanks for the quick answer. http://www.freebsd.org/cgi/query-pr.cgi?pr=21970 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message