From owner-freebsd-stable@FreeBSD.ORG  Sat Mar 20 13:42:50 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 D8EE8106564A
	for <freebsd-stable@FreeBSD.org>; Sat, 20 Mar 2010 13:42:50 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mx1.freebsd.org (Postfix) with ESMTP id 9760B8FC15
	for <freebsd-stable@FreeBSD.org>; Sat, 20 Mar 2010 13:42:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o2KDfbXm093096;
	Sat, 20 Mar 2010 07:41:37 -0600 (MDT) (envelope-from imp@bsdimp.com)
Date: Sat, 20 Mar 2010 07:41:56 -0600 (MDT)
Message-Id: <20100320.074156.47703827965796709.imp@bsdimp.com>
To: joerg_wunsch@uriah.heep.sax.de, j@uriah.heep.sax.de
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20100320115528.GA50212@uriah.heep.sax.de>
References: <201003190837.48346.jhb@freebsd.org>
	<20100319211456.GA17662@uriah.heep.sax.de>
	<20100320115528.GA50212@uriah.heep.sax.de>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@FreeBSD.org
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
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 13:42:50 -0000

In message: <20100320115528.GA50212@uriah.heep.sax.de>
            Joerg Wunsch <j@uriah.heep.sax.de> writes:
: 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.

Does this happen on a cold boot or a warm boot?

Warner