From owner-freebsd-stable@FreeBSD.ORG  Sun Nov 30 20:46:59 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 720E8106567B
	for <stable@freebsd.org>; Sun, 30 Nov 2008 20:46:59 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from kennaway-macbookpro.local (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 4077D8FC19;
	Sun, 30 Nov 2008 20:46:59 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <4932FBC2.5060807@FreeBSD.org>
Date: Sun, 30 Nov 2008 12:46:58 -0800
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Holger Kipp <hk@alogis.com>
References: <20081130124938.GA44403@intserv.int1.b.intern>
In-Reply-To: <20081130124938.GA44403@intserv.int1.b.intern>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: stable@freebsd.org
Subject: Re: panic: spin lock held too long on 7.1-PRERELEASE (sio)
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: Sun, 30 Nov 2008 20:46:59 -0000

Holger Kipp wrote:
> Hi,
> 
> I currently encounter
> 
> spin lock 0xc0c83ba8 (sio) held by 0xc6337460 (tid 100005) too long
> panic: spin lock held too long
> cpuid=3
> 
> on hp server with two dual-core intel xeon (3.8GHz) and 3GB RAM.
> System is 7.1-PRELEASE last fetched 29.11.2008, 17:58 UTC.
> 
> This happens with VSCom Card that was previously in use in a
> 5.3-STABLE system (also hp server, but older hardware) without
> problems. The card is a 8-port serial card using puc0 and puc1
> with 4 ports each.
> 
> Interestingly, problem seems to occur only if sendfax is using
> devices attache to puc1. Works without problems at the moment
> with sendfax only using puc0-sios. See dmesg below.
> 
> Any ideas what might be causing this, or is this even related
> to kern/121322, 118044 or 117913?

Enable WITNESS in your kernel and try to reproduce the problem.  It 
should give additional information about the condition leading to the 
deadlock.

Kris