Date: Sat, 27 Jul 1996 12:29:37 -0700 (PDT) From: "Keith Beattie[SFSU Student]" <beattie@george.lbl.gov> To: fqueries@jraynard.demon.co.uk (James Raynard) Cc: questions@freebsd.org Subject: Re: vnode_pager_input: I/O read error Message-ID: <199607271929.MAA09047@george.lbl.gov> In-Reply-To: <199607271753.RAA03268@jraynard.demon.co.uk> from "James Raynard" at Jul 27, 96 05:53:00 pm
next in thread | previous in thread | raw e-mail | index | archive | help
James Raynard wrote: > > > > > I just compiled a new kernel and I'm now having some serious > > problems... > > > > Getting signal 11's for no apparent reason is a classic sign of a > hardware problem, most commonly a bad SIMM, although they can also > be caused by problems with cache or the motherboard. > Things are getting worse. When I boot, fsck fails and running it manually it succeds on my first ide drive (the one with / on it) but then while checking my SCSI drive it dies from a sig 8: --- manual fsck run --- *** /dev/rsd0s1e BAD SUPERBLOCK: VALUES IN SUPERBLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE pid 13: fsck: uid 0: exited on signal 8 floating exception --- manual fsck run --- I tried it several times and it always dies the same way. > > The best thing to do now is probably to try swapping around SIMMs, > if you have any spare ones around. > I don't have any spare ones. I'd just have to remove one bank at a time. But are sig 8's indicative of bad SIMMs? I *need* this to be a software problem, I can spare the time to reformat/reintsall/whatever, new hardware is a different story... Thanks, Keith -- // Keith Beattie Lawrence Berkeley Laboratory (LBL) \\ // SFSU Grad Student Imaging and Distributed Computing Group (ITG) \\ // KSBeattie@lbl.gov http://www-itg.lbl.gov/~beattie \\ // 1 Cyclotron Rd. MS: 50B-2239 Berkeley, CA 94720 (510) 486-6692 \\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607271929.MAA09047>