All of lore.kernel.org
 help / color / mirror / Atom feed
* [ath9k-devel] N not in use.
@ 2009-03-31 21:11 Dmitri Seletski
  2009-04-01  5:26 ` Sujith
  0 siblings, 1 reply; 2+ messages in thread
From: Dmitri Seletski @ 2009-03-31 21:11 UTC (permalink / raw)
  To: ath9k-devel

Hello.

I have noticed several things about driver(apart from failures)

1) If i force N- it doesnt connect at all, it can "see" my wireless when

its in pure N mode.

2) I have noticed, every time i restart my pc, i can connect to wifi.(at

the moment it's in b, g, n mode)

3) with earlier version of drivers, machine used to hang a lot, with no

way for me to determine(X was on)

4) previous versions were not giving that much of error messages in

dmesg, however, once network disconnected (and if computer didn't hang)

i had very small chance to connect

5) I have noticed i get generally problems with computer. But it could

be due corrupted c-lib(because of quite some "hot" reboots)

Driver i used for those attachments - is todays driver, so everything is
fresh.

What can i do to improve anything? i am not programmer... :(
But i'll try to test.

Thanks

Dmitri

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wireless.log
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090331/ff9f064e/attachment-0002.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lspciVV.txt
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090331/ff9f064e/attachment-0003.txt 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [ath9k-devel] N not in use.
  2009-03-31 21:11 [ath9k-devel] N not in use Dmitri Seletski
@ 2009-04-01  5:26 ` Sujith
  0 siblings, 0 replies; 2+ messages in thread
From: Sujith @ 2009-04-01  5:26 UTC (permalink / raw)
  To: ath9k-devel

Dmitri Seletski wrote:
> Hello.
> 
> I have noticed several things about driver(apart from failures)
> 
> 1) If i force N- it doesnt connect at all, it can "see" my wireless when
> 
> its in pure N mode.

What do you mean by forcing to N- mode ?

> [  179.205804] WARNING: at /home/dimko/compat-wireless-2009-03-31/net/mac80211/rx.c:2491 __ieee80211_rx+0x69f/0x6b0 [mac80211]()
> [  179.205811] Modules linked in: it87 hwmon_vid output nvidia(P) ath9k snd_hda_intel mac80211 snd_pcm cfg80211 snd_timer i2c_nforce2 snd k8temp forcedeth hwmon i2c_core soundcore snd_page_alloc
> [  179.205839] Pid: 0, comm: swapper Tainted: P        W  2.6.28.9 #4
> [  179.205843] Call Trace:
> [  179.205846]  <IRQ>  [<ffffffff810431df>] warn_on_slowpath+0x5f/0x90
> [  179.205861]  [<ffffffff810b0437>] ? kmalloc_large_node+0x67/0xc0
> [  179.205868]  [<ffffffff810b1f65>] ? __kmalloc_node_track_caller+0xd5/0xe0
> [  179.205889]  [<ffffffffa0168727>] ? ath_rxbuf_alloc+0x27/0x90 [ath9k]
> [  179.205912]  [<ffffffffa00949ff>] __ieee80211_rx+0x69f/0x6b0 [mac80211]
> [  179.205920]  [<ffffffff813fef52>] ? _spin_unlock_irqrestore+0x12/0x40
> [  179.205939]  [<ffffffffa0168d6c>] ath_rx_tasklet+0x52c/0x820 [ath9k]
> [  179.205958]  [<ffffffffa0167161>] ath9k_tasklet+0x81/0xb0 [ath9k]
> [  179.206254]  [<ffffffffa04e70af>] ? rm_isr+0xaa/0x10a [nvidia]
> [  179.206319]  [<ffffffff810486a4>] tasklet_action+0xb4/0x150
> [  179.206326]  [<ffffffff81049285>] __do_softirq+0x85/0x160
> [  179.206333]  [<ffffffff8100d63c>] call_softirq+0x1c/0x30
> [  179.206340]  [<ffffffff8100eefd>] do_softirq+0x3d/0x80
> [  179.206345]  [<ffffffff81048b95>] irq_exit+0x45/0x50
> [  179.206352]  [<ffffffff8100f21d>] do_IRQ+0x12d/0x200
> [  179.206358]  [<ffffffff8100c8c6>] ret_from_intr+0x0/0xa
> [  179.206362]  <EOI>  [<ffffffff810148e2>] ? default_idle+0x42/0x50
> [  179.206375]  [<ffffffff81014a18>] ? c1e_idle+0x38/0x100
> [  179.206382]  [<ffffffff8105f431>] ? atomic_notifier_call_chain+0x11/0x20
> [  179.206388]  [<ffffffff8100b4d9>] ? cpu_idle+0x69/0xa0
> [  179.206394]  [<ffffffff813f88f0>] ? start_secondary+0x153/0x1b3
> [  179.206400] ---[ end trace 2b0224dc17871e1d ]---

This is a bit weird, can you give us some more details ?
Configuration of the AP, connection type ( encrypted/open ) etc.
Also, please enable CONFIG_ATH9K_DEBUG in config.mk of compat-wireless,
and load the driver with the modparam debug=0x2000 and post the kernel log here.

> 01:00.0 VGA compatible controller: nVidia Corporation G80 [GeForce 8800 GTS] (rev a2) (prog-if 00 [VGA controller])
> 	Subsystem: eVga.com. Corp. Device e825
> 	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
> 	Interrupt: pin A routed to IRQ 16
> 	Region 0: Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
> 	Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
> 	Region 3: Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
> 	Region 5: I/O ports at ac00 [size=128]
> 	[virtual] Expansion ROM at fbfe0000 [disabled] [size=128K]
> 	Capabilities: [60] Power Management version 2
> 		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> 		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 	Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable-
> 		Address: 0000000000000000  Data: 0000
> 	Capabilities: [78] Express (v1) Endpoint, MSI 00
> 		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <4us
> 			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 x16, ASPM L0s L1, Latency L0 <256ns, L1 <4us
> 			ClockPM- Suprise- LLActRep- BwNot-
> 		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
> 			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> 		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
> 	Capabilities: [100] Virtual Channel <?>
> 	Capabilities: [128] Power Budgeting <?>
> 	Kernel driver in use: nvidia
> 	Kernel modules: nvidia

I don't think this should affect ath9k, but still, please remove the binary
kernel module 'nvidia' when you are reporting kernel issues.

Sujith

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-04-01  5:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-31 21:11 [ath9k-devel] N not in use Dmitri Seletski
2009-04-01  5:26 ` Sujith

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.