> after spending days stress-testing my various Linux-machines
> (under Linux-2.0.34pre16) with heavy disk-I/O, network-I/O, high
> CPU-load, forking and flood-pinging, without a single hickup
> since the ISDN problems were solved, I went crazy:
> I remembered the famous "crashme" program, which creates
> and executes lots of illegal code.
>
> Well, I tried it both as root and as unprivileged user,
> and guess what: Linux-2.0.34pre16 locked solid in both
> cases after just about 10 minutes... :-(
> No logfile-entry, no "oops" on the console, just dead!
Strange. I know of hw bug in 386 CPU which could do just this. What
CPU were you using? Can you reproduce it? Can you reproduce it with
other CPU?
Pavel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu