lkml.org 
[lkml]   [2006]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: sym53c8xx PCI card broken in 2.6.18
    David Johnson napsal(a):
    > Hi all,
    >
    > I'm running a Sun Ultra Enterprise 450 (SPARC64) machine which has an on-board
    > SCSI controller and a PCI SCSI controller, both supported by the sym53c8xx
    > driver.
    >
    > With 2.6.17.9 (and earlier) SCSI works perfectly, but with 2.6.18-rc4 and
    > 2.6.18-rc4-git1 I'm getting errors on boot for all devices attached to the
    > PCI card, but all the devices attached to the on-board controller are
    > detected and configured OK.
    >
    > lspci identifies the on-board controller as:
    > SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 03)
    > and the PCI controller as:
    > SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14)
    >
    > Here's the output from initialisation of the devices on the PCI card (repeated
    > for every device):
    > scsi2: sym-2.2.3
    > scsi 2:0:0:0 ABORT operation started
    > scsi 2:0:0:0 ABORT operation timed out
    > scsi 2:0:0:0 DEVICE RESET operation started
    > scsi 2:0:0:0 DEVICE RESET operation timed out
    > scsi 2:0:0:0 BUS RESET operation started
    > scsi 2:0:0:0 BUS RESET operation timed out
    > scsi 2:0:0:0 HOST RESET operation started
    > sym2: SCSI bus has been reset
    > scsi 2:0:0:0 HOST RESET operation timed out
    > scsi: device offlined - not ready after error recovery
    >
    > The devices on the PCI controller are a mixture of 'Fujitsu MAG3182L SUN18G'
    > and 'Seagate ST318203LSUN18G' drives.
    >
    > Looking through the changelogs between 2.6.17.9 and 2.6.18-rc4-git1, I can't
    > see any changes to sym53c8xx, so I'm guessing this has been caused by some
    > generic SCSI subsystem change. Let me know if I can do any more to debug.
    >
    > Regards,
    > David.
    >
    I must say that I have the same experience with E250 a D1000 disk array.
    I think that is HW problem but I have the same symptom described before.
    If I have disk in internal bay and controller all works perfect. But if I put
    disk to D1000 I get the same error. I have use 2.6.18-rc3.

    Dan
    -
    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: 2006-08-23 23:05    [W:2.788 / U:0.048 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site