Just had a _very_ nasty oops in 2.1.15. It's a stock kernel with a relatively
inactive ACL patch I'm working on with Artem Belevich. I was rebuilding my
kernel to add SMP support, and decided to switch VCs and build something else.
Nothing out of the ordinary, other than as soon as the gcc started, I was
bombarded by an endless stream of what appeared to be nonfatal oopses.
Unfortunately, klogd has been acting a little strange on me since I installed
2.1.15, and absolutely nothing got logged. I couldn't even CTRL-ALT-DEL out
of this situation - had to hit the reset button. Machine is an Intel P5-166
(12 stepping) with 48 MB of memory on a Tyan Tomcat II board. One other
caveat of interest, I had the kernel make running with -j7 (a holdover from
before SMP broke with the new series), so the system believed it was actually
running 8 simultaneous compiles. Sorry this is so thin in info. If anyone
wants to persue this further, I'd be glad to offer any info that would be of
use.
- Pete
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMrcEUzkUd9WlV5D5AQHZzAP/UWCnOj788T3pZzVvSL30iABnZ+oLcKPO
YA25jVLiJ8e412A3vI7zUOJMA11GW2aF8o8A/7m0KIM1Xmy4l7Wt/UoO2P6PIU9t
dmc7ZZW5IKQQ7w3DZSVTXVuXXn1IGM8itSZNctmKvAQKK4IOna4YzaZgPgZOFo1b
mfv9wCgZlwo=
=tjdv
-----END PGP SIGNATURE-----