From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem Date: Fri, 14 Mar 2014 12:16:55 -0500 Message-ID: <1394817415.5829.6.camel@dcbw.local> References: <1394746907.15946.8.camel@dcbw.local> <20140313220812.GW3200@reaktio.net> <20140314075548.GX3200@reaktio.net> <87wqfxnppc.fsf@nemi.mork.no> <20140314084159.GA3200@reaktio.net> <87siqlnol8.fsf@nemi.mork.no> <20140314090525.GB3200@reaktio.net> <87ob19nndo.fsf@nemi.mork.no> <20140314125934.GC3200@reaktio.net> <87vbvgnbv3.fsf@nemi.mork.no> <20140314142559.GD3200@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: =?ISO-8859-1?Q?Bj=F8rn?= Mork , netdev@vger.kernel.org, linux-usb@vger.kernel.org, Enrico Mioso , Oliver Neukum To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Return-path: Received: from mx1.redhat.com ([209.132.183.28]:61669 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756180AbaCNRPP (ORCPT ); Fri, 14 Mar 2014 13:15:15 -0400 In-Reply-To: <20140314142559.GD3200@reaktio.net> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, 2014-03-14 at 16:25 +0200, Pasi K=C3=A4rkk=C3=A4inen wrote: > On Fri, Mar 14, 2014 at 02:33:36PM +0100, Bj=C3=B8rn Mork wrote: > > Pasi K=C3=A4rkk=C3=A4inen writes: > > > On Fri, Mar 14, 2014 at 10:24:51AM +0100, Bj=C3=B8rn Mork wrote: > > >> Pasi K=C3=A4rkk=C3=A4inen writes: > > >>=20 > > >> > # ifconfig wwp0s26u1u5i1 > > >> > wwp0s26u1u5i1: flags=3D4163 m= tu 1500 > > >> > inet 10.8.219.204 netmask 255.255.255.248 broadcast = 10.8.219.207 > > >> > inet6 fe80::e5b:8fff:fe27:9a64 prefixlen 64 scopeid = 0x20 > > >> > ether 0c:5b:8f:27:9a:64 txqueuelen 1000 (Ethernet) > > >> > RX packets 0 bytes 0 (0.0 B) > > >> > RX errors 1493 dropped 0 overruns 0 frame 0 > > >> > > > >> > Note the RX errors.. ?=20 > > >>=20 > > >>=20 > > >> Yes, that is not expected and is quite possibly hiding the expla= nation. > > >>=20 > > > > > > Ok, good to know. > > > > > >> Could you do a usbmon dump to try to capture the contents of the= USB > > >> buffers we drop here? See > > >> https://www.kernel.org/doc/Documentation/usb/usbmon.txt > > >>=20 > > >> Note that the text interface may truncate the buffers too early = for the > > >> result to be useful. wireshark/thsark will for example allow yo= u to > > >> capture the whole buffer (when snooping on the "usbmonX" interfa= ce - not > > >> the netdev!) > > >>=20 > > > > > > I'll try that..=20 > > > > > >> We also have a few debug messages in the driver for different ty= pes of > > >> errors we drop. Turning on those might explain something (assum= ing you > > >> have DYNAMIC_DEBUG enabled): > > >>=20 > > >> ethtool -s wwp0s26u1u5i1 msglvl rx_err on > > >>=20 > > >> Note that these will be logged at "debug" level, so you need to = turn on > > >> logging/showing such messages as well. > > >>=20 > > > > > > # uname -a > > > Linux localhost.localdomain 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar= 7 17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > > > > > > # grep -i DYNAMIC_DEBUG /boot/config-3.13.6-200.fc20.x86_64 > > > CONFIG_DYNAMIC_DEBUG=3Dy > > > > > > # echo 8 > /proc/sys/kernel/printk > > > # cat /proc/sys/kernel/printk > > > 8 4 1 7 > > > > > > # ethtool -s wwp0s26u1u5i1 msglvl rx_err on > > > > > > Is that enough? > >=20 > > I believe so, but I don't feel too steady on all the dynamic-ness h= ere. > >=20 > > > I don't see any errors logged in "dmesg" output, > > > but the RX errors counters do keep increasing in ifconfig output.= =2E=20 > >=20 > > OK, let's see if we can figure it out based on the usbmon data. > >=20 >=20 > http://pasik.reaktio.net/huawei-e3276-usbmon3.pcapng >=20 > (I did move the dongle to a different usb bus nr 3 to make it the onl= y device on that bus before capturing..)=20 >=20 > So what I did: >=20 > - Start wireshark capture on USB bus nr 3. > - Plug in the Huawei E3276 dongle. > - Wait for usb_modeswitch to happen. > - Use minicom to talk to /dev/cdc-wdm0 and send AT commands to connec= t to Internet: > - ATQ0 V1 E1 S0=3D0 > - AT^NDISDUP=3D1,1,"internet" Are you sure the device has actually registered with the network at the point you do the NDISDUP? At this point what do you get for "AT+CREG?" and "AT+CFUN?" ? Dan > - After the dongle has connected query for DHCP status: > - AT^DHCP? >=20 > - Launch dhcp client (dhclient) on wwp0s20u1i1 interface. > - Wait for a while and see RX error counters increasing on ifconfig o= utput. > - Cancel (ctrl+c) the dhclient. > - Stop wireshark capture.=20 >=20 >=20 > Does that capture file show anything interesting to you?=20 >=20 > >=20 > >=20 > > Bj=C3=B8rn >=20 >=20 > Thanks, >=20 > -- Pasi >=20 > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html