Re: Signal 11
You appear to have been correct about the ram. I pulled the two 64M sticks
that I bought from OWC last Jan. and replaced the old ram. The signal 11
errors promptly ceased. I tested it by recompiling the kernel. I then tested
each OWC stick individually. They both caused signal 11 errors when I compiled
the kernel. One was worse than the other in that I got an error sooner. So I
contacted OWC and got an RMA for the ram. This was the first time I bought
ram from OWC. Two out of two bad sticks seems pretty unlucky :-(
On September 02 2002, Michel Lanners <email@example.com> wrote:
>On 2 Sep, this message from Marvin Germain echoed through cyberspace:
>> I have had Woody installed for a couple of days now on my powerbase 180,
>>which contains a powerlogix G4 upgrade card. I am running the 2.4.18 kernel
>> that came on the debian CD. I have been having a lot of problems with programs
>>dying with a signal 11. This has happened frequently to the X server. I have
>>also had occassional difficulty getting the system to shut down properly. Then
>>it takes forever to get through fsck because fsck dies with signal 11 or signal
>>4 on practically every inode. Incidently, fsck frequently wanted to change a
>>normal looking inode size to some crazy 20-digit number. I had to say "n" to
>>a lot of its suggestions. I have also had vi and ps fail with segmentation faults.
>> I decided to build my own kernel, which also took for ever because gcc died
>>after every few sources with a signal 11. I finally got through it. BootX would
>>not recognize the vmlinux file, but I was able to boot off the miboot.image file,
>>which seems to be intended for a rescue floppy. At any rate, there was no change
>>in the system behavior. I am contemplating wiping the disk and starting all over.
>>This is only a last resort, however, mainly because I had to run dselect about 20
>>times to get everything to install. I'm not looking forward to doing that again. Can
>>anyone offer me a better idea? Thanks.
>Re. your problems, that looks suspiciously like a hardware problem, most
>probably with faulty RAM.