I just experienced my first lockup while using linux 2.0.x - some info about
my configuration:
AMD 5x86 DX4 133
16 MB FPM, 32 MB EDO
3 IDE-HDs
PCI S3 Trio 32/64 Video-adapter
PCI ne2k-clone
Gravis Ultrasound
.. and a cool blinkenlight-thing attached to the parallel port
The kernel is 2.0.35 with the IP-portfw and Precise Timestamping patches
applied.
This is my home-pc, and at the time it crashed I was running X and my
personal blinkenlight-daemon, I mention this, because I wrote it to use
cli() and sti() while setting the LEDs.
I think this lockup can be blamed on the cli() and sti() thing, a little
code fragment follows:
----8<----
sti ();
#if NUMLIGHTS==4
lights = ((port_in (PORT) & ((256 - (1 << (2 + NUMLIGHTS))))) | lights);
#else
lights = ((port_in (PORT) & ((256 - (1 << (NUMLIGHTS))))) | lights);
#endif
port_out (PORT, lights);
cli ();
----8<----
Other programs running during the lockup: httpd, squid, netscape, pine with
little to no sysload, my CPU blinkenlights froze at 5-35% cpu-usage. Network
activity was also low; maybe 5 nfs-packets per second max; I don't know
anything about memload, but I don't think that is related to this crash.
Nothing in the logs though. The machine didn't respond to pinging or any of
the magic keys.
Anybody with good ideas? Having to wait 5 minutes for fsck to finish is
quite annoying.
VrGr,
__ ___ __ C. Jasper Spaans <spaans@corps.nl> -o)
/ //__ /\\
/__ __/ __/ Donkerstraat 9-A 2611 TE DELFT 015-2133685 _\_v
join the penguin force!
23:03pm up 7822 days, 13:50, 1 user, load average: 0.00, 0.00, 0.00
-
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.altern.org/andrebalsa/doc/lkml-faq.html