From owner-freebsd-stable@FreeBSD.ORG  Fri May 11 01:50:35 2007
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id BEAB716A405
	for <freebsd-stable@freebsd.org>; Fri, 11 May 2007 01:50:35 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id AA36513C46C
	for <freebsd-stable@freebsd.org>; Fri, 11 May 2007 01:50:35 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196])
	by elvis.mu.org (Postfix) with ESMTP id 456AD1A3C19;
	Thu, 10 May 2007 18:51:20 -0700 (PDT)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id DA4855159E; Thu, 10 May 2007 21:50:34 -0400 (EDT)
Date: Thu, 10 May 2007 21:50:34 -0400
From: Kris Kennaway <kris@obsecurity.org>
To: Scott Swanson <scotts@inetz.com>
Message-ID: <20070511015034.GA77771@xor.obsecurity.org>
References: <46438569.1000506@inetz.com>
	<20070510214348.GA68925@xor.obsecurity.org>
	<4643C010.7060302@inetz.com>
	<20070511010654.GA75689@xor.obsecurity.org>
	<4643C34F.9070504@inetz.com>
	<20070511011929.GA76360@xor.obsecurity.org>
	<4643CA85.90800@inetz.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4643CA85.90800@inetz.com>
User-Agent: Mutt/1.4.2.2i
Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org>
Subject: Re: panic: spin lock held too long (w/ backtrace)
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: Fri, 11 May 2007 01:50:35 -0000

On Thu, May 10, 2007 at 07:44:37PM -0600, Scott Swanson wrote:
> >> (kgdb) proc 18303
> >> (kgdb) bt
> >> #0  0xc0644f5b in sched_switch (td=0xc95a5900, newtd=0xc92aad80,
> >> flags=0) at /usr/src/sys/kern/sched_4bsd.c:973
> >> #1  0xeaa6dcb4 in ?? ()
> >> #2  0x00000001 in ?? ()
> >> #3  0x0ee2c000 in ?? ()
> >> #4  0x00000000 in ?? ()
> >> #5  0x00004000 in ?? ()
> >> #6  0x00000000 in ?? ()
> >> #7  0x00000000 in ?? ()
> >> #8  0xc95a5900 in ?? ()
> >> #9  0xeaa6dd30 in ?? ()
> >> #10 0xc081a8fb in syscall (frame=Cannot access memory at address 0x4008
> >> ) at /usr/src/sys/i386/i386/trap.c:983
> >> Previous frame inner to this frame (corrupt stack?)
> > 
> > Garbage :(  Are you using any modules?
> > 
> > Kris
> 
> Well, I do have ASR_COMPAT enabled in the kernel to monitor the Adaptec
> 2010S controller.
> 
> # asr old ioctls support, needed by raidutils
> options         ASR_COMPAT
> 
> In retrospect I guess I should have started investigating there first.
> Is there a good way to determine if this is actually the problem without
> just recompiling the kernel and hoping for the best?
> 
> I see that it is still listed in NOTES, but maybe this option should now
> be avoided?

Dunno how this answers my question so I'll retry :) Are you using any
.ko modules for things not compiled into your kernel?  It's the only
way I can think of to get a nonsense backtrace like that (you have to
do more work to trace kernels with modules loaded).  Check kldstat.

Kris