Messages in this thread | | | Date | Fri, 28 May 1999 07:34:01 -0400 (EDT) | From | "Steven N. Hirsch" <> | Subject | Re: Mysterious lockups in 2.2.9. |
| |
On Fri, 28 May 1999, Brian Schau wrote:
> > Hmm. I'm usually quite adept at breaking kernels (bad luck, perhaps?), > > but haven't had so much as a hiccup from 2.2.9 + Trond's NFSv3 client > > patch + HJ/gam's server patches. I'm running three boxes fairly > > constantly, an AMD 5x86/133, an Intel P166 and a dual-Pentium II SMP > > machine. All the drive subsystems are exclusively SCSI (NCR53Cxx, Adaptec > > 7880, 7895 respectively - mix of drives). Networked with 100Base ethernet > > and all crossmounted with each other via NFS (don't ask). > > > > Completely flawless. > > > > Steve > > > Ok. There goes my scsi-is-the-culprit idea ...
Well, the computer must have been listening. Not an hour after I posted this, I was untarring two largish files simultaneously when a complete machine lockup happened on the P166! No response to any stimulus, and the SCSI activity LED was stuck on. Magic sysreq didn't work... Red button + reboot + (looonnngg) fsck :-(.
The actual work was being done on an NFS client which mounts the P166 as server.
Steve
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |