From owner-freebsd-net@FreeBSD.ORG Wed Nov 7 08:15:19 2007 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A35016A46B for ; Wed, 7 Nov 2007 08:15:19 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.freebsd.org (Postfix) with ESMTP id E18DE13C491 for ; Wed, 7 Nov 2007 08:15:18 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.7] (may be forged)) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id lA78F19w003538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Nov 2007 00:15:01 -0800 X-Auth-Received: from [127.0.0.1] (node49.244.100.208.1dial.com [208.100.244.49] (may be forged)) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id lA78EbVK002184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 7 Nov 2007 00:14:58 -0800 Message-ID: <473173CB.40606@u.washington.edu> Date: Wed, 07 Nov 2007 00:14:03 -0800 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: pyunyh@gmail.com References: <20071019182349.J97691@odysseus.silby.com> <47194EA1.8000402@u.washington.edu> <20071019212012.C97691@odysseus.silby.com> <47202922.3070700@u.washington.edu> <47209570.20609@tomjudge.com> <4723330A.7070803@u.washington.edu> <4728B256.5080005@u.washington.edu> <9CFC3779-3A4C-4ADD-8F2C-982887CB3039@u.washington.edu> <472FA362.6040608@u.washington.edu> <20071107004149.GB70832@cdnetworks.co.kr> In-Reply-To: <20071107004149.GB70832@cdnetworks.co.kr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.3.310218, Antispam-Engine: 2.5.2.313940, Antispam-Data: 2007.11.6.235226 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='ECARD_WORD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_419_CONTACT_ADDY_B 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: net@freebsd.org Subject: Re: Marvell chipsets on 8-CURRENT and XP x64 won't talk with one another X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2007 08:15:19 -0000 Pyun YongHyeon wrote: > On Mon, Nov 05, 2007 at 03:12:34PM -0800, Garrett Cooper wrote: > > Garrett Cooper wrote: > > >On Oct 31, 2007, at 9:50 AM, Garrett Cooper wrote: > > >>I'm running tcpdump on my Mac and I noted a lot of 'bad checksums' > > >>(0x081c was the official error in all cases), then consulted the msk > > >>driver. It appears that there's a bug with Yukon II chipsets with the > > >>hardware checksumming and I wonder whether or not the chipset that I > > >>have is affected by this issue as well. > > >>I'll provide my chipset/model info in my next reply (can't access it > > >>from this PC). > > >>-Garrett > > > > > >Got a wee bit busy there. > > > > > >Anyhow, here's the chipset info (snippet) reported from dmesg: > > > > > >[gcooper@shiina: ~]$ ssh -C optimus "dmesg | grep msk" > > >Password: > > >mskc0: port 0xd800-0xd8ff mem > > >0xfe9fc000-0xfe9fffff irq 17 at device 0.0 on pci2 > > >msk0: > > >on mskc0 > > >msk0: Ethernet address: 00:1b:fc:45:9b:5c > > >miibus0: on msk0 > > > > > >-Garrett > > > > The issue indeed is with the msk(4) driver in FreeBSD. > > I just plugged in an em(4) compatible card, powered it up and now my > > server works like a champ with the XP machine. > > I'm confused. As I said in previous mail please check network cables > such that down-shifting wouldn't take part in this issue. If that > does not fix the issue, force speed/duplex on both ends. > Which I made sure of. Enforcing duplexing from the FreeBSD (and I assume Windows?) end worked successfully. So, unless something's doing a really shoddy job of detecting the media type for a number of different cables, I don't think that . > > As a reference the MB's affected by this are mostly the ASUS MB's, i.e. > > P5B and P5K series ones. MSI MB's may be affected by this issue as well > > because I think they come with msk(4) compatible chipsets onboard.. > > Bad checksum seems to be different issue to me. Capture traffic on > Mac with tcpdump and give me a URL for the pcap file. > Btw, it would be even better if you can show me the PHY driver > (e1000phy(4)) information in dmesg output. Will do once I get my gigabit switch back from Netgear (bloody port routing controller card on the switch died after transferring a few GB of data, sadly enough :(...). I assume the e1000phy patch is already in 8-CURRENT? What exactly does output from e1000phy(4) output look like though? My thought about this is that all of the TCP packets received from the FreeBSD machine were considered bad, so the XP machine gave up after so many tries and bad checksum reports. I could be wrong though. Thanks for the advice, -Garrett