From owner-freebsd-stable@FreeBSD.ORG  Sat Mar 20 11:55:30 2010
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 E3D731065670;
	Sat, 20 Mar 2010 11:55:30 +0000 (UTC)
	(envelope-from j@uriah.heep.sax.de)
Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9])
	by mx1.freebsd.org (Postfix) with ESMTP id 850B38FC13;
	Sat, 20 Mar 2010 11:55:30 +0000 (UTC)
Received: by uriah.heep.sax.de (Postfix, from userid 107)
	id 82B7E1C; Sat, 20 Mar 2010 12:55:28 +0100 (MET)
Date: Sat, 20 Mar 2010 12:55:28 +0100
From: Joerg Wunsch <j@uriah.heep.sax.de>
To: freebsd-stable@freebsd.org, Warner Losh <imp@freebsd.org>
Message-ID: <20100320115528.GA50212@uriah.heep.sax.de>
References: <20100318192758.GP52442@uriah.heep.sax.de>
	<201003190837.48346.jhb@freebsd.org>
	<20100319211456.GA17662@uriah.heep.sax.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100319211456.GA17662@uriah.heep.sax.de>
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E
X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584  1070 F48C A81B 69A8 5873
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: 
Subject: Re: Strange problem: if_xe only works in GENERIC kernel
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
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: Sat, 20 Mar 2010 11:55:31 -0000

As Joerg Wunsch wrote:

> OK, at kernel #11 :), I can now say it's the USB subsystem.  Just
> leaving "device usb" (and also "device uhci") in makes it work.
> 
> So the question appears to be why keeping the USB driver in makes the
> interrupt storm detection work...

Maybe that's the relationship?

camel# dmesg | fgrep 'irq 11'
vgapci0: <VGA-compatible display> mem 0xe0000000-0xe0ffffff,0x70000000-0x703fffff,0x70400000-0x704fffff irq 11 at device 0.0 on pci1
cbb0: <TI1251 PCI-CardBus Bridge> mem 0x50102000-0x50102fff irq 11 at device 2.0 on pci0
cbb1: <TI1251 PCI-CardBus Bridge> mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x8400-0x841f irq 11 at device 7.2 on pci0
xe0: <Intel EtherExpress(TM) PRO/100 PC Card Mobile Adapter16> at port 0x100-0x10f iomem 0x20000000-0x20000fff irq 11 function 0 config 1 on pccard1

I guess vgapci0 doesn't really use interrupts, so this leaves cbb0/1
and uhci0 sharing an interrupt.  Apparently, the interrupt storm at
cbb gets detected correctly as long as at least another device
installs an interrupt handler on irq 11.

Does that make any sense as an explanation?

I can live with the current situation (and proceed in setting up that
machine as a firewall, which was my original intention), although I
could also spend another day into debugging that symptom if someone
can get me some directions.
-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)