Signal 11 is a seg fault.
The reason you can compile your kernel then have it
fail then start up again with no problems is because
you might have some sort of memory problem
where the compilation takes up memory, hits some
defective part of memory gets a seg fault(Signal 11)
and quits, start up again, memory is free, and you
can do it again till you hit that section.
My room-mate had a similar problem but I think
it had something to do with th fact he had
a cyrix chip that was notorious for over heating
even though the fan was working he'd get
seg faults. He just opened his case and
but a real human type fan pointing into the
case, thats the makeshift way.
But for your info Signal 11 is supposedly the
same thing as a seg fault as far as I know.
-Omar
Chien-Yu Chen wrote:
> This past weekend, I decided to change my old slackware to redhat 5.1. there
> were several places where I receive signal 11 and I wonder if anyone here has
> any idea on this.
> When I tried to install using FTP, I had to do it several times because many
> times, it popped up with signal 11 message during installation, and just
> stopped there. first I thought this might be a hd problem and did a check
> during formatting, and no error were found when I do that.
> second place where I found signal 11 is when I got the system up, and trying
> to re-compile the kernel. it's 2.0.34. there are many places where it says,
> signal 11 when I do make zImage. funny thing is, after it failed, I'll do make
> zImage again, and it will pick up where it left without any problem until
> another one of the signal 11 occured again so.. and there seems to be some
> un-defined variable in the kernel source code, especiall under devices/char and
> the SMB support. any ideas?
> ---------------------------------------------------------------------------
> Send administrative requests to [EMAIL PROTECTED]
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
