From: Stephen Hemminger <stephen@networkplumber.org>
To: Kevin <kevin.padoa@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [Bug 98781] New: WWAN: TX bytes counter shows very huge impossible value
Date: Sat, 13 Jun 2015 08:33:39 -0700 [thread overview]
Message-ID: <20150613083339.71d38d3d@urahara> (raw)
In-Reply-To: <loom.20150613T021828-603@post.gmane.org>
On Sat, 13 Jun 2015 00:28:58 +0000 (UTC)
Kevin <kevin.padoa@gmail.com> wrote:
> Stephen Hemminger <stephen <at> networkplumber.org> writes:
>
> >
> >
> > Begin forwarded message:
> >
> > Date: Sat, 23 May 2015 16:54:50 +0000
> > From: "bugzilla-daemon <at> bugzilla.kernel.org" <bugzilla-daemon <at>
> bugzilla.kernel.org>
> > To: "shemminger <at> linux-foundation.org" <shemminger <at>
> linux-foundation.org>
> > Subject: [Bug 98781] New: WWAN: TX bytes counter shows very huge
> impossible value
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=98781
> >
> > Bug ID: 98781
> > Summary: WWAN: TX bytes counter shows very huge impossible
> > value
> > Product: Networking
> > Version: 2.5
> > Kernel Version: 4.0.x
> > Hardware: Intel
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: Other
> > Assignee: shemminger <at> linux-foundation.org
> > Reporter: mm <at> superbash.de
> > Regression: No
> >
> > Since version 4.0.x the TX bytes counter of the WWAN module shows a weird
> > value.
> >
> > Example:
> >
> > $ > ifconfig wwan
> >
> > wwan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> > inet xxx.xxx.xxx.xxx netmask 255.255.255.252 broadcast
> > xxx.xxx.xxx.xxx
> > inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20<link>
> > ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
> > RX packets 19036 bytes 19190321 (18.3 MiB)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 15874 bytes 43228847574631 (39.3 TiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
> > 39.3 TiB - wow, absolutely not true
> >
> > The WWAN is used as bridge to my internet provider (LTE usb stick)
> >
> > I use the counter to control the traffic. It's only the TX counter, the RX
> > works ok.
> >
> I have exactly the same issue, exhibited when upgrading (n-1) kernel on
> Ubuntu Vivid 15.04 from 3.17.x:
>
> Linux uranis 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015
> x86_64 x86_64 x86_64 GNU/Linux
>
> wwan0 Link encap:Ethernet HWaddr 26:03:a9:e3:88:2e
> inet addr:41.150.225.132 Bcast:41.150.225.135 Mask:255.255.255.248
> inet6 addr: fe80::2403:a9ff:fee3:882e/64 Scope:Link
> UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:3366 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3497 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1459963 (1.4 MB) TX bytes:15019500985395 (15.0 TB)
>
> Kernel internal or module (driver) bug, shows up everywhere including
> 'system monitor'. This problem has come up a few years back and was solved,
> but seems to be back again...
>
> Any ideas on fix ?
What driver is this device?
next prev parent reply other threads:[~2015-06-13 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 15:38 Fw: [Bug 98781] New: WWAN: TX bytes counter shows very huge impossible value Stephen Hemminger
2015-06-13 0:28 ` Kevin
2015-06-13 15:33 ` Stephen Hemminger [this message]
2015-06-16 9:04 ` David Laight
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=20150613083339.71d38d3d@urahara \
--to=stephen@networkplumber.org \
--cc=kevin.padoa@gmail.com \
--cc=netdev@vger.kernel.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