From owner-freebsd-stable  Thu Oct 31 20: 2:41 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7C17237B401
	for <freebsd-stable@freebsd.org>; Thu, 31 Oct 2002 20:02:40 -0800 (PST)
Received: from forrie.ne.client2.attbi.com (forrie.ne.client2.attbi.com [24.147.156.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B15ED43E77
	for <freebsd-stable@freebsd.org>; Thu, 31 Oct 2002 20:02:39 -0800 (PST)
	(envelope-from forrie@forrie.com)
Received: from workstation.forrie.com (i-21.forrie.net. [192.168.1.21])
            by forrie.ne.client2.attbi.com with id gA142Vp12279;
            Thu, 31 Oct 2002 23:02:31 -0500 (EST)
Message-Id: <5.1.1.6.2.20021031230137.01ff0440@192.168.1.1>
X-Sender: forrie@192.168.1.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Thu, 31 Oct 2002 23:02:30 -0500
To: "Daniel O'Connor" <doconnor@gsoft.com.au>,
	freebsd-stable@freebsd.org
From: Forrest Aldrich <forrie@forrie.com>
Subject: Re: Unrecognized CPU Class (and a disc error)
In-Reply-To: <1036123245.1736.148.camel@chowder.localdomain>
References: <5.1.1.6.2.20021031225359.01fd6ea0@192.168.1.1>
 <5.1.1.6.2.20021031223636.01fdb7c0@192.168.1.1>
 <5.1.1.6.2.20021031225359.01fd6ea0@192.168.1.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG


>I believe FreeBSD probes the drives independently from the BIOS..
>
>I had a problem where I plugged a 2.5" HD in via an adapter and it was
>being detected as a UDMA66 drive when it only did UDMA33 and got a
>similar error to yours.
[ ... ]

I'll go in to the data center tomorrow and check the cables and BIOS -- I'm 
sure they were okay.

If this is a FreeBSD error (and I'm not certain yet) - what was your fix 
for this - will this cause problems with the system?


Thanks alot,
Forrest


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