Date: Tue, 17 Oct 95 18:53:16 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) To: gillham@andrews.EDU Cc: FreeBSD-Hackers@freebsd.org Subject: Re: Stability questions... Message-ID: <9510171753.AA15624@wavehh.hanse.de> References: <9510171512.AA24607@edmund>
next in thread | previous in thread | raw e-mail | index | archive | help
gillham@andrews.EDU (Andrew Gillham) wrote: >Apologies if this is the wrong mailing list. >I installed FreeBSD 2.0.5-RELEASE over the weekend, and I have >been having problems with it. What I am seeing is "cc1 interrupted >by signal 11" or similar when I am trying to compile a kernel. >Restarting make will eventually get it all built though. Is this a >known problem with 2.0.5-RELEASE, or is my hardware flakey? I can reliable make by box behave that way by either playing with the RAM timing settings or by overclocking the CPU. So I'm sure it is a hardware problem. >I have been running NetBSD on this box without any problems. That is odd, yes. When I kick my Mainboard, both NetBSD and FreeBSD break. Maybe it's a possible explanation that NetBSD uses other memory banks to provide memory for the compiler by default. You have 32 MB and only about 8 are used in compilations. And I know that the AMD chips have some littel differences in the MMU hardware. Maybe the FreeBSD VM system does something else here than NetBSD. Try that: - Remove some of your RAM, try different SIMMs on their own. - Turn of external Cache (standard answer :-) - Maybe you can try an Intel CPU? - Try a different SCSI controller. Yes, sounds odd, but the FreeBSD VM/buffer-cache system can provide files much faster that NetBSD does. NetBSD has one extra level of copying in RAM. Maybe this shows up timing problems with your system. Try for example a 1542, which will make things slower. OK, it really sounds odd. And let us know what solves the problem! >Also, I supped freebsd-current onto my NetBSD NFS server, and tried >building it. I was able to build a kernel and /sbin/* (by restarting >make whenever cc1 got a SEGV), and rebooted with the new kernel. This >new kernel didn't appear to have the SEGV problem, but I'm not 100% >sure, as something else broke. After a few minutes of compiling (on the >NFS mount) the kernel says "Biodone: buffer already done" or something >and hangs my compile. (sorry for the not exact errors, but I'm at >work, and the PCs are at home) Accessing the NFS mountpoint will hang >my shell, but I can still halt the box from another console. >Any ideas? Should I be trying to update to 2.1-current instead of >2.2-current? (how would I do that? I just ask for 'current' via sup.) Absolutely. 2-2-current is lilely to have problems. It is not like NetBSD-current, it is much more "experimental". The 2-1 snapshots are the best solution for production systems that should be up-to-date, but stable. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <cracauer@wavehh.hanse.de> - Fax +49 40 522 85 36 BSD User Group Hamburg, Germany - No NeXTMail anymore, please. Copyright 1995. Redistribution via Microsoft Network is prohibited
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9510171753.AA15624>