Re: Finding mysterious 2.0.33 crashes

Manfred Petz (pm@radawana.cg.tuwien.ac.at)
Sat, 14 Feb 1998 18:12:03 +0100 (CET)


> Has anyone had mysterious hangups in 2.0.33 (total hang, no messages in
> logs, no oops) who is _not_ using an Adaptec SCSI driver? It could help
> narrow the range of code to be checked if that's a common factor in all
> these cases. Also, has anyone had this problem who is _not_ using an
> NE2000 ethernet card? Who is _not_ using a PS/2 mouse? Who is _not_
> using glibc?
>
> Let's try to figure out the commonalities of our systems. My first
> suspicion is the 2940 driver.
>

Here I'm running 6 Linux servers with *identical* hardware:

o quite old HP-Vectras with AMD P5
o 3c509
o 1x Quantum IDE (onboard controller)
o memory ranging from 16MB to 48MB (that's the only
difference in hardware)
o there's an onboard PS/2 but there's no mouse.

no other special hardware
*identical* kernel (I build it once for all systems)

all machines but two of them now run 2.0.33 for weeks, before I used
2.0.31 (with great success, one server actually runs 2.0.31 for 90 days now).

But here's my problem:

ONE machine runs 2.0.31 very fine (for months!). Someday I decided to
upgrade to 2.0.32. It then *repeatedly* crashed after at most 2 days of
uptime. 2.0.33 same story. Absolutely dead, no oops, no syslog entry.
I tried this multiple times.

It seems to me that there must have happened something between 2.0.31
and 2.0.32.

The machine which crashes with > 2.0.31 is our web server. On the other
hand I'm running 2.0.33 on two other (but completely different) machines
with ~ 50 virtual domains without any problem...

Tell me, if I can do something to help you fix this nasty problem.
We even can talk about access to this machine if it helps.

pm

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu