From owner-freebsd-hardware@FreeBSD.ORG Tue Jun 3 08:21: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 CB98537B401; Tue, 3 Jun 2003 08:21:33 -0700 (PDT) Received: from vmx2.skoleetaten.oslo.no (vmx2.skoleetaten.oslo.no [193.156.192.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F6C943FAF; Tue, 3 Jun 2003 08:21:32 -0700 (PDT) (envelope-from shamz@nevada.skoleetaten.oslo.no) Received: from smtp.skoleetaten.oslo.no (localhost [127.0.0.1]) by vmx2.skoleetaten.oslo.no (Clean Mail System) with SMTP id BB83079390; Tue, 3 Jun 2003 17:21:30 +0200 (CEST) Received: from nevada.skoleetaten.oslo.no (nevada.skoleetaten.oslo.no [193.156.192.131]) by smtp.skoleetaten.oslo.no (Clean Mail System) with ESMTP id 93B46792DD; Tue, 3 Jun 2003 17:21:30 +0200 (CEST) Received: from nevada.skoleetaten.oslo.no (localhost [127.0.0.1]) h53FLUOU036784; Tue, 3 Jun 2003 17:21:30 +0200 (CEST) (envelope-from shamz@nevada.skoleetaten.oslo.no) Received: (from shamz@localhost)h53FLNIl036783; Tue, 3 Jun 2003 17:21:23 +0200 (CEST) Date: Tue, 3 Jun 2003 17:21:23 +0200 From: Shaun Jurrens To: freebsd-net@freebsd.org, freebsd-hardware@freebsd.org Message-ID: <20030603152123.GM98443@nevada.skoleetaten.oslo.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9ToWwKEyhugL+MAz" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE Subject: 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: Tue, 03 Jun 2003 15:21:34 -0000 --9ToWwKEyhugL+MAz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=20 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=20 interfaces numerous times. The only suggestion I can offer at the moment is to try various card=20 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=20 compiled in and different HZ settings. Obviously no POLLING on my SMP=20 boxes. I know one or two others that have had problems with this too, but haven't= =20 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=20 guess. I don't have any dc cards here, and no one has ever complained=20 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 . --=20 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 --9ToWwKEyhugL+MAz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+3LzzOn9KPvg+hK4RAv8hAKCHiW6Kc4bYNtXAe1oZ+wZxKnjXIgCeJv0m 68xuOi/dWy9FYXxoCALnJ/U= =Wr+2 -----END PGP SIGNATURE----- --9ToWwKEyhugL+MAz--