From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 4 09:32:33 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E23FA37B40D; Wed, 4 Jun 2003 09:32:33 -0700 (PDT) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 119BA43FA3; Wed, 4 Jun 2003 09:32:32 -0700 (PDT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost [127.0.0.1])h54GWka6046570; Wed, 4 Jun 2003 18:32:46 +0200 (CEST) (envelope-from girgen@pingpong.net) Date: Wed, 04 Jun 2003 18:32:46 +0200 From: Palle Girgensohn To: Shaun Jurrens , freebsd-net@freebsd.org, freebsd-hardware@freebsd.org Message-ID: <46490000.1054744366@rambutan.pingpong.net> In-Reply-To: <20030603152123.GM98443@nevada.skoleetaten.oslo.no> References: <20030603152123.GM98443@nevada.skoleetaten.oslo.no> X-Mailer: Mulberry/3.0.3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: fxp0: device timeout | SCB already complete (me too) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 16:32:34 -0000 Hi Shaun, Thanks for the input! Glad to hear I'm not the only one In my case, both the SCSI and NIC are integrated on the motherboard, so I cannot really move them around... :) Also, as I mentioned, I tried a de0 (PCI card, not onboard, and it literally stopped the machine). Is the de0 driver also a problem? /Palle --On tisdag, juni 03, 2003 17.21.23 +0200 Shaun Jurrens wrote: > I hate to say it, but I've had these for months starting at 4.6-stable > and continuing up to at least the latest 4.7-RRELEASE-p* . I have one > dual -current box that has exibited the same behaviour as well. > > The boxes work just fine with the xl0 driver. Lots of different > motherboards and processors (all PIII) and a number of different Intel > card revisions. I can't run my squid boxes on fxp cards _at all_ for > example, the fxp driver will take the box down with it. On my firewalls > it's locked up the interfaces numerous times. > > The only suggestion I can offer at the moment is to try various card > placements over your PCI slots. I've found stability using one of the > first two slots for my Adaptec controller (2940U[2]W, 29160[N]) and the > rest for the Intel nics. This happens both with or without POLLING > enabled. I've tried a number of combinations of POLLING enabled/disabled, > not compiled in and different HZ settings. Obviously no POLLING on my > SMP boxes. > > I know one or two others that have had problems with this too, but > haven't had the time or equipment at hand to work with any developers on > getting this fixed. I guess I got the equipment now (various PIII UP/SMP > boards from Gigabyte, Asus) and a little time if anyone wants to bite. > > My guess is that the POLLING commits broke something, but that's just a > guess. I don't have any dc cards here, and no one has ever complained > about either them or the rl cards timing out. There also seems to be > a definite correlation between the fxp problem and the ahc driver. > > Ok, the rest of the "me too's" should now chime in with a bit of time > and energy. There's also a PR open on this: kern/45568 . > > > > -- > Med vennlig hilsen/Sincerely, > > Shaun D. Jurrens > Drift og Sikkerhetskonsulent > IKT-Avdeling > Oslo Skoleetaten > > gpg key fingerprint: 007A B6BD 8B1B BAB9 C583 2D19 3A7F 4A3E F83E 84AE