Ricardo Junior writes:
> 
[snip]
> 	A month ago or so I installed a RAID1 volume setup with RAIDFRAME. The 
> machine ran fine until today, when they called me home because the server 
> was down. Unfortunatelly, the server was reset before proper procedures. I 
> went there and the root filesystem (stored in raid0a) was dirty with two 
> directories corrupted. I fsck'ed it and the system was up again. No core, 
> nothing in the logs. This was the second crash, and I could not find out 
> what happened.
> 	
> 	When I was finishing the "system checkup", I closed the open sessions and 
> went back to the login screen. To verify if I had forgotten any consoles 
> open, I switched the ttyE's with CTRL+ALT+F1/2/3/4 (fast, holding ctrl+alt 
> and pressing "f1 f2 f3 f4" very fast). What happened? The kernel stopped again.
> 	I didn't have the time to write down a full stack trace. There were many 
> people complaining. The message was: Stopped at cpu_Debugger +0x4 leave.

Ummmmm..... You wern't typing so fast that you didn't accidentally hit 
CTRL-ALT-ESC, did you?  (The above "message" certainly indicates that...)

(I have no guesses as to what caused the second crash -- more info (like the 
full stack trace) is needed...)

Later...

Greg Oster