[lucid] ath5k phy1: no further txbuf available, dropping packet wireless drops connection after large transfer on virtualbox to the host on bridged ethernet

[Julian G.]

Presumably this is present on every kernel.
View the attached dmesg.

I transfered a 300MB file over FTP on a bridged wireless connection using filezilla on the VM and pure-ftpd on the host

The HOSTS adapter driver then spit errors (ath5k) and dropped the wireless connection

I could not re-engage the connection unless i did a rmmod ath5k;modprobe ath5k

[13289.569680] ath5k phy0: no further txbuf available, dropping packet
[13290.004620] ath5k phy0: failed to warm reset the MAC Chip
[13290.004632] ath5k phy0: can't reset hardware (-5)
[13290.649288] ath5k phy0: failed to warm reset the MAC Chip
[13290.649300] ath5k phy0: can't reset hardware (-5)
[13295.869220] ath5k phy0: failed to warm reset the MAC Chip
[13295.869232] ath5k phy0: can't reset hardware (-5)
[13298.390090] No probe response from AP 00:0f:b3:73:75:c9 after 500ms, disconnecting.
[13299.241830] ath5k phy0: no further txbuf available, dropping packet
[13299.704070] ath5k phy0: no further txbuf available, dropping packet
[13301.731809] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13301.930063] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13302.130059] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13302.330052] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13309.249425] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13309.440067] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13309.640076] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13309.840050] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13316.608307] ath5k phy0: no further txbuf available, dropping packet
[13319.022242] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13319.220076] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13319.420053] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13319.620051] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13326.349543] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13326.540063] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13326.740064] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13326.940686] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13331.356875] ath5k phy0: no further txbuf available, dropping packet
[13332.010581] ath5k phy0: no further txbuf available, dropping packet
[13333.865118] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13334.060077] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13334.260340] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13334.460750] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13339.999231] ath5k phy0: failed to warm reset the MAC Chip
[13339.999243] ath5k phy0: can't reset hardware (-5)
[13341.480720] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13341.680056] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13341.880056] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13342.080054] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13346.515218] ath5k phy0: no further txbuf available, dropping packet
[13348.828173] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13349.020074] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13349.220064] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13349.420062] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13356.307562] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13356.500371] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13356.700479] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13356.900064] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13361.268898] ath5k phy0: no further txbuf available, dropping packet
[13363.662923] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13363.860058] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13364.060072] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13364.260075] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13370.972344] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13371.170069] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13371.370066] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13371.570066] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13376.046523] ath5k phy0: no further txbuf available, dropping packet
[13377.158991] ath5k phy0: failed to warm reset the MAC Chip
[13377.159002] ath5k phy0: can't reset hardware (-5)
[13403.459397] ath5k phy0: no further txbuf available, dropping packet
[13404.509077] ath5k phy0: failed to warm reset the MAC Chip
[13404.509085] ath5k phy0: can't reset hardware (-5)
[13405.880394] ath5k phy0: no further txbuf available, dropping packet
[13417.921540] ath5k 0000:02:06.0: PCI INT A disabled
[13420.894996] ath5k 0000:02:06.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18
[13420.895094] ath5k 0000:02:06.0: registered as 'phy1'
[13420.953863] ath: EEPROM regdomain: 0x10
[13420.953868] ath: EEPROM indicates we should expect a direct regpair map
[13420.953874] ath: Country alpha2 being used: CO
[13420.953877] ath: Regpair used: 0x10
[13421.011139] phy1: Selected rate control algorithm 'minstrel'
[13421.011995] ath5k phy1: Atheros AR5212 chip found (MAC: 0x56, PHY: 0x41)
[13421.011999] ath5k phy1: RF5112B multiband radio found (0x36)
[13421.697609] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[13421.697624] device wlan0 entered promiscuous mode
[13449.477569] wlan0: deauthenticating from 00:0f:b3:73:75:c9 by local choice (reason=3)
[13449.498239] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13449.500676] wlan0: direct probe responded
[13449.500687] wlan0: authenticate with AP 00:0f:b3:73:75:c9 (try 1)
[13449.502069] wlan0: authenticated
[13449.502113] wlan0: associate with AP 00:0f:b3:73:75:c9 (try 1)
[13449.503929] wlan0: RX AssocResp from 00:0f:b3:73:75:c9 (capab=0x461 status=0 aid=1)
[13449.503936] wlan0: associated
[13449.505187] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[13459.830030] wlan0: no IPv6 routers present
[13486.331136] ath5k phy1: no further txbuf available, dropping packet
[13488.160450] ath5k phy1: no further txbuf available, dropping packet
[13491.960044] No probe response from AP 00:0f:b3:73:75:c9 after 500ms, disconnecting.
[13494.449373] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13494.640080] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13494.840053] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13495.040067] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13499.518610] ath5k phy1: no further txbuf available, dropping packet
[13501.956644] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 1)
[13502.150063] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 2)
[13502.350061] wlan0: direct probe to AP 00:0f:b3:73:75:c9 (try 3)
[13502.550079] wlan0: direct probe to AP 00:0f:b3:73:75:c9 timed out
[13517.954246] ath5k phy1: no further txbuf available, dropping packet

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user 2778 F.... pulseaudio
 /dev/snd/pcmC0D0c: user 2778 F...m pulseaudio
 /dev/snd/pcmC0D0p: user 2778 F...m pulseaudio
 /dev/snd/timer: user 2778 f.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Audigy'/'SB Audigy 1 [SB0090] (rev.3, serial:0x511102) at 0xa000, irq 19'
   Mixer name : 'TriTech TR28602'
   Components : 'AC97a:54524123'
   Controls : 194
   Simple ctrls : 30
