From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Date: Mon, 23 Jul 2012 14:10:47 -0700 Subject: [ath9k-devel] Seem to have fried my AR9300 NIC? Message-ID: <500DBDD7.1050001@candelatech.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Came back after a 1 week vacation and found the 3.3.8+ kernel spitting timeout errors, and network devices will not 'ifconfig foo up'. I rebooted into 3.5.0+, and see the same (or at least similar errors): ath: wiphy0: timeout (100000 us) on reg 0xa2c4: 0x00158dd9 & 0x00000001 != 0x00000000 ath: wiphy0: Unable to reset hardware; reset status -5 (freq 2412 MHz) ath: wiphy0: timeout (100000 us) on reg 0xa640: 0x00000001 & 0x00000001 != 0x00000000 ath: wiphy0: timeout (100000 us) on reg 0xa2c4: 0x00158dd9 & 0x00000001 != 0x00000000 ath: wiphy0: Unable to reset hardware; reset status -5 (freq 2412 MHz) ath: wiphy0: timeout (100000 us) on reg 0xa640: 0x00000001 & 0x00000001 != 0x00000000 ath: wiphy0: timeout (100000 us) on reg 0xa2c4: 0x00158dd9 & 0x00000001 != 0x00000000 ath: wiphy0: Unable to reset hardware; reset status -5 (freq 2412 MHz) This system ran stable for several months..so maybe the hardware just died. But if anyone has any suggestions for debugging this more, please let me know. 03:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN adaptor (rev 01) Subsystem: Atheros Communications Inc. Device 3116 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Candela Technologies Inc http://www.candelatech.com