I really cant think what to make of this except one reason. Sig 11 is
cause if some data is corrupted while retrieving from memory. So if the
data happens to be a pointer, it will now point to some other location
which might vioate its valid "segment".
Flaky hardware sometimes leads to incorrect retreival. Thus the only
explanation i can think of rests on "sometimes". A system might work fine
for hours till such an error.
Such errors are also caused by esoteric things like cosmic radiation
etc,but iguess thats ruled out.
Just to rule out defect in your hard disk, can you run it by disabling
swapping.
All the best shridhar...for you know i am in the same boat as well.
sreangsu
> I compiled the kernel at vendors place. It compiled OK. I brought whole setup
> home. Same CPU, Same mobo, same memory and even same set of cables. When I say
> same, it's same piece, not of same make and model.
>
> Now I tried to compile kernel at home. I again received Sig11.
>
> I turned off HDD DMA. That made make zImage to live a bit longer. But it did not
> help to complete it. I even pulled of CDROM/floppy drive to reproduce settings
> at vendors place. But no help.
>
> Now I will try to fiddle with BIOS settings...
----------------------------------------------
The mailing list archives are available at
http://lists.linux-india.org/cgi-bin/wilma/LIH
