km@mathcs.emory.edu (06/01/90)
We've been getting kernel read fault panics on our 4/280 server every few
days since we converted to 4.1. "crash" doesn't show a real pattern, since
we started saving the cores. One time it was in the "ie" driver
interrupting a user program, another time it was in the "zs" driver
interrupting a system call.
We weren't seeing this in 4.0.3. The 4.1 is unpatched, the 4.0.3 had
various patches (at least some flavor of alm patches).
Anyone else seeing this?
Ken Mandelberg | km@mathcs.emory.edu PREFERRED
Emory University | {rutgers,gatech}!emory!km UUCP
Dept of Math and CS | km@emory.bitnet NON-DOMAIN BITNET
Atlanta, GA 30322 | Phone: (404) 727-7963emcalc@sugar.hackercorp.com (William M. Schmidt) (06/04/90)
In article <8384@brazos.Rice.edu>, km@mathcs.emory.edu writes: > We've been getting kernel read fault panics on our 4/280 server every few > days since we converted to 4.1. "crash" doesn't show a real pattern, since > we started saving the cores. One time it was in the "ie" driver > interrupting a user program, another time it was in the "zs" driver > interrupting a system call. On our 3/280 running an unpatched version of 4.1 we're seeing daily parity errors on zs1, the keyboard/mouse interface. The interesting thing is that since we're using a terminal as a console this device is not included in the kernel configuration file. It'd be nice to know what's going on. Bill Schmidt | Texas Accelerator Center | "Eagles may soar, but a worm never emcalc@sugar.hackercorp.com | gets sucked into a jet engine"