From: Enrico Mioso <mrkiko.rs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Bjørn Mork" <bjorn-yOkvZcmFvRU@public.gmane.org>
Cc: "Pasi Kärkkäinen" <pasik-X3B1VOXEql0@public.gmane.org>,
"Dan Williams" <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Oliver Neukum" <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem
Date: Fri, 14 Mar 2014 10:37:34 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.03.1403141036590.6461@gmail.com> (raw)
In-Reply-To: <87ob19nndo.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1998 bytes --]
Yes, this is
the
solution, dfefinitively.
On Fri, 14 Mar 2014, Bjørn Mork wrote:
==Date: Fri, 14 Mar 2014 10:24:51
==From: Bjørn Mork <bjorn-yOkvZcmFvRU@public.gmane.org>
==To: Pasi Kärkkäinen <pasik-X3B1VOXEql0@public.gmane.org>
==Cc: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
== linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Enrico Mioso <mrkiko.rs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
== Oliver Neukum <oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
==Subject: Re: [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem
==
==Pasi Kärkkäinen <pasik-X3B1VOXEql0@public.gmane.org> writes:
==
==> # ifconfig wwp0s26u1u5i1
==> wwp0s26u1u5i1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 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<link>
==> 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.. ?
==
==
==Yes, that is not expected and is quite possibly hiding the explanation.
==
==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
==
==Note that the text interface may truncate the buffers too early for the
==result to be useful. wireshark/thsark will for example allow you to
==capture the whole buffer (when snooping on the "usbmonX" interface - not
==the netdev!)
==
==We also have a few debug messages in the driver for different types of
==errors we drop. Turning on those might explain something (assuming you
==have DYNAMIC_DEBUG enabled):
==
== ethtool -s wwp0s26u1u5i1 msglvl rx_err on
==
==Note that these will be logged at "debug" level, so you need to turn on
==logging/showing such messages as well.
==
==
==
==Bjørn
==
next prev parent reply other threads:[~2014-03-14 9:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 8:50 [PATCH net-next v6 0/3] The huawei_cdc_ncm driver Bjørn Mork
2013-11-04 8:50 ` [PATCH net-next v6 1/3] net: cdc_ncm: Export cdc_ncm_{tx,rx}_fixup functions for re-use Bjørn Mork
2013-11-04 8:50 ` [PATCH net-next v6 2/3] net: huawei_cdc_ncm: Introduce the huawei_cdc_ncm driver Bjørn Mork
2013-11-04 8:50 ` [PATCH net-next v6 3/3] net: cdc_ncm: remove non-standard NCM device IDs Bjørn Mork
2013-11-05 20:22 ` [PATCH net-next v6 0/3] The huawei_cdc_ncm driver David Miller
2014-03-13 20:25 ` [PATCH net-next v6 0/3] The huawei_cdc_ncm driver / E3276 problem Pasi Kärkkäinen
2014-03-13 21:41 ` Dan Williams
2014-03-13 22:08 ` Pasi Kärkkäinen
2014-03-14 7:55 ` Pasi Kärkkäinen
[not found] ` <20140314075548.GX3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-14 8:34 ` Bjørn Mork
2014-03-14 8:41 ` Pasi Kärkkäinen
2014-03-14 8:58 ` Bjørn Mork
2014-03-14 9:05 ` Pasi Kärkkäinen
2014-03-14 9:24 ` Enrico Mioso
2014-03-14 9:24 ` Bjørn Mork
[not found] ` <87ob19nndo.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2014-03-14 9:37 ` Enrico Mioso [this message]
2014-03-14 12:59 ` Pasi Kärkkäinen
2014-03-14 13:33 ` Bjørn Mork
2014-03-14 14:25 ` Pasi Kärkkäinen
2014-03-14 17:16 ` Dan Williams
[not found] ` <1394817415.5829.6.camel-ZWpNTBV2bRGs1BDpvl8NfQ@public.gmane.org>
2014-03-14 17:33 ` Pasi Kärkkäinen
[not found] ` <20140314142559.GD3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-17 11:31 ` Bjørn Mork
2014-03-17 11:59 ` Pasi Kärkkäinen
[not found] ` <20140317115919.GK3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-17 12:45 ` Pasi Kärkkäinen
2014-03-17 13:15 ` Bjørn Mork
2014-03-17 13:17 ` Pasi Kärkkäinen
[not found] ` <20140317131731.GM3200-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2014-03-17 14:23 ` Bjørn Mork
[not found] ` <87txawlx9h.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2014-03-17 14:46 ` Enrico Mioso
2014-03-17 15:05 ` Pasi Kärkkäinen
2014-03-17 15:07 ` Bjørn Mork
[not found] ` <87k3btm57a.fsf-lbf33ChDnrE/G1V5fR+Y7Q@public.gmane.org>
2014-03-17 12:56 ` Bjørn Mork
2014-03-17 13:10 ` Bjørn Mork
[not found] ` <385896107.16855.1394783754007.JavaMail.mobile-sync@vcpd12>
2014-03-14 7:58 ` Mrkiko Rs
2014-03-14 8:01 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.03.1403141036590.6461@gmail.com \
--to=mrkiko.rs-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bjorn-yOkvZcmFvRU@public.gmane.org \
--cc=dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org \
--cc=pasik-X3B1VOXEql0@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).