From owner-freebsd-stable  Wed May  3  9:11:52 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.campbell-mithun.com (Mercury.campbell-mithun.com [192.159.32.151])
	by hub.freebsd.org (Postfix) with ESMTP
	id 541A837BBC2; Wed,  3 May 2000 09:11:49 -0700 (PDT)
	(envelope-from swb@grasslake.net)
Received: from marlowe (Marlowe.campbell-mithun.com [192.159.32.184])
	by mercury.campbell-mithun.com (8.9.1a/8.9.1) with SMTP id LAA11763;
	Wed, 3 May 2000 11:11:48 -0500
Message-ID: <009a01bfb51a$5442bbe0$b8209fc0@marlowe>
From: "Shawn Barnhart" <swb@grasslake.net>
To: "Mike Smith" <msmith@FreeBSD.ORG>
Cc: <freebsd-stable@FreeBSD.ORG>
References: <200004302232.PAA03609@mass.cdrom.com> <005101bfb456$02d20a50$b8209fc0@marlowe> <005201bfb507$9703cb30$b8209fc0@marlowe>
Subject: Re: HPDA/DAC960PL errors
Date: Wed, 3 May 2000 11:12:07 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG




| Well, perhaps not.  Running the old firmware, 2.39, my install of 4.0
fails
| early on copying files:
|
| bus_dmamap_load : Too many segs!  buf_len = 0x10000
| mlx0 : I/O error -- attempt to write beyond end of drive
|
| Any idea what these mean?
|
| I flashed it with the newest Mylex firmware rev, 2.73, and tried the
install
| again, and got the same errors. I've redefined and am reinitializing the
| array as we speak -- perhaps the existing RAID 5 configuration was bad.

Well, I'm about to give up on the Mylex adapter.  I've: updated to 2.73
firmware, reconfigured and reinitialized the array using Mylex DOS config
program; I can format, copy to, and boot off of a DOS partition; newfs the
drive during FBSD install, but once copying commences it just falls apart
with multiple repititons of the above error and then hangs up.

The kernel I'm using was built on a machine cvsup'd to 4.0-STABLE last
Thursday.

I noticed someone else with the same problem with 4.0-CURRENT in Deja News
but their threading of usenet mailing list echos is terrible, so its hard
for me to tell if it actually got fixed.





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