Date: Tue, 1 Feb 2000 09:00:53 -0700 From: Bob Kot <bobkat@azstarnet.com> To: "Matthew N. Dodd" <winter@jurai.net> Cc: freebsd-bugs@FreeBSD.ORG, imp@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: i386/14030: aha0 probe fails 3.3.0-RELEASE install with DTC3290 EISA SCSI Message-ID: <00020109301200.00299@atlas.tic.toc> References: <Pine.BSF.4.21.0001311958540.479-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Jan 2000, you wrote:
> I've reviewed the PR trail.
>
> Can you try increasing the length of the timeout for the Diag. Start loop
> under -CURRENT?
No can do under -CURRENT this machine does not have enough resources to
support -CURRENT in addition to 3.3-Release which I do not want to
remove until 4.0's actual release.
I will help or test anything I can but it will have to be under
3.3-Release. If you read the PR trail I tested that loop and recorded
the values of status (all of them). The very 1st one is 0x30 as are all
susequent values. This is an acceptable status for the subsequent while
loop that tests for valid ready status HA_READY. Which lets the
ahareset() function proceed.
I took a peek at /sys//dev/aha/aha.c 1.34 and all this looks the same.
I will repeat this if you think it will help. What is an acceptable
time out value?
Bob
> > Any chance this PR will be fixed prior to impending 4.0 release.
> >
> > This problem is a time consuming impediment for installation, and I want
> > to put 4.0 on a machine with this controller as soon as it is released.
> >
> > One possible fix (mine) is on the PR audit trail. A pre-4.0 release
> > resolution/commit would be much appreciated.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00020109301200.00299>