From owner-freebsd-net@FreeBSD.ORG Wed Nov 7 10:33:00 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 2901A16A419 for ; Wed, 7 Nov 2007 10:33:00 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.190]) by mx1.freebsd.org (Postfix) with ESMTP id E934213C491 for ; Wed, 7 Nov 2007 10:32:59 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1792236rvb for ; Wed, 07 Nov 2007 02:32:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=eQGU0D9GJHztN7rQbR345iiEblQgLSL97E9lQscrtwk=; b=LdhU1yFgudTMub+BW88XCq4F5XvdevmAsfnKuhmWjmReIWYd7x4GPNVwPwUCA3iArFMX3vTbkivrMjF3FKv23ctPGgyEradCdkPnj9t0RrI00E/lmXPBOsHGN5qic1LQbgX56X0+pcvbZAfSSIPYbftQAjImXisG+/zd/4rMdDE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=pnsSX4A1JackdjeAG48VabNgUjp49SrTVnz0pkToDWWXPplpJvie+ThrGHSajfi5sTBAyMhXs2mwtFBlR33zzr2hTKLcRWkWPL1J2tG7WJV1JAtyG9wvCYYk1KKee1MxDSeZREz7Np5V5OF+haC3iBkUTqP+g3XVlQnk/BZg1f8= Received: by 10.114.209.1 with SMTP id h1mr7333824wag.1194431569984; Wed, 07 Nov 2007 02:32:49 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m5sm18563829wag.2007.11.07.02.32.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Nov 2007 02:32:48 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id lA7AWfpl076071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Nov 2007 19:32:41 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id lA7AWeNk076070; Wed, 7 Nov 2007 19:32:40 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 7 Nov 2007 19:32:40 +0900 From: Pyun YongHyeon To: Garrett Cooper Message-ID: <20071107103240.GG70832@cdnetworks.co.kr> References: <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> <473173CB.40606@u.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <473173CB.40606@u.washington.edu> User-Agent: Mutt/1.4.2.1i 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 Reply-To: pyunyh@gmail.com 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 10:33:00 -0000 On Wed, Nov 07, 2007 at 12:14:03AM -0800, Garrett Cooper wrote: > 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 . If you use forced speed/duplex settings, both FreeBSD and Windows *should* use the same speed/duplex. Failing that will result in speed/duplex mismatches which in turn creates lots of unexpected results(poor performance, packet loss, watchdog timeout etc). Requiring forced speed/duplex normally means a bug in PHY driver. Since I still don't know what PHY model/revision was attached to msk(4) I'm not sure about 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? > Sorry, I don't know what e1000phy patch you refers. "dmesg | grep ^e1000phy" will show you PHY related information. > 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. > To narrow down the issue, disable checksum offload/TSO in msk(4) and see Mac box still receives bad packets generated from msk(4). To disable checksum offload/TSO, use the following command. #ifconfig msk0 -tso -txcsum > Thanks for the advice, > -Garrett -- Regards, Pyun YongHyeon