From owner-freebsd-stable@FreeBSD.ORG  Thu Mar  6 10:19:33 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4F6DC1065673
	for <freebsd-stable@freebsd.org>; Thu,  6 Mar 2008 10:19:33 +0000 (UTC)
	(envelope-from jdc@parodius.com)
Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3])
	by mx1.freebsd.org (Postfix) with ESMTP id 3F7F98FC25
	for <freebsd-stable@freebsd.org>; Thu,  6 Mar 2008 10:19:33 +0000 (UTC)
	(envelope-from jdc@parodius.com)
Received: by mx01.sc1.parodius.com (Postfix, from userid 1000)
	id F38EA1CC038; Thu,  6 Mar 2008 02:19:32 -0800 (PST)
Date: Thu, 6 Mar 2008 02:19:32 -0800
From: Jeremy Chadwick <koitsu@freebsd.org>
To: Ken Chen <ken73.chen@gmail.com>
Message-ID: <20080306101932.GA83571@eos.sc1.parodius.com>
References: <d018a9bd0803060147w3ed05c67p4a6fb1ff478a4b7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d018a9bd0803060147w3ed05c67p4a6fb1ff478a4b7@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: freebsd-stable@freebsd.org
Subject: Re: 7.0 kernel panic on Intel SR2400
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2008 10:19:33 -0000

On Thu, Mar 06, 2008 at 05:47:16PM +0800, Ken Chen wrote:
> I upgrade from 6.2 to 7.0 on this Intel SR2400 server, then it panic after
> mounting storage when boot with 7.0 kernel.
> 
> I don't leave enough space for core dumping, so I should get nothing more
> for the panic. Any way to gather enough information for bug reporting?

I'm not sure what other options you have; it's important that people
understand when configuring disks, to make swap equal to (or larger
than) the amount of memory you have, AND make sure /var is larger than
the total amount of memory you have.

> ...
> iir0: <Intel Integrated RAID Controller> mem 0xfa000000-0xfbffffff irq 48 at device 8.0 on pci4
> iir0: [GIANT-LOCKED]
> ...
> ses0 at iir0 bus 1 target 6 lun 0
> ses0: <ESG-SHV SCA HSBP M22 0.06> Fixed Processor SCSI-2 device
> ses0: SAF-TE Compliant Device
> da0 at iir0 bus 2 target 0 lun 0
> da0: <Intel Host Drive   #00 > Fixed Direct Access SCSI-2 device
> da0: Tagged Queueing Enabled
> da0: 69931MB (143219475 512 byte sectors: 255H 63S/T 8915C)
> Trying to mount root from ufs:/dev/da0s1a
> ...

Shot in the dark, but the behaviour sounds similar to what I was seeing
when using Intel MatrixRAID in a RAID-1 array with 2 disks.  See here:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108924

-- 
| Jeremy Chadwick                                    jdc at parodius.com |
| Parodius Networking                           http://www.parodius.com/ |
| UNIX Systems Administrator                      Mountain View, CA, USA |
| Making life hard for others since 1977.                  PGP: 4BD6C0CB |