|Anonymous | Login | Signup for a new account||2016-02-08 18:07 MST|
|Main | My View | View Issues | Change Log | Roadmap | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000189||[channel: elrepo/el6] kmod-atl1e||crash||sometimes||2011-10-10 17:12||2012-04-19 18:01|
|Summary||0000189: kmod-atl1e driver crashes during sustained heavy network traffic|
I'm using kmod-atl1e-18.104.22.168-1.el6.elrepo.x86_64 with the latest 64-bit CentOS 6 kernel (2.6.32-131.12.1.el6.x86_64) on a Dell Zino HD with an Atheros AR8151 gigabit ethernet adapter. It's attached to a 100Mbit/sec switch that appears to have auto-neg'ed correctly according to ethtool.
At times of sustained heavy network traffic (usually via large multiple file copies across the network_using NFS, rsync or sftp, the network connection locks solid after anything between 2 and 20 minutes. As a side point, forcing autoneg off via ethool (e.g. "ethtool -s eth0 speed 100 duplex full autoneg off") also locks up the network connection in an identical manner (the lights go off completely on the network socket).
|Additional Information||I was trying to find the original source for this package and the URL that everyone quotes ( http://partner.atheros.com/Drivers.aspx [^] ) is badly broken with a Bad Request error :-( I ended up finding it on a filesharing site of all places! Unpacking that source reveals that there are various options to change size of buffers etc. for the driver - I'm wondering if it's simply running out of transmit/receive buffers and crashing out at high traffic levels? Maybe the driver needs a rebuild with higher default buffer values (I'm just grabbing at straws here)?|
|Tags||No tags attached.|
Hmm, it would appear that Atheros has been purchased by Qualcomm, and we can't seem to find the driver sources on the new site, making it somewhat hard to continue to update these drivers.
If anyone can find a link to the sources, it would be useful.
WRT the driver version in question - obviously we have the source available as part our our SRPM so a rebuild with different parameters is possible although ideally I'd prefer to see such issues fixed upstream (with Qualcomm now).
A little bit of detective work turned up the fact it looks like the atl1e driver is to be abandoned by Qualcomm Atheros and a new driver, "alx", is in development to replace it:
Unfortunately from the above URL, the engineer put on the case to do it seems somewhat inexperienced with kernel network driver development if the initial conversation is to be believed :-(
It does look like a patch for alx has turned up though:
At what it will be "backportable" to CentOS 6's 2.6.32 kernel is anyone's guess - let's hope nothing post-2.6.32 is used by the new alx driver...
The alx driver has been released here:
I have downloaded the compat-wireless package that they link and it works fine in my setup:
Can I therefore suggest that you look at providing kmod-alx as RPMs on ELRepo? The alx driver is intended to completely replace the old atl1e driver.
Re. note 1750. Thank you for the update.
I have just one query. You mention a "compat-wireless" package and then later suggest that it be used to replace the atl1e driver. The atl1e kmod package that we currently provide is for wired, not wireless, connections.
Please clarify the situation.
The alx driver has been added to the compat-wireless package, which did indeed confuse me initially because the name almost suggests that the package just contains wireless drivers for old devices! This isn't true, however, because if you download the compat-wireless package, it actually contains wireless, wired and even Bluetooth drivers in it.
If you run "scripts/driver-select" with no parameters from inside the unpacked compat-wireless package, you get a full list of all the drivers included:
Usage: scripts/driver-select [ <driver-name> | <driver-group-name> | restore ]
Supported 802.11 drivers:
Supported Ethernet drivers:
Supported group drivers:
atheros < ath5k ath9k carl9170 zd1211rw ath6kl >
ath < ath5k ath9k carl9170 ath6kl >
brcm80211 < brcmsmac brcmfmac >
intel < iwlwifi, iwlegacy >
rtl818x < rtl8180 rtl8187 >
rtlwifi < rtl8192ce >
ti < wl1251 wl12xx (SPI and SDIO)>
Supported group drivers: Bluetooth & Ethernet:
atlxx < atl1 atl2 atl1e alx>
bt < Linux bluetooth drivers >
restore: you can use this option to restore compat-wireless to the original state
So the build sequence I used was:
bzcat compat-wireless-2012-02-28-p.tar.bz2 | tar xvf -
It should be noted that alx has a dependency on the compat module that's also installed via "make install". I tracked down what actually gets run and installed - here's what happens:
Command: version="`uname -r`"
Command: cd /lib/modules/$version/build
Command: /sbin/depmod -ae -F System.map $version
Command: /sbin/depmod -a
It should be noted that there are various scripts also installed into /usr/sbin, but you don't really need them at all. I'm not sure about the two udev files installed (are they used?), but I've included them to be safe.
Thank you for clarifying the issue and thus erasing my confusion.
That package looks very interesting. I have added it to the bottom of my ToDo list and I will try to get the alx package built as soon as possible.
There is an active RFE for compat-wireless here:
However, I'm not sure if the alx driver is included in that 3.3-rc1 tarball. The list of drivers in the latest package is:
$ find . -name *.ko
A compat-wireless package is now available for those who would like to test.
The alx driver doesn't yet appeared to have made it into the stable branch but atl1e.ko is there so I don't know if that provides a better option than the kmod-atl1e driver? I'm assuming the alx driver will filter down to the stable branch in due course.
Please feel free to provide any feedback if you are able to test.
|Unfortunately, the atl1e driver situation got so bad for us (a crash a day with the Zinos), that there would be mutiny at work if I tried that driver again. We've had zero problems with alx, so I'm sticking with that. If/when alx appears in compat-wireless officially, then we'd be willing to try whatever you package up.|
|OK, thanks for that.|
|I'm going to close this bug now. We can test the alx driver as and when it makes it into the compat-wireless package.|
|2011-10-10 17:12||rkl||New Issue|
|2011-10-10 17:12||rkl||Status||new => assigned|
|2011-10-10 17:12||rkl||Assigned To||=> burakkucat|
|2011-10-13 11:07||pperry||Note Added: 0001129|
|2011-11-07 10:33||rkl||Note Added: 0001196|
|2012-03-02 08:39||rkl||Note Added: 0001750|
|2012-03-02 12:07||burakkucat||Note Added: 0001752|
|2012-03-02 12:07||burakkucat||Status||assigned => feedback|
|2012-03-02 15:43||rkl||Note Added: 0001753|
|2012-03-02 15:56||burakkucat||Note Added: 0001754|
|2012-03-02 15:56||burakkucat||Status||feedback => assigned|
|2012-03-06 16:51||toracat||Relationship added||related to 0000243|
|2012-03-09 16:52||burakkucat||Assigned To||burakkucat => pperry|
|2012-03-10 12:38||pperry||Note Added: 0001821|
|2012-03-20 07:23||pperry||Note Added: 0001890|
|2012-03-26 15:37||rkl||Note Added: 0001912|
|2012-03-26 22:02||pperry||Note Added: 0001913|
|2012-04-19 17:59||pperry||Note Added: 0002038|
|2012-04-19 18:01||pperry||Status||assigned => resolved|
|2012-04-19 18:01||pperry||Resolution||open => not fixable|
|Mantis 1.1.8[^] Copyright © 2000 - 2009 Mantis Group|