From owner-freebsd-current@FreeBSD.ORG Fri Jun 4 12:21:19 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 854C416A4E6 for ; Fri, 4 Jun 2004 12:21:18 -0700 (PDT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id F179043D31 for ; Fri, 4 Jun 2004 12:21:17 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 11935 invoked from network); 4 Jun 2004 19:20:53 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 4 Jun 2004 19:20:52 -0000 Received: from 10.50.41.233 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i54JKnAK083127; Fri, 4 Jun 2004 15:20:49 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Andreas Moeller Date: Fri, 4 Jun 2004 15:21:34 -0400 User-Agent: KMail/1.6 References: <40BF38B4.6090208@gmx.net> <200406041101.15208.jhb@FreeBSD.org> <40C0B150.1030702@gmx.net> In-Reply-To: <40C0B150.1030702@gmx.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406041521.34813.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org 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: Fri, 04 Jun 2004 19:21:19 -0000 On Friday 04 June 2004 01:28 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? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org