From owner-freebsd-current@FreeBSD.ORG Fri Jun 4 08:00:47 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 60E5116A4DA for ; Fri, 4 Jun 2004 08:00:47 -0700 (PDT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0E2B43D60 for ; Fri, 4 Jun 2004 08:00:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6616 invoked from network); 4 Jun 2004 15:00:31 -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 15:00:31 -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 i54F0Spq081499; Fri, 4 Jun 2004 11:00:28 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Fri, 4 Jun 2004 11:01:15 -0400 User-Agent: KMail/1.6 References: <40BF38B4.6090208@gmx.net> In-Reply-To: <40BF38B4.6090208@gmx.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406041101.15208.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org 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: Fri, 04 Jun 2004 15:00:47 -0000 On Thursday 03 June 2004 10:41 am, Andreas Moeller wrote: > Hello list! > > 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? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org