From owner-freebsd-current@FreeBSD.ORG Tue Mar 30 15:31:22 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 0C2CB16A4CF for ; Tue, 30 Mar 2004 15:31:22 -0800 (PST) Received: from gabby.gsicomp.on.ca (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [69.197.202.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF00243D2D for ; Tue, 30 Mar 2004 15:31:20 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by gabby.gsicomp.on.ca (8.12.9p2/8.12.9) with ESMTP id i2UNripU018153; Tue, 30 Mar 2004 18:53:45 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <00a201c416ae$a71a8470$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Tobias Roth" References: <002501c415fb$aa8b7fa0$1200a8c0@gsicomp.on.ca> <20040330060052.GB24456@speedy.unibe.ch> Date: Tue, 30 Mar 2004 18:28:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-current@freebsd.org Subject: Re: Problems with fxp0 and wi0 devices 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: Tue, 30 Mar 2004 23:31:22 -0000 > On Mon, Mar 29, 2004 at 09:06:51PM -0500, Matt Emmerton wrote: > > I'm running FreeBSD 5.2.1-RELEASE on a ThinkPad T23 and I can't use either > > of the built-in fxp0 or wi0 network adapters. > > > > Whenever I try and configure them with dhclient, dhclient just hangs. > > Whenever I try and configure them manually (static IP and route), packets > > never go anywhere. > > Whenever I access fxp0, I get "fxp0: device timeout" messages on my screen. > > > > looks like the irq problems i and a few other people experienced on their > T30s. the problem popped up some time between 5.0 and 5.1 and nobody ever > really fixed it, as it was machine specific (machine, not model or brand!), > and not really reproductable. but the workaround was to change irq mapping > in bios around a bit (from all automatically to some random combination of > settings). the values that worked for one person didn't for the next. I wonder if different BIOS revisions change the situation. That sounds like the only logical explanation. I checked and I'm at the latest BIOS, so no easy fix there :( > a few weeks after i upgraded to 5.2.1 i noticed by coincidence that the > problem disappeared again for me. I upgraded last night from 5.1 to 5.2.1 and the problems persisted. I will poke around. Thanks for the information. -- Matt Emmerton