Xref: utzoo unix-pc.general:7212 comp.sys.att:11466 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!convex!egsner!texrex!rmfowler From: rmfowler@texrex.uucp (Rex Fowler) Newsgroups: unix-pc.general,comp.sys.att Subject: Re: panic: page fault in kernel (3B1/3.51m) Keywords: 3b1 panic crash loadable drivers Message-ID: <1991Jan12.022328.16645@texrex.uucp> Date: 12 Jan 91 02:23:28 GMT References: <1991Jan10.201457.16268@sonyd1.Broadcast.Sony.COM> <4832@umbc3.UMBC.EDU> <37874@cup.portal.com> Reply-To: rmfowler%texrex@cirr.com Organization: texrex - Personal System - Dallas, TX Lines: 29 A few weeks ago I posted that I had finally fixed my 3b1 kernel parity error crash problem. Well, I lied. It must have been a lucky 30 hours uptime since the normal uptime was around 1-4 hours before crashing. This crash problem lasted over 4 months! 3 days ago I decided to see what drivers I had loaded. I was surprised. I have a starlan card but it never occurred to me that a loadable driver was being loaded at boottime. I had removed the starlan card previously and still had crashes so i dismissed the starlan card as the problem. So, I decided to play with the drivers and here's what happened. I replaced lipc with nipc, took out starlan driver, added ate driver to /etc/lddrv/drivers. Rebooted.. I've been up for 3 days now and TODAY I see postings about the loadable drivers causing kernel parity error/crashes! Why didn't this discussion come 4 months ago! :^) Anyway, I still don't know which driver was guilty since I changed so many of them at once. After my machine has been up for 5-6 days, (just to be safe) I will try to isolate which of the drivers was screwing me. Right now I am just relieved that FINALLY, 4 months later, I have a reliable machine! I am pretty sure that it was the starlan driver. I didn't get the errors associated with the lipc driver that I saw in todays posting by Thad. -- Rex Fowler UUCP: egsner!texrex!rmfowler