From owner-freebsd-smp Mon Apr 12 18:26:45 1999 Delivered-To: freebsd-smp@freebsd.org Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.149.24]) by hub.freebsd.org (Postfix) with ESMTP id 0A32C14D58 for ; Mon, 12 Apr 1999 18:26:40 -0700 (PDT) (envelope-from bryan@cheops.anu.edu.au) Received: (from bryan@localhost) by cheops.anu.edu.au (8.9.1/8.9.1) id LAA24023 for freebsd-smp@freebsd.org; Tue, 13 Apr 1999 11:24:19 +1000 (EST) From: bryan collins Message-Id: <199904130124.LAA24023@cheops.anu.edu.au> Subject: 3.1 SMP broke, 3.0 SMP works To: freebsd-smp@freebsd.org Date: Tue, 13 Apr 1999 11:24:18 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've been having major problems with a new Dual PII server built about 2 weeks ago. We loaded 3.1R with an SMP kernel, and get reboots about out of kvm and sometimes just reboot without a panic message or dump. We tried all sorts of things, even a patch that I found mentioned about increasing the kernel mem size, reducing MAXUSERS, NMBCLUSTERS etc. No luck. We eventually gave up on 3.1R and found a 3.0R dist on an ftp sever, loaded it up with same SMP params, and so far its been up almost 2 days. More than twice aslong as the uptimes with 3.1R So it seems somethings changed from 3.0 to 3.1 thats causes us this drama. Running the same setup with 3.1R NON-SMP kernel, lasted just over 24 hours. The machine runs squid and mail, so gets a bit of traffic. Anyone else gone to 3.1R SMP and seen hassles? Cheers Bry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message