From owner-freebsd-hackers Wed Jul 7 23: 2:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 1D4F214DFC for ; Wed, 7 Jul 1999 23:02:39 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id XAA25090; Wed, 7 Jul 1999 23:01:26 -0700 (PDT) Message-Id: <199907080601.XAA25090@implode.root.com> To: Jay Kuri Cc: hackers@FreeBSD.ORG Subject: Re: Problem with fxp driver and 82559 cards In-reply-to: Your message of "Wed, 07 Jul 1999 23:03:32 EDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 07 Jul 1999 23:01:26 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >Large data transfers seem to cause the lockup. I know at least 1 netbsd >> >person has reported similar problems with these new cards, (kern/7216). >> > >> >Has anyone seen problems like these? Any ideas? >> >> Hmmm...I've been using them in some machines here and haven't seen any >> problems. Strange. Do all of your systems have similar motherboards and CPU? > > The only thing that I can identify as a common factor, is that the >PCI slots are on a riser card. One type is an NLX-form factor >motherboard. The other is an industrial system with a Single Board >Computer (SBC) and a passive backplain. Aside from the riser card, these >machines are completely different. (IDE vs. SCSI, no other PCI devices, >SCSI pci device, pentium vs pentium-II... onboard video/ethernet(in >addition to the intel cards) vs nothing onboard...) > > However, we have at least one industrial-type system (with a >different board/config) that works fine with these cards, though we didn't >do the install with one. I'll try that tomorrow and report my findings. > >I doubt this is the case, but is the fxp driver different on the install >floppy than on the post-install kernel / kernel-source? Same driver on floppy and installed kernel. >Any suggestions as to what I should look into? It sounds like a motherboard chipset problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message