On Fri, 16 Apr 1999 10:38:15 +0200 (IST), "Peter L. Peres" <[EMAIL PROTECTED]>
wrote:
>On Fri, 16 Apr 1999, Oded Arbel wrote:
>
>>the next thing that happend is that I got some sort of kernel panic message,
>>involving some thing about the CPU (I don't remember exactly the phrasing,
>>except that it was full of register names and stuff like that - I think I
>>kind of panicked my self ;-> ) and I couldn't do anything else, not even a
>>proper reboot (pressing CTRL-ALT-DEL got me another endless flow of panic
>>messages and nothing else) so I had to go for the big red button.
It doesn't seem like buggy software (you didn't do something unusual).
It is either a fault hardware or corrupted files.
>If a simple compile fails, you should get a simple sigsegv, maybe a core.
>NO crash. However, if some pages in your swap partition got corrupted
>because the disk was overloaded during compile... you might see what you
It took me a few seconds to understand what you meant.
Did you mean by "disk getting overloaded during compile" that gcc is running
out of virtual memory? (overflowing the physical mem + swap partition size)?
Could this cause a system crash??
>saw. Find them oopses in the logs and try to make sense of them. Just out
>of curiosity.
>
>Peter
Udi
