Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #629 (new defect)

Opened 16 years ago

Last modified 14 years ago

ath0: ath_reset: unable to reset hardware: 'Hardware didn't respond as expected' (HAL status 3)

Reported by: heller@deepsoft.com Assigned to:
Priority: major Milestone:
Component: madwifi: HAL Version:
Keywords: Cc:
Patch is attached: 0 Pending:

Description

I have a P133 Laptop (a Toshiba Tecra 510CDT) and a Netgear WG511T wireless PC PCMCIA/CardBus card. I am running both White Box Linux 3.0 (aka RHEL 3.0) and CentOS 4.3 (aka RHEL 4.3). I have the FC1 kernel (2.4.22-1.2199.8.legacy.nptl) and the madwifi RPMs from ATRPMS.net on the White Box Linux 3.0 side and a custom re-built 2.6.9-34 kernel and localy built madwifi driver on the CentOS side. With both systems, the driver loads and the card is detected and works for a short time. Then it stops working. In my /var/log/messages file I get these messages:

From /var/log/messages file (madwifi-old-r1417-20060128:)

May  3 10:04:37 gollum kernel: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111
, RF5112, RF2413)
May  3 10:04:37 gollum kernel: wlan: 0.8.6.0 (EXPERIMENTAL)
May  3 10:04:37 gollum kernel: ath_rate_sample: 1.2
May  3 10:04:37 gollum kernel: ath_pci: 0.9.6.0 (EXPERIMENTAL)
May  3 10:04:37 gollum kernel: PCI: Enabling device 0000:05:00.0 (0000 -> 0002)
May  3 10:04:37 gollum kernel: Build date: May  3 2006
May  3 10:04:37 gollum kernel: Debugging version (IEEE80211)
May  3 10:04:37 gollum kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
May  3 10:04:37 gollum kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps
 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
May  3 10:04:37 gollum kernel: ath0: turboG rates: 6Mbps 9Mbps 12Mbps 18Mbps 24M
bps 36Mbps 48Mbps 54Mbps
May  3 10:04:37 gollum kernel: ath0: H/W encryption support: WEP AES AES_CCM TKI
P
May  3 10:04:37 gollum kernel: ath0: mac 7.9 phy 4.5 radio 5.6
May  3 10:04:37 gollum kernel: ath0: Use hw queue 1 for WME_AC_BE traffic
May  3 10:04:37 gollum kernel: ath0: Use hw queue 0 for WME_AC_BK traffic
May  3 10:04:37 gollum kernel: ath0: Use hw queue 2 for WME_AC_VI traffic
May  3 10:04:37 gollum kernel: ath0: Use hw queue 3 for WME_AC_VO traffic
May  3 10:04:38 gollum kernel: ath0: Use hw queue 8 for CAB traffic
May  3 10:04:38 gollum kernel: ath0: Use hw queue 9 for beacons
May  3 10:04:38 gollum kernel: Debugging version (ATH)
May  3 10:04:38 gollum kernel: ath0: Atheros 5212: mem=0x11000000, irq=11
May  3 10:04:41 gollum kernel: ip_tables: (C) 2000-2002 Netfilter core team
May  3 10:04:41 gollum dhclient: dhclient(4221) is already running - exiting. 
May  3 10:05:11 gollum dhclient: Internet Systems Consortium DHCP Client V3.0.1
May  3 10:05:11 gollum dhclient: Copyright 2004 Internet Systems Consortium.
May  3 10:05:11 gollum dhclient: All rights reserved.
May  3 10:05:11 gollum dhclient: For info, please visit http://www.isc.org/produ
cts/DHCP
May  3 10:05:11 gollum dhclient: 
May  3 10:05:12 gollum dhclient: Listening on LPF/ath0/00:14:6c:44:15:0c
May  3 10:05:12 gollum dhclient: Sending on   LPF/ath0/00:14:6c:44:15:0c
May  3 10:05:12 gollum dhclient: Sending on   Socket/fallback
May  3 10:05:12 gollum dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67
May  3 10:05:12 gollum dhclient: DHCPACK from 144.228.189.114
May  3 10:05:14 gollum NET: /sbin/dhclient-script : updated /etc/resolv.conf
May  3 10:05:14 gollum dhclient: bound to 204.248.129.14 -- renewal in 1585 seco
nds.
May  3 10:05:25 gollum kernel: ath0: hardware error; resetting
May  3 10:05:25 gollum kernel: ath0: ath_reset: unable to reset hardware: 'Hardw
are didn't respond as expected' (HAL status 3)
May  3 10:06:42 gollum kernel: ath_pci: driver unloaded
May  3 10:06:42 gollum kernel: ath_rate_sample: unloaded
May  3 10:06:42 gollum kernel: wlan: driver unloaded
May  3 10:06:42 gollum kernel: ath_hal: driver unloaded

