From owner-freebsd-current@FreeBSD.ORG  Mon Aug 30 18:44:34 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0014916A4CE
	for <freebsd-current@freebsd.org>;
	Mon, 30 Aug 2004 18:44:33 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9C16243D4C
	for <freebsd-current@freebsd.org>;
	Mon, 30 Aug 2004 18:44:33 +0000 (GMT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.11/8.12.11) with ESMTP id i7UIfY3s054623;
	Mon, 30 Aug 2004 12:41:35 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Mon, 30 Aug 2004 12:41:41 -0600 (MDT)
Message-Id: <20040830.124141.44509158.imp@bsdimp.com>
To: ahd@kew.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <012301c48e25$14924180$84cba8c0@hh.kew.com>
References: <012301c48e25$14924180$84cba8c0@hh.kew.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: PCI SIO devices hog interrupts, cause lock order problems
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Aug 2004 18:44:34 -0000

In message: <012301c48e25$14924180$84cba8c0@hh.kew.com>
            "Andrew H. Derbyshire" <ahd@kew.com> writes:
: Basically, any PCI SIO device hogs its interrupt if the PUC device is not
: also in the kernel, and this causes real problems for any environment like
: mine where pulling the modem is not trivial.  Does the distributed GENERIC
: kernel have room for the PUC device?  Are there side effects that PUC should
: be excluded from GENERIC?

puc should be in GENERIC, imho.

: As a bonus, there appears to be a bug with kernel locking exposed by the
: problem.  With the stock generic kernel, the XL device reports it couldn't
: map the interrupt, and then a lock order reversal is reported.  (See the
: attached log for the gory details).

This is a known problem.

Warner