Justin, I am running RH 9.0 and RH 2.1 ES on DL380 servers. RH 9.0 had no problems at all. Everything is running fine.
However on RH2.1 ES, we ran into issues with network connectivity being lost, and the machine stopping to respond. The fix was listed in "HP/Compaq Customer Advisory Number: CO030310 CW02" Take a look at it. That might help. http://wwss1pro.compaq.com/support/reference_library/viewdocument.asp?source=CO030310_CW02.xml&dt=3 and http://wwss1pro.compaq.com/support/reference_library/viewdocument.asp?source=CO030310_CW01.xml&dt=3 I would suggest using RH 9.0 . So far I had no issues with it. Saqib Ali --------- http://www.xml-dev.com On Tue, 30 Sep 2003, Maurer, Justin wrote: > 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 > > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