I get the same error message 'ath0: hardware error; resetting // ath0: ath_reset: unable to reset hardware: 'Hardware didn't respond as expected' (HAL status 3)'. Both kernels (2.4 and 2.6), and with the 'old' and 'ng' drivers (recent snapshots under the 2.6 kernel, I only got the 'old' (stable) driver working with the 2.4 kernel)). I have posted *twice* to the madwifi-users mailing list, with no useful response. I did set the PCI Subordinate Bus setting up, but this has no effect.

Is this a known problem? Is it a problem with the fact that this is an older '586 Laptop? I can live with non-functionallity with the 2.4 kernel, but with the 2.6 kernel?!?!? And no, I don't have ANY flavor of MS-Windows installed on this machine. And yes, I am willing to help fix this, if I had any clue as to what to try. The mailing list response has been non-existent. I am about to give up on wireless access -- I'll probably be returning the Netgear card. I am not about to buy a new laptop, so that in itself is not a solution at this time. I would be willing to get a different wireless card, if there is a make and model that is known to work with my laptop and this driver (or some other driver).

Change History

05/19/06 15:40:15 changed by anonymous

  • owner changed.
  • component changed from madwifi: driver to madwifi: HAL.

06/28/06 01:35:29 changed by Mortici

I have the same problem, at least i get that error as well. But the funky part is i have to plug the card in and out a few times in order for the driver to recognize it and make it work, and even then i have connectivity for about 15 to 20 mins then in locks up the laptop, untill i pull the card out, then its another game of plug in plug out and hope it gets recognized.

Greg.

08/19/06 23:29:51 changed by Joerg@linux-online24.de

Same problem here. Is there a patch available?

08/21/06 07:12:33 changed by mrenzmann

@Joerg: Not yet. Since the HAL reports to the driver that something didn't work as expected, the first thing would be to find out what exactly happens. This needs some interaction with Atheros, which is what I'm working on.

Which versions of MadWifi did you test? Do you have the same cardbus card as mentioned in the initial report? What does your system look like?

08/25/06 19:52:15 changed by anonymous

I have the same problem with chipset 5212 with latest madwifi-ng checkout from subversion. pcmcia card is wpn511.

11/14/06 11:08:34 changed by gregery20@yahoo.com.au

I have this problem too, with a Netgear W311T PCI wireless card. Is there any workarounds for this? Such as a script that will get the card working again if it fails this way. It seems to happen about once per day.

12/26/06 09:32:03 changed by anonymous

Same problem here with a Netgear WG311T

02/21/07 00:02:39 changed by SubMarine

I get the same error (after a few minutes) with Netgear WG511T when i've bridged my wireless pcmcia card (mastermode) (wg511t) and my 3com pcmcia lan card. Problem also happens instantly if I start transfering a file through the bridge at high speeds. I have no problems when the interfaces aren't bridged.

11/08/07 03:27:09 changed by junfirst@nate.com

Hi, all please help me..... now i got the following messages......

# wifi0: stuck beacon; resetting (bmiss count 11) # wifi0: ath_reset: unable to reset hardware: 'Hardware didn't respond as expected ' (HAL status 3)

i didn't find the solution..... What is the problems??????? What can i do...????