Subject: RE: Parity error - passing arguments to the Kernel to ignore cert ain drives Q.
From: Blottman John B III NPRI (BlottmanJB@Npt.NUWC.Navy.Mil)
Date: Mon Jan 31 2000 - 07:35:32 MST
Abdon,
I cannot provide a solution for your problem, but I can offer a workaround.
I too have similar problems with a Beige G3 and an Adaptec PCI-SCSI
controller. (mine is the 3940UW). It uses the aic7xxx driver. The kernel is
not 'stalling', but entering a loop in which the scsi bus is being reset,
and timing out. I have never found a solution to this. I posed my problem
to the aic7xxx mailinglist group: AIC7xxx@FreeBSD.org, but without a
response. I tried various upgrades to the kernel, upto 2.2.14pre9 (ydl ships
with 2.2.6) which include updates for the aic7xxx driver, without success.
See http://people.redhat.com/dledford/aic7xxx.html
To work around the problem, I rebuilt the kernel with the aic7xxx device
defined as a module. That way the kernel boots. I just cannot access the
drives off the Adaptec card under Linux. The mac OS can still use the
drives. This is a big disappointment for me, but may be ok for you.
re: Why is the kernel recoginizing the Adaptec 2940UW as the primary SCSI
bus rather than the built-in MESH?
Linux identifies devices differently from unix. The first device loaded is
identified as :0. The device drivers are loaded alphabetically, so Adaptec
comes before Mesh.
Good luck,
John
> ----------
> From: A. G.
> Reply To: yellowdog-general@lists.yellowdoglinux.com
> Sent: Sunday, January 30, 2000 12:38 AM
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Parity error - passing arguments to the Kernel to ignore
> certain drives Q.
>
>
> Hi all,
>
> Just got done installing YDL on a Beige G3 and I'm having problems with
> the kernel stalling when it gets to a certain drive. I'm pretty sure
> this drive is unsupported as I had to take it out of the SCSI chain in
> order to install YDL, but I need it in there for the MacOS side.
>
> Hardware background info:
>
> ATA chain: 1 drive, CD-ROM (master-slave, no problems here)
> Built-in SCSI (MESH): 2 external drives and an internal zip (no problems
> there, no scsi id conflicts)
> Adaptec 2940UW on PCI slot: (Offending drive on it, only one on the
> card) Drive has a SCA interface with SCA to SCSI adapter. (Assuming that
> is where the parity error is coming from, as I can boot YDL ok without
> it)
>
> Specific error message is:
> ----------------------------------------------
> (scsi0:0:1:0) Parity error during Command Phase
> SCSI host 0 abort (pid1) timed out - resetting
> SCSI bus is being reset for host 0 channel 0
> SCSI host 0 channel 0 reset (pid1) timed out -trying harder
> SCSI bus is being reset for host 0 channel 0
> ----------------------------------------------
>
> And it goes on a loop from there. I believe there is arguments that you
> can pass to the kernel to avoid unsupported devices. I have tried
> "sda=noautotune" as I'm assuming it could be a DMA time-out. Of course,
> I could be waaaay off.
>
> That brings me to another (related) question... Why is the kernel
> recognizing the Adaptec 2940UW as the primary SCSI bus rather than the
> built-in MESH? Shouldn't the internal be bus 0 and the 2940UW bus 1?
> (Not that it would matter on boot up though...)
>
> I have looked thru the old posts to the list all the way to March and
> haven't found anything related. Any help, ideas or pointers thrown my
> way would be greatly appreciated. Thanks much.
>
> Regards,
>
> Abdon
>
>
> ---
> Abdon G.
> www.ColorReal.net
>
> "Sometimes, it doesn't matter how hard you try, things will not turn out
> the way you want them to. However, if you keep going no matter what,
> perhaps you will still not get things your way, but at least you'll get
> tougher."
>
This archive was generated by hypermail 2a24 : Tue Feb 01 2000 - 17:50:59 MST