lkml.org 
[lkml]   [2002]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: AIC7XXX + v2.4.18 problems?
    On Wed, Jun 19, 2002 at 11:09:13AM -0400, Nick Papadonis wrote:
    > Is anyone else having problems with the AIC7XXX driver using a AHA-29160
    > controller? I believe my kernel is going into a unrecoverable spin-lock
    > when there is high SCSI load. I'm assuming this because the keyboard
    > lights still function and network still replies to pings.

    A spinlock deadlock causes the machine to be *totally* unresponsive (aka,
    no keyboard led changes and no pings) (at least, this is true of the scsi
    subsystem spinlocks).

    > In addition the 'st' driver returns with unrecoverable errors when
    > trying to tar to tape. This usually occurs after a few hundred
    > megabytes have been pushed through a device.

    Hmmm...the tape drive isn't listed in your output below.

    > My setup is :
    > - AHA-29160N controller
    > - Internal 50 PIN / SCSI-2 port in use
    > - See below for connected drives

    It appears that you have the two hard drives connected to this 50 pin
    port. That's not good. The drives should be connected to the LVD port
    via a good LVD cable with LVD terminator, the CD-ROM should be on the 50
    pin port, and the tape (which I'm assuming is external and not a new LVD
    tape drive but an older narrow tape drive using a 50 pin connecter) should
    either be on the same cable as the CD-ROM (via an internal/external cable
    adapter) or on the 50pin port on the back of the card (but only if the
    port on the back of the card is not an LVD capable port, but is instead a
    SE port wired together with the internal 50 pin port). Hooking them up
    the way you have them is asking for trouble because your high end disks
    are being forced to operate in a very degraded performance state.

    > Channel A Target 0 Negotiation Settings
    > User: 40.000MB/s transfers (40.000MHz DT, offset 255)
    > Goal: 20.000MB/s transfers (20.000MHz, offset 31)
    > Curr: 20.000MB/s transfers (20.000MHz, offset 31)

    See, disk 1 is being forced all the way fown to narrow, ultra speeds.

    > Channel A Target 2 Negotiation Settings
    > User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
    > Goal: 20.000MB/s transfers (20.000MHz, offset 15)
    > Curr: 20.000MB/s transfers (20.000MHz, offset 15)

    Same here, narrow ultra speeds. Both of these disks should likely be
    running in wide ultra2 speeds or better (this second one might not do
    ultra2, I couldn't tell by the model number, but I suspect it does).

    > Channel A Target 3 Negotiation Settings
    > User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
    > Goal: 40.000MB/s transfers (40.000MHz, offset 127)
    > Curr: 3.300MB/s transfers

    Async transfers (the cd-rom). This should *not* be on the same cable as
    the disks.

    --
    Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
    Red Hat, Inc.
    1801 Varsity Dr.
    Raleigh, NC 27606

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:26    [W:0.028 / U:6.200 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site