From owner-freebsd-current@FreeBSD.ORG Fri Jul 18 03:53:54 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 0529937B401 for ; Fri, 18 Jul 2003 03:53:54 -0700 (PDT) Received: from mailhub01.unibe.ch (mailhub01-skge0.unibe.ch [130.92.9.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29DD343FCB for ; Fri, 18 Jul 2003 03:53:52 -0700 (PDT) (envelope-from roth@iam.unibe.ch) Received: from localhost (localhost [127.0.0.1]) by mailhub01.unibe.ch (Postfix) with ESMTP id 6A6EB25BA1B; Fri, 18 Jul 2003 12:53:50 +0200 (MEST) Received: from mailhub01.unibe.ch ([127.0.0.1]) by localhost (mailhub01 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04007-01-95; Fri, 18 Jul 2003 12:53:49 +0200 (MEST) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub01.unibe.ch (Postfix) with ESMTP id 7D4B325BA18; Fri, 18 Jul 2003 12:53:49 +0200 (MEST) Received: from speedy.unibe.ch (speedy [130.92.64.35]) by asterix.unibe.ch (8.11.6+Sun/8.11.6) with ESMTP id h6IArnK15308; Fri, 18 Jul 2003 12:53:49 +0200 (MET DST) Received: (from roth@localhost) by speedy.unibe.ch (8.11.6+Sun/8.10.2) id h6IArlt10890; Fri, 18 Jul 2003 12:53:47 +0200 (MEST) Date: Fri, 18 Jul 2003 12:53:47 +0200 From: Tobias Roth To: "M. Warner Losh" Message-ID: <20030718105347.GA9225@speedy.unibe.ch> References: <20030717012649.54310.qmail@secure-info.ca> <20030717082918.GA21592@speedy.unibe.ch> <20030717.095800.45156295.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030717.095800.45156295.imp@bsdimp.com> User-Agent: Mutt/1.4i X-Operating-System: SunOS speedy 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-80 X-Virus-checked: by University of Berne 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: Fri, 18 Jul 2003 10:53:54 -0000 On Thu, Jul 17, 2003 at 09:58:00AM -0600, M. Warner Losh wrote: > 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? kevin oberman suggested the use of the ps2 utility for thinkpads. i did not have the chance to try it out myself. > : 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. shortly after i discovered this problem, my TP started to have immense problems with the summer heat and started crashing during buildworlds. that's why i didn't look into the irq problem any further at this time. now, i just got my TP back from ibm, and while they did not really fix the heat problem (i will send it back to them next week), i got around to do some irq tests. irqs 0,1,8,12,13,14,15 are set and no subject of manual change. irq 2, i have no idea about. irq 3 and 4 are the infrared device and the serial port. irq 7 is the parallel port irq 6 can be freed by disabling legacy floppy support in the bios. however it does not seem be taken by a different device when freed. this leaves us with irqs 5,9,10,11 to distribute in the pci section of the bios. after some playing around, i set INT[A-H] PCI IRQ to 5,9,10,11,11,9,10,11. I do not know whether the order matters, but the distribution does. like this, every irq is assigned to two devices: 5->uhic0 and cbb0, 9->cbb1 and pcm0, 10->uhic2 and wi0, 11->uhic1 and fxp0. the only drawback i encountered with these settings was a short hang during boot when probing uhic2. it did not hang there before i started switching around irqs, but i do not know what is wrong here. other than that, everything works now. > : 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. the only odd thing is that 5.0 did not have this bug, while 5.1 has it. if it needs fixing is up to you, i am now happy with the current solution. but then, the default bios settings are so stupid that it may not be feasable to do anything about it. hope that helps, t.