Very Computer

Hi,

I've been trying recently to upgrade to kernel version 2.0.35, because
I need some new drivers in it.  I've installed the patch for the
aic7xxx driver version 5.1.2, however, despite anything I try, I CANNOT
get it to boot.  It appears to detect everything normally, but when it
comes about time to mount the root partition, everything fails.  Here
is a copy of the screen output when I boot using the parameters
"aic7xxx=verbose:0x1ffff":

aic7xxx: <Adaptec AHA-294X Ultra SCSI host adapter> at PIC 13/0
aic7xxx: Initial PCI_COMMAND value was 0x17
aic7xxx: Initial DEVCONFIG value of 0x1580
aic7xxx: Loading serial EEPROM...done
(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PIC 13/0
(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
(scsi0) BIOS disabled, IO Port 0xf800, IRQ 11
(scsi0) IO Memory at 0xfedff000, MMAP Memory at 0x8805000
(scsi0) SE High byte termination Enabled
(scsi0) Downloading sequencer code... 419 instructions downloaded
(scsi0) Resetting channel
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.2/3.2.4
       <Adaptec AHA-294X Ultra SCSI host adapter>
scsi : 1 host.
 Vendor: QUANTUM   Model: VIKING 4.5 WSE     Rev: 880R
 Type:   Direct-Access                       ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
 Vendor: IOMEGA    Model: ZIP 100            Rev: D.09
 Type:   Direct-Access                       ANSI SCSI revision: 02
Detected scsi removable disk sdb at scsi0, channel 0, id 5, lun 0
 Vendor: PLEXTOR   Model: CD-ROM PX-20TS     Rev: 1.00
 Type:   CD-ROM                              ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
(scsi0:0:0:0) Using Wide(16bit) transfers
(scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8899737 [4345 MB] [4.3
GB]
sdb : READ CAPACITY failed.
sdb : status = 1, message = 00, host = 0, driver = 28
sdb : extended sense code = 2
sdb : block size assumed to be 512 bytes, disk size 1BG
<---snip--->
Partition check:
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >  <---This is correct--->
<---snip--->
(scsi0:0:0:0) Parity error durring Data-In phase.
(scsi0:0:0:0) Parity error durring Data-In phase.
(scsi0:0:0:0) Underflow - Wanted 1024, read 512, residual SG count 1.
(scsi0:0:0:0) Parity error durring Data-In phase.
(scsi0:0:0:0) Underflow - Wanted 1024, read 512, residual SG count 1.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0
(scsi0:0:0:0) Reset called with recycled SCB for cmd.
(scsi0:0:0:0) Reset called, no scb, flags 0x1
(scsi0:0:-1:-1) Reset channel called, will initiate reset.
(scsi0:0:-1:-1) Resetting currently active channel.
(scsi0:0:-1:-1) Channel reset
(scsi0:0:-1:-1) Reset device, active_scb 0
(scsi0:0:0:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:1:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:2:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:3:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:4:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:5:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:6:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:7:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:8:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:9:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:10:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:11:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:12:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:13:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:14:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:15:-1) Cleaning up status information and delayed_scbs.
(scsi0:0:-1:-1) Cleaning QINFIFO.
(scsi0:0:-1:-1) Cleaning waiting_scbs.
(scsi0:0:-1:-1) Cleaning waiting for selection list.
(scsi0:0:-1:-1) Cleaning disconnected scbs list.
(scsi0:-1:-1:-1) 0 commands found and queued for completion.

That's the last thing I see.  The everything stops after that.  Does
anyone know what the real problem is and how I can fix it?  I figure it
has something to do with the parity error, but I don't know anything
about what the real problem is, or how to fix it.  I really need the new
kernel, but the driver that comes with it as well as the most recent one
(applied patch) don't work.  Help!!! I'm using an Adaptec 2940UW with a
Quantum Viking 4.5 GB SCSI 3 HD.  Everything works fine using the 2.0.29
kernel with the aic7xxx driver in that version.  I've also tried using
the boot option aic7xxx=reverse_scan, but that made no difference.

Thanks in advance for any help.

Lyle Taylor

I'll admit this looks like a SCSI read error, but in the stupid
questions department:

 - Did you compile support as module or non-module?  You'll need this
compiled into the kernel to boot to it, unless you use an initrd.

 - Are you sure you got LILO configured right, including the right
boot/root partition?

 - Could you boot this partition before and/or can you boot it on your
old kernel?

--

    What part of "Gestalt" don't you understand?
    Welchen Teil von "Gestalt" verstehen Sie nicht?

web:       http://www.netcom.com/~kmself
SAS/Linux: http://www.netcom.com/~kmself/SAS/SAS4Linux.html    

 12:31am  up 1 day, 0 min,  5 users,  load average: 0.11, 0.15, 0.11

Hi Lyle,

I've had similar problems with the 5.2.* aic7xxx drivers. These drivers seem to
be even more sensitive to termination/cable length issues than the old ones.

Have you tried the measures outlined in README.aic7xxx (it's in
/usr/src/drivers/scsi)?

You might also try removing all external SCSI devices and see if your system
will boot. If so, start adding these devices back until it no longer boots. I
discovered that with the new drivers, my system would not boot with both my HP
DAT and my QUANTUM external HD connected (my symptoms were the same as yours).
Luckily, I had an extra AVA1505 in the closet so I put it in my system and am
now using it for the DAT.

Good Luck,
-Tom
--
Tom Eastep      
COMPAQ Computer Corporation
Enterprise Computing Group
Tandem Division

Hi,

I've tried everything I understand in the file, and nothing made any
difference. Disconnecting other devices from my SCSI card gave me
slightly different values for the parity errors, but the end result was
always the same.  Also, my root partition is on /dev/sda1, and it simply
won't boot no matter what is connected or not.

Thanks.  Any more ideas?

Lyle Taylor

Yup.

Quote:>  - Are you sure you got LILO configured right, including the right
> boot/root partition?

Yup again.  I have a standard bootdisk image prepared that I use.  I
simply mount my bootdisk, copy the new kernel onto it, and then run a
little script that runs lilo with the right parameters to install
everything onto the floppy.  I have to do it this way, because lilo
doesn't like my hard disk.  It works fine with my old kernel, and I
shouldn't have to change any parameters for the new one.

Quote:>  - Could you boot this partition before and/or can you boot it on your
> old kernel?

Yup again.  I only have problems when trying to use any of the new diver
versions.

What now?

Thanks for you help.

Lyle Taylor

Quote:>Hi,

>I've been trying recently to upgrade to kernel version 2.0.35, because
>I need some new drivers in it.  I've installed the patch for the
>aic7xxx driver version 5.1.2, however, despite anything I try, I CANNOT
>get it to boot.  It appears to detect everything normally, but when it
>comes about time to mount the root partition, everything fails.  Here
>is a copy of the screen output when I boot using the parameters
>"aic7xxx=verbose:0x1ffff":

>aic7xxx: <Adaptec AHA-294X Ultra SCSI host adapter> at PIC 13/0
>aic7xxx: Initial PCI_COMMAND value was 0x17
>aic7xxx: Initial DEVCONFIG value of 0x1580
>aic7xxx: Loading serial EEPROM...done
>(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PIC 13/0
>(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
>(scsi0) BIOS disabled, IO Port 0xf800, IRQ 11
>(scsi0) IO Memory at 0xfedff000, MMAP Memory at 0x8805000
>(scsi0) SE High byte termination Enabled
>(scsi0) Downloading sequencer code... 419 instructions downloaded
>(scsi0) Resetting channel
>scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.2/3.2.4
>       <Adaptec AHA-294X Ultra SCSI host adapter>
>scsi : 1 host.
> Vendor: QUANTUM   Model: VIKING 4.5 WSE     Rev: 880R
> Type:   Direct-Access                       ANSI SCSI revision: 02
>Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: IOMEGA    Model: ZIP 100            Rev: D.09
> Type:   Direct-Access                       ANSI SCSI revision: 02
>Detected scsi removable disk sdb at scsi0, channel 0, id 5, lun 0
> Vendor: PLEXTOR   Model: CD-ROM PX-20TS     Rev: 1.00
> Type:   CD-ROM                              ANSI SCSI revision: 02
>Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0
>scsi : detected 1 SCSI cdrom 2 SCSI disks total.
>(scsi0:0:0:0) Using Wide(16bit) transfers
>(scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8
>SCSI device sda: hdwr sector= 512 bytes. Sectors= 8899737 [4345 MB] [4.3
>GB]
>sdb : READ CAPACITY failed.
>sdb : status = 1, message = 00, host = 0, driver = 28
>sdb : extended sense code = 2
>sdb : block size assumed to be 512 bytes, disk size 1BG
>Thanks in advance for any help.

>Lyle Taylor

When I installed Linux on my system, I had to change the CDROM drive
settings in the SCSI bios to stop resetting problems (I think I saw a
reset in your log as well). The settings changed were:

Initiate Wide Negotiation was changed to NO
I alse set Max Sync Rate to 20 Mz (Not sure if this one was needed)
My setup used both internal connectors

I assume the CDROM is not a wiide drive

Try changing these and see what happens (You may also have to change
these same settings for the ZIP drive).

Signature Caught up in Committee
Committee not come out with changes yet

Never give someone a gun unless you are sure which way they will
point it - Jeffrey Sinclair - By Any means Necessary - Babylon 5

I'm good at dumb, easy suggestions. How about changing your
SCSI cabling, just for "good luck"? Kinda like pulling out
yer spark plug wires and re-connecting 'em when your
car stalls for no apparent reason.

--
Jack J. Woehr                 # The Drug War is Race War
PO Box 51, Golden, CO 80402   # The Drug War is Class War.

http://www.veryComputer.com/~jax/rcfb # Arrest the War on *.

But why was it able to start and mount with the precompiled kernel
from the RH5.1 CDROM?