From owner-freebsd-alpha Fri Jul 14 14:16:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 16FE937C55F for ; Fri, 14 Jul 2000 14:16:39 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA05782; Fri, 14 Jul 2000 14:25:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007142125.OAA05782@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: dg@root.com Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: fxp0 hangs on a PC164 using STABLE In-reply-to: Your message of "Fri, 14 Jul 2000 10:07:36 PDT." <200007141707.KAA16976@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 14 Jul 2000 14:25:05 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >fxp is not supported on the Alpha, and known to be unreliable there. > >Contact the maintainer or use a different card. FWIW, this actually > >sounds like an issue that's been seen on x86 as well. > > It does? I've never heard of a bug report like this for x86 and in fact I'm > not aware of any bugs in the driver for x86. It's been described many times, actually. It sounds a lot like a bad interaction between either the card or the driver and the hub/switch at the other end, however it's shown up on a reasonably regular basis. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message