From: Martin <marogge@onlinehome.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath9k-devel@venema.h4ckr.net, ath9k-devel@venema.h4ckr.net
Subject: Re: 3.3.1 ath9k regression
Date: Wed, 04 Apr 2012 21:33:48 +0200 [thread overview]
Message-ID: <4F7CA21C.2000907@onlinehome.de> (raw)
In-Reply-To: <iM56i-6N7-11@gated-at.bofh.it>
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
WARNING: multiple messages have this Message-ID (diff)
From: Martin <marogge@onlinehome.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] 3.3.1 ath9k regression
Date: Wed, 04 Apr 2012 21:33:48 +0200 [thread overview]
Message-ID: <4F7CA21C.2000907@onlinehome.de> (raw)
In-Reply-To: <iM56i-6N7-11@gated-at.bofh.it>
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 at 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@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
next parent reply other threads:[~2012-04-04 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <iM4WB-6k6-3@gated-at.bofh.it>
[not found] ` <iM56i-6N7-11@gated-at.bofh.it>
2012-04-04 19:33 ` Martin [this message]
2012-04-04 19:33 ` [ath9k-devel] 3.3.1 ath9k regression Martin
2012-04-05 18:25 Ortwin Glück
-- strict thread matches above, loose matches on Subject: below --
2012-04-03 5:46 Kelly Anderson
2012-04-03 6:01 ` Ben Greear
2012-04-04 10:40 ` Mantas M.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F7CA21C.2000907@onlinehome.de \
--to=marogge@onlinehome.de \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.