From owner-freebsd-scsi@FreeBSD.ORG  Wed Jun 11 23:04:08 2003
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 282B337B401
	for <freebsd-scsi@freebsd.org>; Wed, 11 Jun 2003 23:04:08 -0700 (PDT)
Received: from rootlabs.com (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 69BA443FDD
	for <freebsd-scsi@freebsd.org>; Wed, 11 Jun 2003 23:04:07 -0700 (PDT)
	(envelope-from nate@rootlabs.com)
Received: (qmail 42211 invoked by uid 1000); 12 Jun 2003 06:04:09 -0000
Date: Wed, 11 Jun 2003 23:04:09 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: Nick Twaddell <ntwaddel@webspacesolutions.com>
In-Reply-To: <003101c33087$9ec93310$0700a8c0@BEASTIE>
Message-ID: <20030611225948.M42109@root.org>
References: <003101c33087$9ec93310$0700a8c0@BEASTIE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-scsi@freebsd.org
cc: current@freebsd.org
Subject: Re: panic: page fault on FreeBSD 5.1 -RELEASE
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jun 2003 06:04:08 -0000

On Wed, 11 Jun 2003, Nick Twaddell wrote:
> I downloaded the 5.1 -RELEASE isos yesterday and tried to install them
> on my server.  My server is an IBM Xseries 330 server with an IBM
> ServeRAID 4LX Raid card.  I tried it with and without ACPI kernels and
> both resulted in a panic.  Here is the error..
>
> Fatal trap 12: page fault while in kernel mode
> Fault code		= supervisor read, page not present
> Instruction pointer	= 0x8:0xc29ee760
> Stack pointer		= 0x10:0xcd33fce4
> Frame pointer		= 0x10:0xcd33fd0c
> Code segment		= base 0x0, limit 0xfffff, type 0x1b
> 			= DPL 0, pres 1, def32 1, gran 1
> Processor eflags	= interupt enabled, resume, IOPL = 0
> Current process 	= 29 (irq9: ahc0 ips0)
> Trap number		= 12
>
> Panic = page fault
>
> Did I do something wrong or is there a problem with the driver? :(

I can't see an invalid eip, ebp, or esp in the above page fault.  It would
really help if you could get a backtrace ("tr" when you have DDB enabled).
BTW, re@ people:  could we add an option (under a sysctl but on by default
in the release) that does a backtrace on page fault?  We already have the
backtrace code accessible w/o DDB I believe.

-Nate