Date: Tue, 21 May 1996 08:55:54 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: af@biomath.jussieu.fr Cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Endeavour 133Mhz+Adaptec 2940=cc1 got signal 11 Message-ID: <199605211555.IAA12274@GndRsh.aac.dev.com> In-Reply-To: <199605211006.LAA17953@garfield.biomath.jussieu.fr> from "af@biomath.jussieu.fr" at "May 21, 96 11:06:24 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> Hello,
>
> I've installed FreeBSD Release 2.1 on the new 133Mhz Pentium (Intel
^^^^^^^^^^^^^^^
> Endeavour m/b, Triton chipset) that will replace my old Sparc II which
^^^^^^^^^^^^^^
> needs retirement. It has 64Mb of main (70ns) memory, 512Kb cache, a
^^^^^^^^^^^^^
> 2Gb IDE boot disk, an Adaptec 2940 PCI SCSI adapter which connects a
> DEC RZ24 200Mb disk only for now.
...
> And then... the dreaded "cc1 got signal 11" symptom :-(
>
> I've clocked down the motherboard (to 66Mhz I guess, the AMIBIOS setup
> doesn't say): same. I've completely invalidated the secondary cache:
Given the above underlined items, and the fact that your dmesg below
showed a CPU speed of 133 MHz, I somehow doubt that anything you did
in actually clocked it down to 66Mhz. Is what you want to to do is set
the external clock speed to 60Mhz, thus slowing the system down to a 120Mhz
Pentium.
When the system boots it should report:
CPU: 120-MHz Pentium 735\90 or 815\100 (Pentium-class CPU)
Then see if you still have problems with signal 11's. If you don't,
two likely causes are your SIMM's are two slow and the vendor is full
of crap about the bios autodetecting memory speed, or you may have simms
that are in violation of the 24 chip count imposed by almost all Triton
chipset motherboards.
...
> The hardware vendor claims that the machine has run a
> three-day burn-in cycle with no problems.
Yea, right, running ``DOS/Windows'' checkit or some other joke of a test
program.
> When I mentioned that I had
> read articles saying that 60ns memory was required, he replied that
> 70ns memory is OK on that kind of motherboard because the BIOS
> automatically sets wait cycles (???) If it were a memory access time
> problem, though, I would have expected the downclocking to make it
> disappear.
Did your system report itself under FreeBSD as a 120Mhz CPU? If not you
failed in down clocking the system.
> Any hints please ? the vendor seems a bit reluctant to swapping the
> motherboard, and even more reluctant to changing memory SIMMs (he says
> 60ns memory is virtually impossible to find nowadays).
He is lying, and infact the price difference between 60 and 70nS memory
is about $1.00/MB of memory. He just doesn't want to deal with it :-(.
--
Rod Grimes rgrimes@gndrsh.aac.dev.com
Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605211555.IAA12274>