From owner-freebsd-current@FreeBSD.ORG Mon Jun 7 21:45:21 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 AA6A116A4CE; Mon, 7 Jun 2004 21:45:21 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id D085D43D4C; Mon, 7 Jun 2004 21:45:20 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (ppp-67-38-164-15.dsl.wotnoh.ameritech.net [67.38.164.15]) (authenticated bits=0)i57LcKQr042367 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 7 Jun 2004 17:38:56 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-current@freebsd.org Date: Mon, 7 Jun 2004 17:45:02 -0400 User-Agent: KMail/1.6.2 References: <40BF38B4.6090208@gmx.net> <40C4CA71.5010800@gmx.net> <200406071732.33715.jhb@FreeBSD.org> In-Reply-To: <200406071732.33715.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200406071745.04697.mistry.7@osu.edu> X-Spam-Status: No, hits=-3.9 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_NJABL,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL,X_NJABL_DIALUP version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) 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 21:45:21 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 07 June 2004 05:32 pm, John Baldwin wrote: > On Monday 07 June 2004 04:05 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 disabli= ng > > >>>>>> ACPI at the loader prompt (set hint.acpi.0.disabled=3D1) I get t= he > > >>>>>> 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? > > > > Find the dmesg aswell as the diff to the old kernel attached. > > Grr, ok. It's going to require better acpi_pci_link support which is sti= ll > being worked on. I'm getting this too: rl0: watchdog timeout Would another dmesg be useful? =2D --=20 Anish Mistry =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAxOHexqA5ziudZT0RAoCnAJ0dHrIXHHSk0UQS1tDed3mz4uFu5wCbBOel Xi6F/t5GfnML0JbnvQhCb1U=3D =3DFiqu =2D----END PGP SIGNATURE-----