From owner-freebsd-bugs@FreeBSD.ORG Fri Dec 3 07:35:05 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F14516A4CF for ; Fri, 3 Dec 2004 07:35:05 +0000 (GMT) Received: from gate1.iwakuni.usmc.mil (gate1.iwz.usmc.mil [192.156.63.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 192EC43D5A for ; Fri, 3 Dec 2004 07:35:04 +0000 (GMT) (envelope-from shadlej@iwakuni.usmc.mil) Message-ID: <7F09B7AD24CE5E42AD429BFEC8757D1701C8A8A3@iwakuni.usmc.mil> From: Shadle CTR James W To: "'freebsd-bugs@freebsd.org'" Date: Fri, 3 Dec 2004 16:37:09 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Subject: kern/71229: Device sk0 hands up when data transfering X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 07:35:05 -0000 Has there been any follow-up on this? I have the same problem. I am using an Asus motherboard. Kites rise highest against the wind - not with it. - Winston Churchill ======================================= Jim Shadle DSN 253-6307 shadlej@iwakuni.usmc.mil ======================================= ==================================================================== The following reply was made to PR kern/71229; it has been noted by GNATS. From: Jeremy Chadwick To: freebsd-gnats-submit at FreeBSD.org, hunreal at gmail.com Cc: Subject: Re: kern/71229: Device sk0 hands up when data transfering Date: Fri, 5 Nov 2004 02:50:09 -0800 I can confirm this exact behaviour on other vendors' motherboards, particularly Gigabyte. The chipset in question: === skc0: port 0xa000-0xa0ff mem 0xf9044000-0xf9047fff irq 20 at device 9.0 on pci1 skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter sk0: on skc0 sk0: Ethernet address: 00:0f:ea:31:f0:ee miibus1: on sk0 e1000phy0: on miibus1 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto skc0 at pci1:9:0: class=0x020000 card=0xe0001458 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' class = network subclass = ethernet === The errors in question when doing large transfers: === Nov 4 23:51:57 icarus kernel: sk0: discard frame w/o leading ethernet header (len 0 pkt len 0) Nov 4 23:51:57 icarus kernel: sk0: discard oversize frame (ether type 0 flags 3 len 9022 > max 1514) Nov 4 23:51:57 icarus kernel: sk0: discard oversize frame (ether type 0 flags 3 len 1556 > max 1514) Nov 4 23:51:57 icarus kernel: sk0: discard frame w/o leading ethernet header (len 0 pkt len 0) Nov 4 23:51:57 icarus kernel: sk0: discard oversize frame (ether type 0 flags 3 len 9022 > max 1514) Nov 4 23:51:57 icarus kernel: sk0: discard oversize frame (ether type 0 flags 3 len 7524 > max 1514) Nov 4 23:51:57 icarus kernel: sk0: discard oversize frame (ether type e889 flags 3 len 9022 > max 1514) Nov 4 23:51:57 icarus kernel: sk0: discard oversize frame (ether type eb3a flags 3 len 3840 > max 1514) ...and so on... === Operating system is 5.3-RELEASE (as of Nov 5 2004 -- today). I have managed to circumvent this problem by forcing the sk0 interface to 100baseTX + full-duplex instead of autodetect (which normally picks up 1000baseTX + full-duplex, since it's connected to a GbE switch). This is definitely looking to be some sort-of driver problem, and IMHO has very little to do with motherboard BIOS revisions as implied in the aforementioned PR (kern/69879). kern/69789, IMHO, should have never been closed. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. |