From owner-freebsd-questions Wed Nov 19 14:38:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA07150 for questions-outgoing; Wed, 19 Nov 1997 14:38:03 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from mail.virginia.edu (mail.Virginia.EDU [128.143.2.9]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA07142 for ; Wed, 19 Nov 1997 14:37:51 -0800 (PST) (envelope-from atf3r@cs.virginia.edu) Received: from ares.cs.virginia.edu by mail.virginia.edu id ab29252; 19 Nov 97 17:37 EST Received: from stretch.cs.virginia.edu (atf3r@stretch-fo.cs.Virginia.EDU [128.143.136.14]) by ares.cs.Virginia.EDU (8.8.5/8.8.5) with ESMTP id RAA23742 for ; Wed, 19 Nov 1997 17:37:34 -0500 (EST) Received: (from atf3r@localhost) by stretch.cs.virginia.edu (8.8.5/8.8.5) id RAA23480; Wed, 19 Nov 1997 17:37:32 -0500 (EST) Date: Wed, 19 Nov 1997 17:37:32 -0500 (EST) From: "Adrian T. Filipi-Martin" Reply-To: adrian@virginia.edu To: FreeBSD Questions List Subject: 2.2.5-RELEASE panicing frequently Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I just upgraded my box to 2.2.5 a few days ago. It was running quite happily as a 2.2.2-STABLE box, but now it panics pretty easily. It even paniced during the install several times. To get the OS installed I removed all but 16M of the RAM thinking it might be a problem related to the mysterious 48M install preoblem I hard about on previous releases. This did work. I have since reinstalled the RAM and, well the panics are back. I am doubtful that my memory went bad during an install. It would be an odd coincidence, so I am suspecting some other bug is at play here. One time during an install panic, I got the following message: vm_page_free: pindex(-260407040), busy(0), PG_BUSY(0), hold(6) I cannot say what the full panic message is because I was on a vty1, not vty0. The machine always reboots before I can see the panic message, so I recompiled it with the DDB_UNATENDED option. (I believe this is the correct option to get the system not to reboot automatically after a panic.) Well, the new kernel will not boot fully. It hangs when trying to access my second SCSI controller, a BT 747S. The system doesn't panic, but I cannot go multi-user without the second SCSI card, so I need to reboot the original kernel. Oddly enough the BT driver prints out messagesa about the BT742A not responding. Does anyone have any suggestions? The BT747S is a recent addition to my system, but noe of the error messages point to it being a problem until I add the SSB option to the kernel. This ideally should not affect the success/failure rates for booting. FYI, so far the only thing I have tried in terms of kernel customization was to remove the bounce buffers options. This didn't help with the panics. I will try a fully customized kernel shortly. I still have unconfigured devices installed. thanks, Adrian -- adrian@virginia.edu ---->>>>| If I were stranded on a desert island, and System Administrator --->>>| I could only have one OS for my computer, Neurosurgical Visualzation Lab -->>| it would be FreeBSD. Think about it..... http://www.nvl.virginia.edu/ ->| http://www.freebsd.org/