From owner-freebsd-stable Thu Sep 28 3:32:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 0D0CD37B424 for ; Thu, 28 Sep 2000 03:32:35 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8SAXnA00349; Thu, 28 Sep 2000 03:33:50 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009281033.e8SAXnA00349@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: BSD Cc: stable@freebsd.org Subject: Re: More panics (different hardware) In-reply-to: Your message of "Thu, 28 Sep 2000 05:26:44 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 03:33:49 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please press the 'scroll lock' key to scroll upwards and report the real error message. Before you post it, take a few minutes to check the handbook section on kernel debugging and try giving us enough information to actually help you. You wouldn't ring your doctor up and say "Hey doc, I hurt" and expect him to tell you what's wrong. Why do you subject us to a comparable form of abuse? > Just as a follow up to my constant panic report on 4.1-S with my > Athlon system, I'd like to say that my Pentium 200 system has now joined > in. This P200 system has served me with 100% rock solid stability for > years. Not once has it had any weird behaviour. Anyways, the behaviour > on both systems is the same. A fault at virtual address 0x30, preceeded > by another fault which by that time has scrolled off the screen. The key > phrase here seems to be "supervisor read, page not present". > > I feel I should add here that I am a commercial unix shell > provider, and so I get the worst imaginable traffic on the internet. This > P200 box doesn't allow shell access though, since it's only a web server. > > A system with 3 bad sticks of ram, and a rock solid system > suddenly going bad? C'mon guys. Will nothing short of ECC RAM prove to > you guys the existance of a software fault? Anybody wanna lend me some? > :) (the P200 RAM is 72-pin .... so no, not the same kind as the Athlon's) > > BTW, 3.5-S ran fine on both systems...at least until it had to > access the large Maxtor HD in the Athlon ... which is what prompted me to > go to 4.1-S. > > Finally, for some good news. The P200 system is physically > accessible to me, so I will try to find a spare hard drive, and make some > crash dumps for the list's benefit. > > Thanks for all the responses I've gotten on this subject! They're > greatly appreciated and help me maintain my sanity. :) > > --Bart > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message