* Re: 3.3.1 ath9k regression [not found] ` <iM56i-6N7-11@gated-at.bofh.it> @ 2012-04-04 19:33 ` Martin 0 siblings, 0 replies; 4+ messages in thread From: Martin @ 2012-04-04 19:33 UTC (permalink / raw) To: Linux Kernel Mailing List, ath9k-devel, ath9k-devel On 04/03/2012 08:10 AM, Ben Greear wrote: > Ath9k list should be interested in this... > > Ben > > On 04/02/2012 10:46 PM, Kelly Anderson wrote: >> This patch in 3.3.1 is causing ath9k device not to show/work on bootup. >> ifconfig does not show the device unless I revert this patch. With the >> patch >> reverted the device works as expected. This is verified on two different >> machines that are both using ath9k mini-pcie wifi cards. >> >>>> ath9k: fix going to full-sleep on PS idle >> >>>> commit c1afdaff90538ef085b756454f12b29575411214 upstream. >> >> >> -- >> To unsubscribe from this list: send the line "unsubscribe >> linux-kernel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ fwiw, I find the same issue on an Asus P50IJ, same fix by reverting the commit from above. Martin 02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: AzureWave Device 1089 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: 32 bytes Interrupt: pin A routed to IRQ 17 Region 0: Memory at feaf0000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [60] Express (v2) 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 L0s L1, Latency L0 <512ns, L1 <64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB Kernel driver in use: ath9k ^ permalink raw reply [flat|nested] 4+ messages in thread
* 3.3.1 ath9k regression @ 2012-04-03 5:46 Kelly Anderson 2012-04-03 6:01 ` Ben Greear 2012-04-04 10:40 ` Mantas M. 0 siblings, 2 replies; 4+ messages in thread From: Kelly Anderson @ 2012-04-03 5:46 UTC (permalink / raw) To: Linux Kernel Mailing List This patch in 3.3.1 is causing ath9k device not to show/work on bootup. ifconfig does not show the device unless I revert this patch. With the patch reverted the device works as expected. This is verified on two different machines that are both using ath9k mini-pcie wifi cards. >> ath9k: fix going to full-sleep on PS idle >> commit c1afdaff90538ef085b756454f12b29575411214 upstream. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 3.3.1 ath9k regression 2012-04-03 5:46 Kelly Anderson @ 2012-04-03 6:01 ` Ben Greear 2012-04-04 10:40 ` Mantas M. 1 sibling, 0 replies; 4+ messages in thread From: Ben Greear @ 2012-04-03 6:01 UTC (permalink / raw) To: Kelly Anderson; +Cc: Linux Kernel Mailing List, ath9k-devel@lists.ath9k.org Ath9k list should be interested in this... Ben On 04/02/2012 10:46 PM, Kelly Anderson wrote: > This patch in 3.3.1 is causing ath9k device not to show/work on bootup. > ifconfig does not show the device unless I revert this patch. With the patch > reverted the device works as expected. This is verified on two different > machines that are both using ath9k mini-pcie wifi cards. > >>> ath9k: fix going to full-sleep on PS idle > >>> commit c1afdaff90538ef085b756454f12b29575411214 upstream. > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 3.3.1 ath9k regression 2012-04-03 5:46 Kelly Anderson 2012-04-03 6:01 ` Ben Greear @ 2012-04-04 10:40 ` Mantas M. 1 sibling, 0 replies; 4+ messages in thread From: Mantas M. @ 2012-04-04 10:40 UTC (permalink / raw) To: linux-kernel [Kelly - use `journalctl -a` or just `dmesg` to get full logs.] I have a similar bug with Atheros AR9285 on a ASUS K52JT laptop. The device appears, but refuses to connect to any AP, timing out in less than a second. (3.3-ARCH did not have this bug.) dmesg output while trying to connect to an open AP follows. > # modprobe ath9k > [ 213.662569] ath: EEPROM regdomain: 0x60 > [ 213.662574] ath: EEPROM indicates we should expect a direct regpair map > [ 213.662580] ath: Country alpha2 being used: 00 > [ 213.662583] ath: Regpair used: 0x60 > [ 213.664533] ieee80211 phy1: Selected rate control algorithm 'ath9k_rate_control' > [ 213.666228] Registered led device: ath9k-phy1 > [ 213.666255] ieee80211 phy1: Atheros AR9285 Rev:2 mem=0xffffc90022d60000, irq=17 > # ip link set wlan0 up > [ 215.577316] ADDRCONF(NETDEV_UP): wlan0: link is not ready > # iw wlan0 connect -w cloud > [ 217.667382] wlan0: authenticate with 00:23:8e:e1:6c:c8 (try 1) > [ 217.864456] wlan0: authenticate with 00:23:8e:e1:6c:c8 (try 2) > [ 218.063975] wlan0: authenticate with 00:23:8e:e1:6c:c8 (try 3) > [ 218.263514] wlan0: authentication with 00:23:8e:e1:6c:c8 timed out > # iw wlan0 connect -w cloud > [ 276.603232] wlan0: authenticate with 00:23:8e:e1:6c:c8 (try 1) > [ 276.802003] wlan0: authenticate with 00:23:8e:e1:6c:c8 (try 2) > [ 277.001461] wlan0: authenticate with 00:23:8e:e1:6c:c8 (try 3) > [ 277.200945] wlan0: authentication with 00:23:8e:e1:6c:c8 timed out Using "debug=0xe01" with rmmod/modprobe causes no visible difference. "pcie_aspm=off" did not help. `lspci -v` shows the device as: > > 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) > Subsystem: AzureWave AW-NE785 / AW-NE785H 802.11bgn Wireless Full or Half-size Mini PCIe Card > Flags: bus master, fast devsel, latency 0, IRQ 17 > Memory at d2a00000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [40] Power Management version 3 > Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- > Capabilities: [60] Express Legacy Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Virtual Channel > Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12 > Capabilities: [170] Power Budgeting <?> > Kernel driver in use: ath9k -- Mantas M. <grawity@gmail.com ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-04-04 19:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <iM4WB-6k6-3@gated-at.bofh.it>
[not found] ` <iM56i-6N7-11@gated-at.bofh.it>
2012-04-04 19:33 ` 3.3.1 ath9k regression Martin
2012-04-03 5:46 Kelly Anderson
2012-04-03 6:01 ` Ben Greear
2012-04-04 10:40 ` Mantas M.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).