BUG - ath9k keep on disconnecting in 2.6.28-rc8

Previous thread: Re: linux-next: Tree for December 12 (netdev ops) by Randy Dunlap on Sunday, December 14, 2008 - 1:26 am. (2 messages)

Next thread: BUG - ath9k keep on disconnecting in 2.6.28-rc8-tip by Jaswinder Singh on Sunday, December 14, 2008 - 4:14 am. (1 message)
To: <linux-kernel@...>, <netdev@...>, <lrodriguez@...>, <jmalinen@...>, <linux-wireless@...>, <ath9k-devel@...>
Date: Sunday, December 14, 2008 - 3:54 am

Hello all,

I am facing problem with 2.6.28-rc8, ath9k keep on disconnecting.

dmesg :
ath9k: 0.1
ath9k 0000:08:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ath9k 0000:08:00.0: setting latency timer to 64
phy0: Selected rate control algorithm 'ath9k_rate_control'
Registered led device: ath9k-phy0:radio
Registered led device: ath9k-phy0:assoc
Registered led device: ath9k-phy0:tx
Registered led device: ath9k-phy0:rx
phy0: Atheros 9280: mem=0xffffc20006200000, irq=17

/sbin/lspci -vv :
08:00.0 Network controller: Atheros Communications Inc. Device 002a (rev 01)
Subsystem: Hewlett-Packard Company Device 1381
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 128 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at d1100000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable-
Address: 00000000 Data: 0000
Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM unknown, Latency L0
<512ns, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive-...

To: Jaswinder Singh <jaswinderlinux@...>
Cc: <linux-kernel@...>, <netdev@...>, <lrodriguez@...>, <jmalinen@...>, <linux-wireless@...>, <ath9k-devel@...>
Date: Sunday, December 14, 2008 - 4:30 am

I'm seeing:
Capabilities: [140] Virtual Channel <?>
in you're post, leading me to believe, you're
missing a capability?
from what I understand, if you're using
NetworkManager you need to
adduser "name" netdev
then have NetworkManager load
wpa_supplicant at the right time.
under the right circumstances..

regards;

Justin P. Mattock

--

To: Jaswinder Singh <jaswinderlinux@...>
Cc: <linux-kernel@...>, <netdev@...>, <lrodriguez@...>, <jmalinen@...>, <linux-wireless@...>, <ath9k-devel@...>
Date: Sunday, December 14, 2008 - 4:09 am

A number of updates have gone into the wireless-testing tree.
You can use that tree or compat-wireless to get the latest driver
and check if the problem persists.

Sujith
--

To: Sujith <m.sujith@...>
Cc: <linux-kernel@...>, <netdev@...>, <lrodriguez@...>, <jmalinen@...>, <linux-wireless@...>, <ath9k-devel@...>
Date: Sunday, December 14, 2008 - 11:14 am

Hello Sujith,

It seems wireless-testing tree fixed my ath9k problem, I am quite
happy with it :-)

I am still checking ath9k by using wireless-testing tree with
different ways and let you know If I face more problems.

Thanks for your help.

Jaswinder Singh.
--

Previous thread: Re: linux-next: Tree for December 12 (netdev ops) by Randy Dunlap on Sunday, December 14, 2008 - 1:26 am. (2 messages)

Next thread: BUG - ath9k keep on disconnecting in 2.6.28-rc8-tip by Jaswinder Singh on Sunday, December 14, 2008 - 4:14 am. (1 message)