From owner-freebsd-stable  Mon Mar 20 10:44:18 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 417B337B961
	for <FreeBSD-STABLE@FreeBSD.ORG>; Mon, 20 Mar 2000 10:44:16 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA27216;
	Mon, 20 Mar 2000 10:44:31 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Matt Heckaman <matt@ARPA.MAIL.NET>
Cc: FreeBSD-STABLE <FreeBSD-STABLE@FreeBSD.ORG>
Subject: Re: Some observations on 4.0-release and 4.0-stable 
In-reply-to: Your message of "Mon, 20 Mar 2000 12:09:17 EST."
             <Pine.BSF.4.21.0003201159280.17426-100000@epsilon.lucida.qc.ca> 
Date: Mon, 20 Mar 2000 10:44:31 -0800
Message-ID: <27213.953577871@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> * ad driver giving me some problems, I think. I had originally two disks
>   under 3.4 which ere wd0 and wd1, (wd0s1,wd1s1) The first disk was
>   handle perfectly under ad0, the second however blows up hard, and I'm
>   not sure why. Here's the dmesg relative and the error;

This is a known bug and something I'm actually re-rolling the 4.0
RELEASE over now.  Soren just fixed it, and I consider this bug bad
enough to merit a re-roll.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message