Date: Thu Nov 12 17:40:18 2009
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=28374986-cd2a-45db-a2b4-1ef488bc9f28
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 05af:0802 Jing-Mold Enterprise Co., Ltd
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ECS nForce3-A
NonfreeKernelModules: nvidia
Package: linux-image (not installed)
ProcCmdLine: root=UUID=b4320cec-4db6-4a7e-9d86-24ad95705604 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-3.4-server
Regression: No
RelatedPackageVersions: linux-firmware 1.24
Reproducible: Yes
RfKill:
 2: phy2: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux-meta
Tags: needs-upstream-testing
TestedUpstream: No
Uname: Linux 2.6.32-3-server x86_64
dmi.bios.date: 09/16/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: nForce3-A
dmi.board.vendor: ECS
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/16/2005:svnECS:pnnForce3-A:pvr:rvnECS:rnnForce3-A:rvr:cvnECS:ct3:cvr:
dmi.product.name: nForce3-A
dmi.sys.vendor: ECS

[Andy Whitcroft (apw)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and tag it kj-linux-meta, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

[Andy Whitcroft (apw)]

Could you test the latest Lucid kernel (2.6.32-4.5) and confirm if this issue appears there. Thanks!

[Andy Whitcroft (apw)]

There is now a Lucid 2.6.32-6.8 kernel which has significant changes from the -3 previously reported. Could we confirm this issue with this updated version. Thanks!

[bhasker (bhasker-unixindia)]

I am using 2.6.33 kernel
I am still getting this problem
>
[ 5875.598722] ath5k phy0: failed to warm reset the MAC Chip
[ 5875.598734] ath5k phy0: can't reset hardware (-5)
[ 5880.500557] No probe response from AP 00:03:7f:00:cc:1f after 500ms, disconnecting.
[ 5881.357102] wlan0: direct probe to AP 00:03:7f:00:cc:1f (try 1)
[ 5881.360465] wlan0: direct probe responded
[ 5881.360475] wlan0: authenticate with AP 00:03:7f:00:cc:1f (try 1)
[ 5881.361961] wlan0: authenticated
[ 5881.361988] wlan0: associate with AP 00:03:7f:00:cc:1f (try 1)
[ 5881.364675] wlan0: RX ReassocResp from 00:03:7f:00:cc:1f (capab=0x431 status=0 aid=1)
[ 5881.364685] wlan0: associated
>

I am not able to use ath5k at-all for a high data throughput purpose. The problem is that I use nfs for my home dir
and as-long-as things are under speed, things are fine. If i start accessing large files (especially videos)
I end up getting these errors.

[passshok (passshok)]

I have same bug on Gentoo Linux kernel and ath5k driver patched with latest compat-wireless-2009-12-11.

Jan 19 16:45:51 morex kernel: [171281.775253] ath5k phy0: no further txbuf available, dropping packet
Jan 19 16:46:01 morex kernel: [171291.810470] ath5k phy0: no further txbuf available, dropping packet

repeats every 10 seconds after some time of work irrespective of amount of data, transferred through the interface.

[Luciana Silva (lucianasilvaoliveira)]

I'm also having this problem.

luciana@netbook:~$ uname -a
Linux netbook 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010 i686 GNU/Linux

luciana@netbook:~$ dmesg |grep "ath5k phy0"
[13724.687168] ath5k phy0: no further txbuf available, dropping packet
[13734.738739] ath5k phy0: no further txbuf available, dropping packet
[13744.823959] ath5k phy0: no further txbuf available, dropping packet
[13754.915964] ath5k phy0: no further txbuf available, dropping packet
[13764.911521] ath5k phy0: no further txbuf available, dropping packet
[13774.941860] ath5k phy0: no further txbuf available, dropping packet
[13785.014001] ath5k phy0: no further txbuf available, dropping packet
[13975.211230] ath5k phy0: no further txbuf available, dropping packet
[13985.191887] ath5k phy0: no further txbuf available, dropping packet
[13995.230163] ath5k phy0: no further txbuf available, dropping packet
[14005.256574] ath5k phy0: no further txbuf available, dropping packet
[14015.271743] ath5k phy0: no further txbuf available, dropping packet
[14025.277964] ath5k phy0: no further txbuf available, dropping packet
[14315.407544] ath5k phy0: no further txbuf available, dropping packet
[14325.462947] ath5k phy0: no further txbuf available, dropping packet
[14335.467683] ath5k phy0: no further txbuf available, dropping packet
[14345.479937] ath5k phy0: no further txbuf available, dropping packet
[14355.492361] ath5k phy0: no further txbuf available, dropping packet
[14365.582346] ath5k phy0: no further txbuf available, dropping packet
[14375.617150] ath5k phy0: no further txbuf available, dropping packet
[14385.696993] ath5k phy0: no further txbuf available, dropping packet
[14386.980546] ath5k phy0: no further txbuf available, dropping packet

[Luciana Silva (lucianasilvaoliveira)]

My device:
03:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)

