netdev - Re: Bug: alx: Atheros AR8131/AR8151/AR8152/AR8161 Ethernet driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130805225752.14e843f7@nehalam.linuxnetplumber.net>
Date:	Mon, 5 Aug 2013 22:57:52 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Kinley Dorji <kinleyd@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Bug: alx: Atheros AR8131/AR8151/AR8152/AR8161 Ethernet driver

On Tue, 6 Aug 2013 11:31:39 +0600
Kinley Dorji <kinleyd@...il.com> wrote:

> Hi,
> 
> I'd like to report a bug that has been introduced since the mainlining
> of the NIC drivers originally in the package AUR/dkms-alx pertaining
> to the above mentioned network cards.
> 
> Kernels affected: 3.10.1 - 3.10.5
> All worked well for kernels <= 3.9.9
> 
> Environment in which it occurs:
> 
> kernel: >= 3.10
> conky: any version (gui/cli)
> NIC: Any one of the above family
> 
> conky variables that probe the NIC all return nothing or 0: eg:
> upspeed, upspeedgraph, downspeed, downspeedgraph
> 
> A small discussion on the issue:
> https://bbs.archlinux.org/viewtopic.php?id=166555
> 
> Network connectivity itself is not a problem - connection works and is stable
> 
> Conky isn't the problem because it works in kernels <= 3.9.9 with dkms-alx.
> 

What is conky using to read the variables. Perhaps looking at
CLI tools like:
  ip -s -d li show dev eth0
or
  ethtool -S eth0

would give some indication of which variables are not being incremented.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html