From owner-freebsd-current@FreeBSD.ORG Thu Jul 17 08:58:08 2003 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 ED1F437B401 for ; Thu, 17 Jul 2003 08:58:08 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDE3A43FBD for ; Thu, 17 Jul 2003 08:58:07 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h6HFw5FL006772; Thu, 17 Jul 2003 09:58:06 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 17 Jul 2003 09:58:00 -0600 (MDT) Message-Id: <20030717.095800.45156295.imp@bsdimp.com> To: roth@iam.unibe.ch From: "M. Warner Losh" In-Reply-To: <20030717082918.GA21592@speedy.unibe.ch> References: <20030717012649.54310.qmail@secure-info.ca> <20030717082918.GA21592@speedy.unibe.ch> X-Mailer: Mew version 2.2 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: Problems with fxp0 on T30 with 5.1-RELEASE 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: Thu, 17 Jul 2003 15:58:09 -0000 In message: <20030717082918.GA21592@speedy.unibe.ch> Tobias Roth writes: this is caused by : an irq conflict. the bug was introduced some time between 5.0 and : 5.1. i have no idea how to solve this, maybe someone else can help : here. maybe the ibm ps2 tool offers some help. details? : another workaround is to free an irq. for me, disabling the pcmcia : stuff in the kernel config helped. others reported that disabling : the serial port helped for them. interesting. : this has to be fixed before 5.2, imho. it renders a default install : on thinkpads useless. note that this does NOT happen on all thinkpad : systems, i didn't figure out what makes up the difference. sounds like a bug that needs to be fixed, but the details are so vague as to make that impossible. chances are very good that someone with a clue (like me) will need a machine that fails to fix it. Warner