[Michael R. Head (burner)]

Debbug 576213 may be related, though it's particular to the use of hostapd (which is how this bug is affecting me)

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576213

[Michael R. Head (burner)]

This kernel patch may be related: https://patchwork.kernel.org/patch/71995/

[Michael R. Head (burner)]

The associated debbug ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576213 ) has now been closed after the developers went to 2.6.32.11:

...
 Add stable 2.6.32.11.
     - MIPS: Cleanup forgotten label_module_alloc in tlbex.c (Closes: #571305)
     - ath5k: fix setup for CAB queue (closes: #576213)
     - NFS: Prevent another deadlock in nfs_release_page() (Closes: #574348)
...

[Michael R. Head (burner)]

I noticed that the new kernel in Lucid ( 2.6.32-20.29 ) now has the above patch.

https://launchpad.net/ubuntu/+source/linux/2.6.32-20.29:

  * ath5k: dont use external sleep clock in AP mode
    - LP: #553837
  * ath5k: fix setup for CAB queue
    - LP: #553837

I'll try this for a few days and if it corrects it, then perhaps this bug was just a dupe of #553837

[Michael R. Head (burner)]

I haven't seen this problem since upgrading to 2.6.32-20.29. I'm going to close it, because I think it has been fixed.

[Ve0 (veo-)]

I have this problem on Ubuntu 10.04

# uname -a
Linux veo-server 2.6.32-22-server #35-Ubuntu SMP Tue Jun 1 15:34:46 UTC 2010 x86_64 GNU/Linux

# cat kern.log |grep ath5k
Jun 4 01:09:58 veo-server kernel: [710192.792950] ath5k phy0: failed to warm reset the MAC Chip
Jun 4 01:09:58 veo-server kernel: [710192.792994] ath5k phy0: can't reset hardware (-5)
Jun 4 01:12:31 veo-server kernel: [ 7.585780] ath5k 0000:03:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
Jun 4 01:12:31 veo-server kernel: [ 7.585834] ath5k 0000:03:00.0: registered as 'phy0'
Jun 4 01:12:31 veo-server kernel: [ 8.327730] ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45)
Jun 4 14:23:30 veo-server kernel: [47471.899535] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:35 veo-server kernel: [47477.123156] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:36 veo-server kernel: [47477.225536] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:36 veo-server kernel: [47477.225585] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:36 veo-server kernel: [47477.225627] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:36 veo-server kernel: [47477.225671] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:36 veo-server kernel: [47477.225712] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:45 veo-server kernel: [47487.160862] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:46 veo-server kernel: [47487.263247] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:55 veo-server kernel: [47497.162668] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:56 veo-server kernel: [47497.300960] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:56 veo-server kernel: [47497.301006] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:56 veo-server kernel: [47497.301048] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:23:56 veo-server kernel: [47497.301090] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:24:06 veo-server kernel: [47507.236267] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:24:16 veo-server kernel: [47517.273977] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:24:26 veo-server kernel: [47527.311688] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:24:36 veo-server kernel: [47537.316485] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:24:46 veo-server kernel: [47547.387106] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:24:56 veo-server kernel: [47557.424817] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:25:06 veo-server kernel: [47567.462539] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:25:16 veo-server kernel: [47577.470229] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:25:26 veo-server kernel: [47587.537947] ath5k phy0: no further txbuf available, dropping packet
Jun 4 14:25:36 veo-server kernel: [47597.575657] ath5k phy0: no further txbuf available, ...

[telmich (nico-launpad-net)]

Similar (same?) issue here on 2.6.32-22-generic with hostapd running in AP mode: When transferring a lot of data, I get the following messages:

[190164.801177] ath5k phy0: failed to warm reset the MAC Chip
[190164.801189] ath5k phy0: can't reset hardware (-5)
[190164.821089] ath5k phy0: noise floor calibration failed (2412MHz)

Restarting hostapd helps.

Thread on ath5k-devel related: http://<email address hidden>/msg03192.html

Not sure whether it's fixed somewhere upstream or not.

[Ve0 (veo-)]

I have same problem:

Aug 12 23:05:28 veo-server kernel: [ 726.085724] ath5k phy0: unsupported jumbo
Aug 12 23:05:50 veo-server kernel: [ 748.000101] ath5k phy0: failed to warm reset the MAC Chip
Aug 12 23:05:50 veo-server kernel: [ 748.000144] ath5k phy0: can't reset hardware (-5)

Linux 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010 x86_64 GNU/Linux

[Sydoruk Yaroslav (lip)]

Ubuntu 10.04.1 LTS
0a:03.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)

[1877012.334350] ath5k phy0: no further txbuf available, dropping packet
[1877793.090586] ath5k phy0: no further txbuf available, dropping packet
[1879173.910912] ath5k phy0: no further txbuf available, dropping packet
[2128339.677632] ath5k phy0: no further txbuf available, dropping packet
[2128369.707140] ath5k phy0: no further txbuf available, dropping packet
[2128549.780059] ath5k phy0: no further txbuf available, dropping packet
[2129000.552386] ath5k phy0: no further txbuf available, dropping packet
[2129271.076893] ath5k phy0: no further txbuf available, dropping packet
[2129491.553117] ath5k phy0: no further txbuf available, dropping packet

[Sydoruk Yaroslav (lip)]

 ath5k phy0: no further txbuf available, dropping packet
This error was if I enable WPA-PSK
network={
   ssid="external"
    proto=RSN WPA
   key_mgmt=WPA-PSK
   pairwise=CCMP TKIP
   group=CCMP TKIP
    scan_ssid=1
   psk="wdqweqweqweqweqweqeqeqe"
    priority=2
}
If I use key_mgmt=NONE
all works fine