linux-kernel - Is via-velocity broken in 2.6.34?

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-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinK4VywsJ86jaC8wQjbXjzvP-z44JD3XbZbMM2a@mail.gmail.com>
Date:	Tue, 7 Sep 2010 15:41:25 -0700
From:	Matt Causey <matt.causey@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Is via-velocity broken in 2.6.34?

Hello,

I'm running a vanilla 2.6.34 on a fleet of thin clients.  We just got
some devices that have a via VT61xx gigabit network card, and we
discovered that the networking does not start on this new hardware.
I've searched the archives here but have not seen similar reports -
though this network adapter might not be in wide circulation
yet....not sure.

The network driver loads just fine, and I'm able to create eth0.  I
can run a dhcp client on the interface, and my dhcp server recieves
the DHCPDISCOVER messages, immediately sending DHCPOFFERs, however the
dhcp client does not acknowledge the offers.  When running ifconfig
while this is happening, the RX packets field increments slowly, while
the TX packets field does not do anything.  It stays at 0.  I would
expect the DHCPDISCOVER packets (since they are transmitting to my
server) to be incrimenting the TX packets field.

When I assign an IPV4 address to the interface, I cannot ping devices
on the same subnet.  When I run tcpdump on other linux hosts on the
same subnet, I can see that the client does an ARP request for the ip
address it is trying to ping.  I also see the arp-replies on the wire,
but the client continuously sends arp-requests.

The previous version we had working was 2.6.29, and the via-velocity
driver there works fine on this particular hardware.  I've just
compiled 2.6.34-6 and the problem is the same.

Attached is debug.tar.  It contains dmesg, config.gz, ethtool,
ifconfig, and lspci output.  I'm not sure what else to do at this
point.  Is there some debugging I can enable in the kernel to give
more clues as to what's gone wrong?

Cheers!

--
Matt

Download attachment "debug.tar" of type "application/x-tar" (19456 bytes)