Date: Wed, 19 Apr 2000 00:37:08 -0500 From: Steve Cahill <nonymous@concentric.net> To: Doug Ledford <dledford@redhat.com>, "aic7xxx FreeBSD.ORG" <AIC7xxx@FreeBSD.ORG> Cc: niessene@natlab.research.philips.com Subject: (update) Re: 2.2.X+scsi+ide=timeout mystery Message-ID: <38FD4604.755CBEC8@concentric.net> References: <388BF45A.2836F5DC@concentric.net> <388BA47A.681A1F87@redhat.com> <388C0101.16509F80@concentric.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--------------4C43C28BEFEFA1928E72FE9A
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi Doug,
I am finally unsubscribing from aic7xxx. I've been subscribing since I
first sent this to you/aic7xxx on 1/24/00 :-)
I was hoping someone would have a similar problem, but never saw a
similar posting.
I finally broke down and bought a new EIDE (UDMA) disk a-la-COMPUSA
(really it is a MAXTOR 15GB UDMA33/66 for a measley $99.95 :-)
Well this fixed the kernel timeouts that I was getting with the Western
Digital 6.4GB UDMA drives I had (both 26400 & 36400).
Conclusions:
=========
1) This was not a Motherboard BIOS problem specific to the PA-2013
2) Very unlikely a kernel or driver problem although it was not
exhibited in the 2.0.3X kernels
3) Not a problem specific to just any generic UDMA EIDE hard drive
when mixed with my scsi (this is what I feared most!)
4) Most likely it is attributable to the BIOS on the WD hard drive
itself causing a BUS (or communication) problem with the
IDE controller and/or Adaptec SCSI BIOS
Anyway, I am happy that I can use this new drive with a little more
space than I had before and with the newer kernels.
Thanks for your help and your advise.
Regards,
--Steve Cahill
Steve Cahill wrote:
> Hi Doug,
>
> Recall I upgraded to the 2.2.14 kernel and even applied your patch
> <aic7xxx-5.1.22.patch> for the most recent driver and it did not cure
> the problem?
>
> --Steve
>
>
> Doug Ledford wrote:
>
>>
>
> We had a machine in here in the test lab with the same problem. After
>
> upgrading the kernel to a 2.2.14 or later kernel, the problem
> myseriously went
> away. We attribute it to IDE changes in the 2.2.14 kernel patch.
> But, I'm
> not an IDE expert....
>
>
>
>> Steve Cahill wrote:
>> >
>> > Well Folks,
>> >
>> > This one is a real mystery.....
>> >
>> > I cannot believe that my setup is unique, but hey... stranger
>> things can
>> > happen I suppose. I have an Adaptec AHA-2940U2W with several
>> devices ( see
>> > 2.0.38 dmesg out below), and an IDE primary drive where my boot
>> record lives
>> > with a (bootable) DOS partition as well as some other Linux
>> partitions:
>> >
>> > hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
>> > hda: WDC AC26400B, 6149MB w/512kB Cache, CHS=784/255/63
>> >
>> > My main (mother) board is an FIC PA-2013 with a 350MHz AMD K6-2
>> > CPU, Millenium G200 video adapter, 128MB (PC100) SDRAM, sound card
>> and modem
>> > reside in the 2 ISA slots and a 3COM 3c905B Cyclone ethernet card
>> in one of
>> > the PCI slots.
>> > (aka very typical setup??)
>> >
>> > When booting any Linux 2.2.X kernel with this IDE drive present I
>> get a
>> > timeout message (which I have posted before, but will include here
>> for
>> > completeness):
>> >
>> > scsi : aborting command due to timeout : pid 60, scsi0, channel 0,
>> id 1, lun
>> > 0 0x28 00 00 70 c2 ce 00 00 02 00
>> >
>> > The timeout can last anywhere from 25 to 40 seconds. Another
>> symptom is
>> > LILO will hang (i.e. executing lilo) or take a very long time to
>> execute.
>> >
>> > When I boot any of the 2.2.X kernels without this drive present
>> the timeout
>> > disappears. In fact when I boot with this drive present in any of
>> the newer
>> > 2.0.3X kernels which support this adapter there is NO timeout and
>> lilo
>> > behaves normally!
>> >
>> > So why don't I just shutup and just use the 2.0.38 kernel? Well I
>> do, but
>> > I would like to have some of the newer 2.2.X kernel features not
>> present in
>> > the 2.0.3X kernels.
>> >
>> > If anyone has a similiar hardware setup (at the very least has the
>> 2940U2W)
>> > that mixes both scsi and ide in the 2.2.X kernels and get no
>> timeouts or
>> > lilo troubles, please let me know. I have discussed this at length
>> with Doug
>> > Ledford and I am sure he would be interested in knowing also. It
>> is possible
>> > that there is something in my BIOS (and/or BIOS settings) that the
>> 2.0.3X
>> > kernels (as well as WINDOZE :) overlooks or doesn't care about.
>>
>> --
>>
>> Doug Ledford <dledford@redhat.com>
>> http://people.redhat.com/dledford
>> Please check my web site for aic7xxx updates/answers before
>> e-mailing me about problems
>>
>> To Unsubscribe: send mail to majordomo@FreeBSD.org
>> with "unsubscribe aic7xxx" in the body of the message
>
--------------4C43C28BEFEFA1928E72FE9A
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Doug,
<p>I am finally unsubscribing from aic7xxx. I've been subscribing since
I first sent this to you/aic7xxx on 1/24/00 :-)
<br>I was hoping someone would have a similar problem, but never saw a
similar posting.
<p>I finally broke down and bought a new EIDE (UDMA) disk a-la-COMPUSA
(really it is a MAXTOR 15GB UDMA33/66 for a measley $99.95 :-)
<p>Well this fixed the kernel timeouts that I was getting with the Western
Digital 6.4GB UDMA drives I had (both 26400 & 36400).
<p>Conclusions:
<br>=========
<p> 1) This was not a Motherboard BIOS problem specific
to the PA-2013
<br> 2) Very unlikely a kernel or driver problem although
it was not exhibited in the 2.0.3X kernels
<br> 3) Not a problem specific to just any generic UDMA
EIDE hard drive when mixed with my scsi (this is what I feared most!)
<br> 4) Most likely it is attributable to the BIOS on
the WD hard drive itself causing a BUS (or communication) problem with
the
<br> IDE controller
and/or Adaptec SCSI BIOS
<p>Anyway, I am happy that I can use this new drive with a little
more space than I had before and with the newer kernels.
<p>Thanks for your help and your advise.
<p>Regards,
<br>--Steve Cahill
<p>Steve Cahill wrote:
<blockquote TYPE=CITE>Hi Doug,
<p>Recall I upgraded to the 2.2.14 kernel and even applied your patch <<i>aic7xxx-5.1.22.patch>
</i>for the most recent driver and it did not cure the problem?
<p>--Steve
<br>
<p>Doug Ledford wrote:
<blockquote TYPE=CITE> </blockquote>
We had a machine in here in the test lab with the same problem. After
<br>upgrading the kernel to a 2.2.14 or later kernel, the problem myseriously
went
<br>away. We attribute it to IDE changes in the 2.2.14 kernel patch.
But, I'm
<br>not an IDE expert....
<br>
<br>
<blockquote TYPE=CITE>Steve Cahill wrote:
<br>>
<br>> Well Folks,
<br>>
<br>> This one is a real mystery.....
<br>>
<br>> I cannot believe that my setup is unique, but hey... stranger things
can
<br>> happen I suppose. I have an Adaptec AHA-2940U2W with several devices
( see
<br>> 2.0.38 dmesg out below), and an IDE primary drive where my boot record
lives
<br>> with a (bootable) DOS partition as well as some other Linux partitions:
<br>>
<br>> hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
<br>> hda: WDC AC26400B, 6149MB w/512kB Cache, CHS=784/255/63
<br>>
<br>> My main (mother) board is an FIC PA-2013 with a 350MHz AMD K6-2
<br>> CPU, Millenium G200 video adapter, 128MB (PC100) SDRAM, sound card
and modem
<br>> reside in the 2 ISA slots and a 3COM 3c905B Cyclone ethernet card
in one of
<br>> the PCI slots.
<br>> (aka very typical setup??)
<br>>
<br>> When booting any Linux 2.2.X kernel with this IDE drive present I
get a
<br>> timeout message (which I have posted before, but will include here
for
<br>> completeness):
<br>>
<br>> scsi : aborting command due to timeout : pid 60, scsi0, channel 0,
id 1, lun
<br>> 0 0x28 00 00 70 c2 ce 00 00 02 00
<br>>
<br>> The timeout can last anywhere from 25 to 40 seconds. Another
symptom is
<br>> LILO will hang (i.e. executing lilo) or take a very long time to
execute.
<br>>
<br>> When I boot any of the 2.2.X kernels without this drive present the
timeout
<br>> disappears. In fact when I boot with this drive present in any of
the newer
<br>> 2.0.3X kernels which support this adapter there is NO timeout and
lilo
<br>> behaves normally!
<br>>
<br>> So why don't I just shutup and just use the 2.0.38 kernel? Well I
do, but
<br>> I would like to have some of the newer 2.2.X kernel features not
present in
<br>> the 2.0.3X kernels.
<br>>
<br>> If anyone has a similiar hardware setup (at the very least has the
2940U2W)
<br>> that mixes both scsi and ide in the 2.2.X kernels and get no timeouts
or
<br>> lilo troubles, please let me know. I have discussed this at length
with Doug
<br>> Ledford and I am sure he would be interested in knowing also. It
is possible
<br>> that there is something in my BIOS (and/or BIOS settings) that the
2.0.3X
<br>> kernels (as well as WINDOZE :) overlooks or doesn't care about.
<p>--
<p> Doug Ledford <dledford@redhat.com> <a href="http://people.redhat.com/dledford">http://people.redhat.com/dledford</a>;
<br> Please check my web site for aic7xxx
updates/answers before
<br>
e-mailing me about problems
<p>To Unsubscribe: send mail to majordomo@FreeBSD.org
<br>with "unsubscribe aic7xxx" in the body of the message</blockquote>
</blockquote>
</html>
--------------4C43C28BEFEFA1928E72FE9A--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38FD4604.755CBEC8>