From owner-freebsd-current  Fri Apr 11 03:39:57 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA10018
          for current-outgoing; Fri, 11 Apr 1997 03:39:57 -0700 (PDT)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10013
          for <freebsd-current@freebsd.org>; Fri, 11 Apr 1997 03:39:54 -0700 (PDT)
Received: from nessie.mcc.ac.uk (nessie.mcc.ac.uk [130.88.200.20])
          by who.cdrom.com (8.8.5/8.6.11) with ESMTP id DAA06587
          for <freebsd-current@freebsd.org>; Fri, 11 Apr 1997 03:39:50 -0700 (PDT)
Received: from albatross.mcc.ac.uk by nessie.mcc.ac.uk with SMTP (PP);
          Fri, 11 Apr 1997 11:37:15 +0100
Received: (from ip@localhost) by albatross.mcc.ac.uk (8.8.5/8.6.12) id LAA18207 
          for freebsd-current@freebsd.org;
          Fri, 11 Apr 1997 11:37:05 +0100 (BST)
From: Ian Pallfreeman <ip@mcc.ac.uk>
Message-Id: <199704111037.LAA18207@albatross.mcc.ac.uk>
Subject: Re: wdx interrupt timeouts (fwd)
To: freebsd-current@freebsd.org
Date: Fri, 11 Apr 1997 11:37:05 +0100 (BST)
In-Reply-To: <199704110944.MAA28535@shadows.aeon.net> from "mika ruohotie" at Apr 11, 97 12:44:27 pm
Reply-To: ip@mcc.ac.uk
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

bsdcur@shadows.aeon.net (mika ruohotie) wrote:

> backup, get another drive.

Thanks for the suggestion; I probably will, but:

	Fatal trap 12: page fault while in kernel mode
	fault virtual address	= 0x4e3a1bd4
	fault code		= supervisor read, page not present
	instruction pointer	= 0x8:0xf010144c
	stack pointer		= 0x10:0xf6b13d80
	frame pointer		= 0x10:0xf6b13d9c
	code segment		= base 0x0, limit 0xfffff, type 0x1b
				= DPL 0, pres 1, def32 1, gran 1
	processor eflags	= interrupt enabled, resume, IOPL = 0
	current process		= 7329 (perl)
	interrupt mask		= bio
	panic: page fault
	
shouldn't be happening just because I'm trying to read a possibly (but not
very likely) bad drive, should it? Note the subject line -- this started with
innocuous "interrupt timeout" messages, progressed to hard errors and now we're
onto panics. I hate IDE, even brand-new supposedly self-correcting drives...

I'm also stuck at first base with the crash dump:


	GDB 4.16 (i386-unknown-freebsd), 
	Copyright 1996 Free Software Foundation, Inc...
	IdlePTD 1ef000

	kernel symbol `kstack' not found.
	(kgdb)

Any suggestions, offers of help, or brain transplants gratefully receieved...

"Why does it always happen to me?"

Ian.