From owner-freebsd-current@FreeBSD.ORG Mon Jun 7 12:06:26 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 23D4716A4D0 for ; Mon, 7 Jun 2004 12:06:26 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0444543D53 for ; Mon, 7 Jun 2004 12:06:26 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20922 invoked from network); 7 Jun 2004 12:06:22 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 7 Jun 2004 12:06:21 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i57C6JT3002223; Mon, 7 Jun 2004 08:06:19 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 7 Jun 2004 08:07:13 -0400 User-Agent: KMail/1.6 References: <40BF38B4.6090208@gmx.net> <200406041521.34813.jhb@FreeBSD.org> <40C0FEFB.8050605@gmx.net> In-Reply-To: <40C0FEFB.8050605@gmx.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406070807.13562.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Andreas Moeller Subject: Re: fxp(4) device timeouts ACPI related? 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, 07 Jun 2004 12:06:26 -0000 On Friday 04 June 2004 07:00 pm, Andreas Moeller wrote: > >>>>The ACPI updates predating last weekend seem to have broken my fxp(4) > >>>>card (Intel PRO/100 S, Intel 82550 chip). Without disabling ACPI at the > >>>>loader prompt (set hint.acpi.0.disabled=1) I get the consecutive > >>>> message of the device timing out and network is unusable. > >>>> > >>>>Perhaps this is useful information for everybody desiring to workaround > >>>>the problem or even some developer to have a closer look at it. If a > >>>>more detailed description of my setup is needed, just let me know. > >>> > >>>Can you get before and after dmesg's and post a diff? > >> > >>Of course. diff is attached, the kernel is an unmodified GENERIC. > > > > Looks like !ACPI gives IRQ 11 to everyone and ACPI gives some devices IRQ > > 5 and some IRQ 11. Can you get a dmesg from the older kernel with ACPI > > enabled and generate a diff of that dmesg against the current kernel with > > ACPI? > > Attached. I had to get some older sources and build the kernel since I > didn't keep an old enough kernel around. The sources used date to May > 28th, 2:50am (UTC) and network works with ACPI enabled. > > I'm by no means an expert but I don't see any new insight revealed by > the diff between those two dmesgs. How about a dmesg from a boot -v with the new kernel? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org