Re: oops, signal 11

2001-01-22 Thread Ralf Baechle
On Sat, Jan 20, 2001 at 01:46:50PM +0100, [EMAIL PROTECTED] wrote: > I know that signal 11 with gcc is a sign of bad hardware; however it > strikes me that I don't get random oopses - a whole bunch of them is appended. The compiler tends to hammer harder on the memory than the kernel; this is

Re: oops, signal 11

2001-01-22 Thread Ralf Baechle
On Sat, Jan 20, 2001 at 01:46:50PM +0100, [EMAIL PROTECTED] wrote: I know that signal 11 with gcc is a sign of bad hardware; however it strikes me that I don't get random oopses - a whole bunch of them is appended. The compiler tends to hammer harder on the memory than the kernel; this is a

oops, signal 11

2001-01-20 Thread mkloppstech
I know that signal 11 with gcc is a sign of bad hardware; however it strikes me that I don't get random oopses - a whole bunch of them is appended. I used 2.4.0 with alsa, kmp3player running and an endless loop compiling the kernel. Mirko Kloppstech ksymoops 2.3.7 on i686 2.4.0. Options

oops, signal 11

2001-01-20 Thread mkloppstech
I know that signal 11 with gcc is a sign of bad hardware; however it strikes me that I don't get random oopses - a whole bunch of them is appended. I used 2.4.0 with alsa, kmp3player running and an endless loop compiling the kernel. Mirko Kloppstech ksymoops 2.3.7 on i686 2.4.0. Options