Re: ProLiant DL380 Frequent Lock-ups - SCSI driver?

From: Joe Polk (listuser_at_javelinux.com)
Date: 09/30/03

  • Next message: Ian Mortimer: "Re: onstream out of business?"
    To: redhat-list@redhat.com
    Date: Tue, 30 Sep 2003 17:36:55 -0400
    
    

    Do you know what version the BIOS is? What Smart Start version did you build
    with? There is an issue regarding SS6.2 or 6.3 I'm not sure that I know
    causes system boots under Windows. I would start by updating the BIOS for
    sure. Are you using hardware RAID?

    <<JAV>>

    ---------- Original Message -----------
    From: "Maurer, Justin" <jmaurer@defywire.com>
    To: <redhat-list@redhat.com>
    Sent: Tue, 30 Sep 2003 16:00:56 -0400
    Subject: ProLiant DL380 Frequent Lock-ups - SCSI driver?

    > Greetings,
    >
    >
    >
    > We have a Compaq/HP ProLiant DL380 G3 (GigE) experiencing
    > frequent lockups. The machine is a build server running RHL 8.0
    > (Psyche) with the default 2.4.18-14smp kernel (the machine is a dual
    > Xeon), and has almost constant disk activity. The machine locks up
    > consistently, though not on a particular interval...Usually it will
    > go for 16-24 hours without a reboot, but sometimes it can be 20
    > minutes, sometimes it can be for days at a time. I can't point to
    > anything more than the constant disk activity that makes me say this,
    > but could it be an issue with the SCSI driver? Here is what dmesg
    > has to say on the subject:
    >
    >
    >
    >
    >
    > SCSI subsystem driver Revision: 1.00
    >
    > kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
    >
    > Compaq CISS Driver (v 2.4.30)
    >
    > cciss: Device 0xb178 has been found at bus 1 dev 3 func 0
    >
    > cciss: using DAC cycles
    >
    > blocks= 71122560 block_size= 512
    >
    > heads= 255, sectors= 32, cylinders= 8716
    >
    >
    >
    > blk: queue c042e400, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
    >
    > Partition check:
    >
    > cciss/c0d0: p1 p2 p3 p4 < p5 p6 >
    >
    > Journalled Block Device driver loaded
    >
    >
    >
    > The machine also has two integrated BroadCom BCM5703X GigE chips
    > (only one is beng used).
    >
    >
    >
    > Can anyone suggest troubleshooting techniques? Are any of these drivers
    > known to be problematic?
    >
    >
    >
    > Thanks,
    >
    > Justin
    ------- End of Original Message -------

    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: Ian Mortimer: "Re: onstream out of business?"

    Relevant Pages