From owner-freebsd-net@FreeBSD.ORG Wed Sep 11 00:15:23 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 943E0C79 for ; Wed, 11 Sep 2013 00:15:23 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6BC35289B for ; Wed, 11 Sep 2013 00:15:23 +0000 (UTC) Received: by mail-pb0-f48.google.com with SMTP id ma3so8237583pbc.21 for ; Tue, 10 Sep 2013 17:15:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=PBDEFNrtROrGaNsjNtzi/2ronA1zEZ/BEfhK/0Y53IQ=; b=rPuhILDjSVKWqWmkJMmFZ0/1EpnxTFAfe8IwGhCLCH70AV6z8Ebz+A29aFNEvfF53z QSxv9KzZvfU4oZD1XbQDSWeW9w6BME5eiRwIU22Tb8n/d+ZwezThMsk4OrvdedF/0MKa LZ1pTbEcv3ZI2qQ/LAHK81FYLBfnw/xUTBmUsNQnXYvZA74b/B6DMQ/X2MKeZQadAkH9 +6wLnr+slwx4h7UmaPwDJrhvCMzXch+DHmDj+LasE9I+MbvObzspuVcsX5Fr2tjeSnq4 lo94W63ZyfvymmSopKm4DWVSNeA1D1xO4RXW2JkGydfvyerAYanW1ryafTKuj0+Cg8UI rcVg== X-Received: by 10.66.150.69 with SMTP id ug5mr468163pab.55.1378858522997; Tue, 10 Sep 2013 17:15:22 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id qf7sm27660758pac.14.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 10 Sep 2013 17:15:22 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 11 Sep 2013 09:15:15 +0900 From: Yonghyeon PYUN Date: Wed, 11 Sep 2013 09:15:15 +0900 To: Guido Falsi Subject: Re: re0 not working at boot on -CURRENT Message-ID: <20130911001515.GA3145@michelle.cdnetworks.com> References: <51DC726D.6040601@madpilot.net> <20130710070431.GE2753@michelle.cdnetworks.com> <51DD9E15.7070609@madpilot.net> <20130906061521.GB3070@michelle.cdnetworks.com> <522A3E50.8080801@madpilot.net> <20130910021502.GA2962@michelle.cdnetworks.com> <522FABE5.4090805@madpilot.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <522FABE5.4090805@madpilot.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 11 Sep 2013 00:15:23 -0000 On Wed, Sep 11, 2013 at 01:31:49AM +0200, Guido Falsi wrote: > On 09/10/13 04:15, Yonghyeon PYUN wrote: > >On Fri, Sep 06, 2013 at 10:42:56PM +0200, Guido Falsi wrote: > >>On 09/06/13 08:15, Yonghyeon PYUN wrote: > >>>On Wed, Jul 10, 2013 at 07:47:01PM +0200, Guido Falsi wrote: > >>>>On 07/10/13 09:04, Yonghyeon PYUN wrote: > >>>>>On Tue, Jul 09, 2013 at 10:28:29PM +0200, Guido Falsi wrote: > >>>>>>Hi, > >>>>>> > >>>>>>I have a PC with an integrate re ethernet interface, pciconf > >>>>>>identifies > >>>>>>it like this: > >>>>>> > >>>>>>re0@pci0:3:0:0: class=0x020000 card=0x11c01734 chip=0x816810ec > >>>>>>rev=0x07 > >>>>>>hdr=0x00 > >>>>>> > >>>>>>I'm running FreeBSD current r252261. > >>>>>> > >>>>>>As stated in the subject after boot the interface does not work > >>>>>>correctly. > >>>>>> > >>>>>>Using tcpdump on another host I noticed that packets (ICMP echo > >>>>>>requests > >>>>>>for example) do get sent, and replies generated by the other host, but > >>>>>>the kernel does not seem to see them. Except that every now and then > >>>>>>some packet does get to the system. > >>>>>> > >>>>>>I'm seeing packet 7, 27, 47, 66, 86, 106, 125, 144, 164, 183 and so on > >>>>>>from a ping which has been running for some time. Just about one every > >>>>>>twenty. Some pattern is showing up. > >>>>>> > >>>>>>this is the output of ifconfig re0 after boot: > >>>>>> > >>>>>>re0: flags=8843 metric 0 mtu > >>>>>>1500 > >>>>>> > >>>>>>options=8209b > >>>>>> ether 00:19:99:f8:d3:0b > >>>>>> inet 172.24.42.13 netmask 0xffffff00 broadcast 172.24.42.255 > >>>>>> inet6 fe80::219:99ff:fef8:d30b%re0 prefixlen 64 scopeid 0x2 > >>>>>> nd6 options=29 > >>>>>> media: Ethernet autoselect (100baseTX ) > >>>>>> status: active > >>>>>> > >>>>>>If I just touch any interface flag with ifconfig, anyone, tso, -txcsum > >>>>>>-rxcsum, it starts working flawlessly. It keeps working also if I > >>>>>>perform the opposite operation with ifconfig afterwards, so it is not > >>>>>>the flag itself fixing it. > >>>>>> > >>>>>>This is an ifconfig after performing this exercise(it's the same, > >>>>>>since > >>>>>>I disabled txcsum and reactivated it in this instance): > >>>>>> > >>>>>>re0: flags=8843 metric 0 mtu > >>>>>>1500 > >>>>>> > >>>>>>options=8209b > >>>>>> ether 00:19:99:f8:d3:0b > >>>>>> inet 172.24.42.13 netmask 0xffffff00 broadcast 172.24.42.255 > >>>>>> inet6 fe80::219:99ff:fef8:d30b%re0 prefixlen 64 scopeid 0x2 > >>>>>> nd6 options=29 > >>>>>> media: Ethernet autoselect (100baseTX ) > >>>>>> status: active > >>>>>> > >>>>>>I don't know much about FreeBSD network drivers so i can't make > >>>>>>theories > >>>>>>about this. I hope someone has an idea what the problem could be. > >>>>>> > >>>>>>I'm available for any further information needed, test, experiment and > >>>>>>so on. > >>>>> > >>>>>Could you show me dmesg output(re(4) and rgephy(4) only)? > >>>> > >>>>re0: port > >>>>0xd000-0xd0ff mem 0xf2104000-0xf2104fff,0xf2100000-0xf2103fff irq 17 at > >>>>device 0.0 on pci3 > >>>>re0: Using 1 MSI-X message > >>>>re0: turning off MSI enable bit. > >>>>re0: Chip rev. 0x2c800000 > >>>>re0: MAC rev. 0x00000000 > >>>>re0: Ethernet address: 00:19:99:f8:d3:0b > >>>>miibus0: on re0 > >>>>rgephy0: PHY 1 on > >>>>miibus0 > >>>>rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, > >>>>100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, > >>>>1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, > >>>>1000baseT-FDX-flow-master, auto, auto-flow > >>>> > >>>>Also, I'm loading this as a module, but, for as much as I know, this > >>>>should not make any difference. > >>>> > >>>> > >>>>>Did it ever work or you see the issue only on CURRENT? > >>>> > >>>>Never worked on this machine (I own it since the last days of February). > >>>> > >>>>I only installed current on it. If needed I can find time to test a > >>>>recent 9.x snapshot on it. > >>>> > >>>>I worked around the problem till now using an USB ethernet adapter, > >>>>always wanted to report this problem, but I've been lazy :) > >>>> > >>> > >>>Would you try attached patch and let me know whether it makes any > >>>difference? > >>> > >> > >>Hi! > >> > >>Thanks for looking into this and sorry for the delay in reporting back. > >> > >>Unluckily the patch does not solve nor mitigates the problem. Symptoms > >>are very similar. > > > >[...] > > > >>Only real difference is the re_eri_read timeout. It did not output that > >>error message before. > > > >Oops, sorry. It seems there is logic error in the diff. > >Try attached one again. > > > > Hi, > > This patch shows the same behavior as the unpatched kernel: [...] > I'd like to note that if I perform a tcpdump from the other machine > (which is also the dns server) I do see the packets getting out as usual > from this machine, and replies being sent. So the problem seems to be to > receive packets, while sending them works fine. Hmm, I thought the diff may reset internal RX filter but it seems it has no effect. If I find a clue I'll let you know. BTW, I guess the diff have showed IC revision of MAC. Could you show me the output of driver? Thanks for testing!