Date: Mon, 15 Jan 1996 15:50:25 -0700 From: Nate Williams <nate@sri.MT.net> To: Jose Federero Martinez <federero@obelix.cica.es> Cc: bugs@FreeBSD.ORG Message-ID: <199601152250.PAA02185@rocky.sri.MT.net> In-Reply-To: <199601152057.VAA18775@obelix.cica.es> References: <199601152057.VAA18775@obelix.cica.es>
next in thread | previous in thread | raw e-mail | index | archive | help
> 1) HARDWARE. > ======== > > * SYSTEM MOTHERBOARD: > ------------------ > No-brand: J-403TG GREEN VLB, v2.1 > 486SX/486DX, ISA, with three slots for VLB controllers. > VLB jumpered at 0 Wait States. > CPU installed: Intel 80486DX2-S, at 66 MHz, fan-cooled. > External cache: 256 KB, 20 ns Although 20ns cache *should* work, it my experience it won't work on a 33Mhz box. I had lots of problems until I replaced my 20ns cache with 15ns cache,and all my problems went away. > DRAM installed: 12 MB, 70 ns (3x4MB 72-pin SIMM) You are running 0 wait-states with 70ns memory, which probably won't work. Try running them at 1WS. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xf1e17000 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xf01839de > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL=0 > current process = Idle > interrupt mask = > kernel: type 12 trap, code=0 > stopped at _matcd_blockread+0x1fe movb %bl,0(%eax) Although it *may* not be related, try disabling your external cache and adding another wait state to see if the problems go away. Nate > -I thought: Jesus, you need a crash dump after the panic, then savecore > it, and send the dump to someone with more knowledge of this stuff > than you. Well, I modified my /etc/sysconfig to dumpon to the swap > partition (/dev/wd0s4b) and savecore it. Then I crashed at will, and, > inside ddb did `call-ed diediedie()'. It told me it was dumping and > then rebooted. Fine. But it resulted worse at all: the filesystems > were very badly damaged. auto-fsck failed, and fscking by hand > resulted in removing a lot of files at /dev, /var and so on. Since I > am a newcomer to FreeBSD, saw no other solution than reinstallation. > Should better read the docs before doing so again This is almost always . > -At last, Linux performs fine and stable. So, the toys called MS-DOS > and Windows 3.1 (with their limitations, of course). Linux doesn't stress the system near as much as FreeBSD does. Most folks get up to 2X faster disk throughput with FreeBSD. Also, Linux often disables buggy hardware w/out informing the user, so it may be disabling your cache w/out telling you so. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601152250.PAA02185>