From owner-freebsd-questions Thu Aug 9 21:27:11 2001 Delivered-To: freebsd-questions@freebsd.org Received: from intergate.sdccd.cc.ca.us (intergate.sdccd.cc.ca.us [209.129.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 9DDEA37B401; Thu, 9 Aug 2001 21:27:06 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ntxdistrict.sdccd.cc.ca.us (ntxdistrict.sdccd.cc.ca.us [10.1.100.1]) by intergate.sdccd.cc.ca.us (8.8.7/8.8.7) with ESMTP id UAA25157; Thu, 9 Aug 2001 20:34:28 -0700 (PDT) Received: by NTXDISTRICT with Internet Mail Service (5.5.2652.78) id ; Thu, 9 Aug 2001 21:29:18 -0700 Message-ID: From: Erin Fortenberry To: "'Justin Sheehy '" , "'freebsd-stable@FreeBSD.ORG '" , "'freebsd-questions@FreeBSD.ORG '" Subject: RE: fxp SCB timeout problems, anyone have a solution? Date: Thu, 9 Aug 2001 21:29:12 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I am having a major problem with a FreeBSD-4.3 machine. As did I. I guess I should have looked at some of the earlier postings before I opend my mouth. :-) > Is there any known fix for this? All of the messages that I see on > the mailing list archives that have "solutions" involve switching out > the hardware for a different NIC. As that would involve having the > machine shipped back home and then out again, this is very > undesirable. I can usually keep the machine on the net for at least a > few minutes at a time before it hangs, so if anyone has any idea how I > could possibly fix this remotely I would be greatly appreciative. There is currently no fix for this. I went through the same thing about 2 months ago with intel's newest i815 chipset MB. What I got from David Greenman is although the 82562 is seen as an fxp0 it was never tested. I had looked into this problem quiet a bit and forget exactly why it does not work, but it does not work. You might try upgrading to the newest stable. Hope this helps. Erin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message