From owner-freebsd-stable Tue Jul 20 7:44:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.digitalselect.net (mailhost.digitalselect.net [209.136.236.13]) by hub.freebsd.org (Postfix) with ESMTP id B3F73152F6 for ; Tue, 20 Jul 1999 07:44:32 -0700 (PDT) (envelope-from adhir@forumone.com) Received: from adhir ([216.181.56.84]) by mailhost.digitalselect.net (8.9.1/8.8.7) with SMTP id KAA12671; Tue, 20 Jul 1999 10:43:53 -0400 From: "Alok K. Dhir" To: , Subject: RE: Panic in latest 3.2-Stable Date: Tue, 20 Jul 1999 10:41:30 -0400 Message-ID: <003b01bed2bd$f4363e00$5438b5d8@forumone.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pull the new RAM and see if you still have the problem. If not, its your RAM. If so, leave the RAM in, swap out the CPU and try again (not sure why the CPU would cause this, but in the interest of being thorough...). If none of these works, put the machine back to its original HW config (RAM and CPU) and try yet again. My guess is you'll find the source of your problem within these steps. You may also want to check/undo any BIOS setting changes you might have made... Are you overclocking? Don't... Another thing to consider: - Some motherboards can't hack 1gb of ram regardless of their specs. I'm not sure if the Supermicro P6SBU is one of these, but I can tell you I've had big problems with a supermicro board (P6SKE) in the past which I couldn't fix until I dumped it for an Aopen (AX6B - highly recommended). For this reason, your new RAM may not necessarily be bad even if pulling it gets it working again... In fact, if it does get it working, I'd try switching the old 512mb for the new as a final test to see if the RAM is suspect or not. Process of elimination. > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of > tcobb@staff.circle.net > Sent: Tuesday, July 20, 1999 10:24 AM > To: freebsd-stable@freebsd.org > Subject: Panic in latest 3.2-Stable > > > Just upgraded a PII 450 (512MB RAM) to > a PIII 550 with 1GB RAM. The motherboard > is a Supermicro P6SBU and the prior > configuration was rock-solid for months. > > Within 1 hour of upgrading to the new processor > and memory, we got a panic and reboot (didn't > catch the message). I then upgraded from > 3.2-Release to 3.2-Stable (19990720), same > thing, panic in about 1 hour. I caught the > panic message, "Supervisor read, page not present". > This is not a debugging kernel and this is on a > live production box so I can't futz with it > very much. > > Anyone seen it, and does anyone have a suggestion? > > Kernel config has maxusers set to 128, NMBCLUSTERS > set to 8192. Is this, perhaps, a tuning issue? > > Expedited help is appreciated! > > -Troy Cobb > Circle Net, Inc. > http://www.circle.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message