From owner-freebsd-current@FreeBSD.ORG  Sun Jul 31 00:00:41 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 7FDA016A41F;
	Sun, 31 Jul 2005 00:00:37 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BBCB243D53;
	Sun, 31 Jul 2005 00:00:12 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j6UNwn2L075063;
	Sat, 30 Jul 2005 17:58:53 -0600 (MDT) (envelope-from imp@bsdimp.com)
Date: Sat, 30 Jul 2005 17:59:39 -0600 (MDT)
Message-Id: <20050730.175939.108405618.imp@bsdimp.com>
To: lehmann@ans-netz.de
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20050731011147.2c00c819.lehmann@ans-netz.de>
References: <20050731003652.12223405.lehmann@ans-netz.de>
	<20050730.164856.113103353.imp@bsdimp.com>
	<20050731011147.2c00c819.lehmann@ans-netz.de>
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: current@freebsd.org
Subject: Re: mlx(4) fully and ep(4) partially broken on 6.0
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Sun, 31 Jul 2005 00:00:41 -0000

In message: <20050731011147.2c00c819.lehmann@ans-netz.de>
            Oliver Lehmann <lehmann@ans-netz.de> writes:
: M. Warner Losh wrote:
: 
: > In message: <20050731003652.12223405.lehmann@ans-netz.de>
: >             Oliver Lehmann <lehmann@ans-netz.de> writes:
: > : same as ep0 wants to run with:
: > : 
: > : ep0: <3Com 3C509-Combo Etherlink III> at port 0x300-0x30f irq 9 on isa0
: > : ep0: No irq?!
: > : panic: resource_list_release: resource entry is not busy
: > : Uptime: 1s
: > 
: > Bummer.  Any chance you can get a traceback?
: 
: Disks are not initialized when the pannic occures...
: Any info I could provide you from within the kdb? A ,,where'' output? Is
: kdb useable from serial console so far?

enable ddb, and use 'trace'.  However, I think I understand where it
is happening.

: > : As you can see, it looks like the card is not configured as PnP (because
: > : that would add "(PnP)" to the description).
: > : 
: > : On my router, fxp3 has irq 9 - Maybe it is irq sharing related? But I
: > : wonder why it works with 5.4 without problems...
: > 
: > You can't share IRQs with ISA bus.  You'll need to find out what
: > changed that causes fxp3 to use irq 9 now.  Maybe it is APIC related?
: 
: As I can see in an old 5.4 dmesg ep0 was the only card with irq9, fxp3
: had 11 on 5.4.

OK.  Sounds like either an unknown changes in the BIOS configuration
(unlikely) or a subtle change in how we route interrupts that the BIOS
doesn't.

Warner