From owner-freebsd-current@FreeBSD.ORG Mon Aug 30 19:23:17 2004 Return-Path: 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 12B8616A4CE for ; Mon, 30 Aug 2004 19:23:17 +0000 (GMT) Received: from shub-internet.kew.com (h00062574bf3c.ne.client2.attbi.com [66.30.223.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id E180143D58 for ; Mon, 30 Aug 2004 19:23:16 +0000 (GMT) (envelope-from ahd@kew.com) Received: by shub-internet.kew.com (Postfix, from userid 1001) id 6B6CD12351; Mon, 30 Aug 2004 15:23:16 -0400 (EDT) To: freebsd-current@freebsd.org In-Reply-To: <20040830.124141.44509158.imp@bsdimp.com> Message-Id: <20040830192316.6B6CD12351@shub-internet.kew.com> Date: Mon, 30 Aug 2004 15:23:16 -0400 (EDT) From: ahd@kew.com (Drew Derbyshire) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 19:23:17 -0000 > From imp@bsdimp.com Mon Aug 30 14:50:50 2004 > : 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. Who makes the call (or the commit)? The cost is ~ 55K on disk (which seems excessive) with current build, I assume that's bloated by the current kernel options. > : 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. Well, it at least it didn't panic on me, which previous experiments (months ago) were prone to do. -ahd- p.s. Sorry about the original mail being ugly MS HTML. I needed the MIME, not the HTML.