Date: Mon, 17 Jun 1996 22:51:35 -0400 From: "Eloy A. Paris" <Eloy.Paris@ven.ra.rockwell.com> To: "M.R.Murphy" <mrm@MARMOT.Mole.ORG> Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: FreeBSD works with Cy486DLC processors? Message-ID: <2.2.16.19960617230901.3f870228@zeus.ven.ra.rockwell.com>
next in thread | raw e-mail | index | archive | help
El 06:38 PM 17/6/96 -0700, tu escribiste: >> My hardware setup is: >> >> Cyrix Cy486DLC CPU >> 16 Megs. of RAM >> 1 GByte IDE hard drive >> FreeBSD 2.1.0-RELEASE >> > >What kind of memory do you have? What speed? What about cache? What speed? >Do you have BIOS options to introduce additional wait states? Have you >tried them? Hi, Thanks for your answer. I have one 16 MByte SIMM. I am not too sure but I think the speed is 70 nanoseconds. I used a different 16 MByte SIMM and got the same segmentation faults. I do not have external cache and hence it is disabled in the ROM BIOS setup. I disabled today the internal cache. There are some BIOS options (a couple of them) to introduce additional wait states. I think I tried them several days ago with no luck but I am going to try again. My kernel is configured just for the hardware I have (1 NE2000 Ethernet card, two serial ports, one printer port, UFS, PROC file system, NFS). My mother board has two PCI slots but PCI support is disabled in the kernel. The faults are random. When the internal cache is enabled, I can easyly reproduce the fault with: modload -u -o /tmp/saver_mod -e saver_init -q /lkm/star_saver_mod.o Of 5 commands like the above, at least one gives me a segmentation fault (the ld command, actually, that is being called by modload). >I should have asked in my previous mail: do you have a CPU cooler? Sure thing. This was the first thing that came to my mind. I have a good cooler and fan. The CPU is cold as ice. I read in the INSTALL doc. that you should avoid using the "entire disk" option with IDE hard drives in the partitioning part of the installation. I am using my entire IDE disk for FreeBSD (no other OS's). Can this be the problem? I don't think so but who knows? Today I got another program exiting with signal 11. The command was 'tr' that has nothing to do with nothing. The internal cache was disabled so I am starting to think there is something else BESIDES the CPU that is giving me a hard time. Probably if I try the wait states options ... Thanks. Eloy.- -- Eloy A. Paris Global Technical Services Rockwell Automation de Venezuela Telephone: 58-2-9432311 Fax: 58-2-9430323
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2.2.16.19960617230901.3f870228>