System: Dual PPro 200/256 overclocked at 233, SuperMicro P6DOF (Orion
450GX chipset), 256MB RAM (ECC, 4-way interleaved), AHA2940UW
controller (IRQ 11), Western Digital Enterprise 4.5GB and IBM
UltraStar2S 4.3GB SCSI-UW HDDs, Fujitsu M2513A 640MB MO SCSI,
Toshiba XM3801TA CD-ROM SCSI, D-Link DE530 PCI NIC (DEC Tulip,
DS21041, IRQ 10), Matrox Millenium II 8MB (IRQ 12).
Setup: Red Hat Linux 4.2, some minor patches, ran 2.0.33, 2.1.98, and
(recently) 2.1.103 with no problems. Only symptom of anything
wrong is "Socket destroy delayed (r=0 w=xx)" repeated often in
/var/log/messages. Has been running for 6months.
Symptom: when trying to boot up in 2.1.105, the second drive (5400rpm)
is not detected at all after the SCSI bus reset. I am using a
lilo append="mem=256m aic7xxx=tag_info:{{8,0,0,8,0,0,0,0}}".
Ouch#2: System locks up hard after CD-ROM door open and closes.
System: Dual PPro 166/512 overclocked to 180, SuperMicro P6DNE (Natoma
440FX chipset) w/ 192MB, AHA2940 controller, Seagate Barracuda
4.3GB and Seagate HawkII 2.1GB SCSI-2 HDD's, Fujitsu 230MB MO
(SCSI), Plextor 14/32 CD-ROM (Ultra-SCSI), Ricoh 6201s CD-RW
(6x2x, SCSI), D-Link DE-220 NIC (NE2000 clone), SB compatible
cheapo sound card, Matrox Millenium 8MB.
Setup: Newly reinstalled Red Hat Linux 5.1; same aic7xxx params above.
Symptom: when running 2.1.101 has a persistent lock-up problem with
when also working remotely at Matlab on a local UltraSparc-- X
windows often locked after a figure is displayed. When using
either 2.1.101 and 2.1.103, has many "Spurious APIC Interrupt,
Aiyeee, should never happen" reports. Does *NOT* report APIC
spurious reports under 2.1.105, but system reproducibly locks
hard after CD-RO ejection and re-insertion.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu