Since the ath5k driver was included in 2.6.25-rc* I've tried it several times,
but the driver seems pretty unstable in keeping the wireless connection to my router.
Machine is a HP NC6000 Laptop with built-in AR5212 wifi card.
lspci reports:
2:04.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
Subsystem: Compaq Computer Corporation Unknown device 00e5
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at 90080000 (32-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
After modprobing ath5k, dmesg reports with 2.6.25-rc6:
ACPI: PCI Interrupt Link [C0C6] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [C0C6] -> GSI 11 (level, low) -> IRQ 11
ath5k_pci 0000:02:04.0: registered as 'phy0'
phy0: Selected rate control algorithm 'pid'
ath5k phy0: Atheros AR5213 chip found (MAC: 0x56, PHY: 0x41)
ath5k phy0: RF5111 5GHz radio found (0x17)
ath5k phy0: RF2111 2GHz radio found (0x23)
udev: renamed network interface wlan0 to wlan1
wlan1: Initial auth_alg=0
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
wlan1: authenticated
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x471 status=0 aid=1)
wlan1: associated
Everything is OK and I'm connected. 00:50:18:3b:2b:04 is my router.
Around 2-5 minutes later the driver suddenly disconnects and syslog reports the following messages.
Since then, ath5k will not reconnect any longer to the router.
wlan1: invalid Michael MIC in data frame from 00:15:0c:e1:c0:96
wlan1: invalid Michael MIC in data frame from 00:15:0c:e1:c0:96
wlan1: RX disassociation from 00:50:18:3b:2b:04 (reason=1)
wlan1: disassociated
wlan1: deauthenticate(reason=14)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX deauthentication from 00:50:18:3b:2b:04 (reason=9)
wlan1: deauthenticated
wlan1: RX protected frame, but have no key
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
wlan1: authenticated
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: association with AP 00:50:18:3b:2b:04 timed out
wlan1: Initial auth_alg=0
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
wlan1: authenticated
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: association with AP 00:50:18:3b:2b:04 timed out
wlan1: Initial auth_alg=0
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
wlan1: authenticated
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: association with AP 00:50:18:3b:2b:04 timed out
wlan1: RX protected frame, but have no key
wlan1: Initial auth_alg=0
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
wlan1: authenticated
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x451 status=1 aid=1)
wlan1: AP denied association (code=1)
wlan1: association with AP 00:50:18:3b:2b:04 timed out
On the other side, with a Prism54 wifi cardbus card everything works 100% reliable with the same kernel:
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [C0C3] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:03:00.0 to 64
p54: LM86 firmware
p54: FW rev 2.7.0.0 - Softmac protocol 4.1
phy0: Selected rate control algorithm 'simple'
phy0: hwaddr 00:04:e2:b3:7e:91, isl3890
Loaded prism54 driver, version 1.2
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:50:18:3b:2b:04
wlan0: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:50:18:3b:2b:04
wlan0: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x471 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:50:18:3b:2b:04)
Any ideas ?
Helge
On Tue, Mar 25, 2008 at 09:11:05PM +0100, Helge Deller wrote:
> On Tuesday 25 March 2008, Bob Copeland wrote:
> > On Tue, Mar 25, 2008 at 2:16 PM, Nick Kossifidis <[email protected]> wrote:
> > > Hello ppl, sory for the delay ;-)
> > >
> > > Are you using encryption ? I haven't got such errors on my tests (it
> > > might be that my setup is really simple) so far...
> >
> > I can't speak for Helge, but in my case yes - WPA-TKIP.
>
> Same here. WPA-PSK & TKIP.
So, I turned off encryption here and did not get any "invalid Michael
MIC" messages while doing a large apt-get upgrade overnight. I do get
random pauses but nothing else in my dmesg.
Helge, can you confirm disabling encryption makes the reset go away?
--
Bob Copeland %% http://www.bobcopeland.com
On Thursday 27 March 2008, Bob Copeland wrote:
> On Tue, Mar 25, 2008 at 09:11:05PM +0100, Helge Deller wrote:
> > On Tuesday 25 March 2008, Bob Copeland wrote:
> > > On Tue, Mar 25, 2008 at 2:16 PM, Nick Kossifidis <[email protected]> wrote:
> > > > Hello ppl, sory for the delay ;-)
> > > >
> > > > Are you using encryption ? I haven't got such errors on my tests (it
> > > > might be that my setup is really simple) so far...
> > >
> > > I can't speak for Helge, but in my case yes - WPA-TKIP.
> >
> > Same here. WPA-PSK & TKIP.
>
> So, I turned off encryption here and did not get any "invalid Michael
> MIC" messages while doing a large apt-get upgrade overnight. I do get
> random pauses but nothing else in my dmesg.
>
> Helge, can you confirm disabling encryption makes the reset go away?
Yes, I can confirm this.
Without encryption everything worked pretty OK.
I only faced one very small hickup, but ath5k reconnected immediately again, so I don't think this is a real problem:
wlan1: authenticated
wlan1: associate with AP 00:50:18:3b:2b:04
wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x461 status=0 aid=1)
wlan1: associated
wlan1: No ProbeResp from current AP 00:50:18:3b:2b:04 - assume out of range
wlan1: Initial auth_alg=0
wlan1: authenticate with AP 00:50:18:3b:2b:04
wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
wlan1: authenticated
Helge
> > wlan1: RX disassociation from 00:50:18:3b:2b:04 (reason=1)
> > wlan1: disassociated
> > wlan1: deauthenticate(reason=14)
>
> "Message integrity field (MIC) failure" -- doesn't look good.
>
> I've seen a few reports of data corruption with ath5k. Maybe it is
> clobbering its own frames too?
I get exactly this symptom as well, but with the 5424 and the changes
queued for 2.6.26. I had just assumed it was because the 5424
calibration etc. isn't fully understood yet. This appears to be a
5212 though, so perhaps fixing it here would fix it for both.
-Bob
On Tue, Mar 25, 2008 at 2:16 PM, Nick Kossifidis <[email protected]> wrote:
> Hello ppl, sory for the delay ;-)
>
> Are you using encryption ? I haven't got such errors on my tests (it
> might be that my setup is really simple) so far...
I can't speak for Helge, but in my case yes - WPA-TKIP. I can test
tonight without encryption and let you know if it makes a difference.
--
Bob Copeland %% http://www.bobcopeland.com
Hello ppl, sory for the delay ;-)
Are you using encryption ? I haven't got such errors on my tests (it
might be that my setup is really simple) so far...
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
On Sat, Mar 22, 2008 at 11:29:58AM +0100, Helge Deller wrote:
> Around 2-5 minutes later the driver suddenly disconnects and syslog reports the following messages.
> Since then, ath5k will not reconnect any longer to the router.
>
> wlan1: invalid Michael MIC in data frame from 00:15:0c:e1:c0:96
> wlan1: invalid Michael MIC in data frame from 00:15:0c:e1:c0:96
> wlan1: RX disassociation from 00:50:18:3b:2b:04 (reason=1)
> wlan1: disassociated
> wlan1: deauthenticate(reason=14)
"Message integrity field (MIC) failure" -- doesn't look good.
I've seen a few reports of data corruption with ath5k. Maybe it is
clobbering its own frames too?
John
--
John W. Linville
[email protected]
2008/3/27, Helge Deller <[email protected]>:
> On Thursday 27 March 2008, Bob Copeland wrote:
> > On Tue, Mar 25, 2008 at 09:11:05PM +0100, Helge Deller wrote:
> > > On Tuesday 25 March 2008, Bob Copeland wrote:
> > > > On Tue, Mar 25, 2008 at 2:16 PM, Nick Kossifidis <[email protected]> wrote:
> > > > > Hello ppl, sory for the delay ;-)
> > > > >
> > > > > Are you using encryption ? I haven't got such errors on my tests (it
> > > > > might be that my setup is really simple) so far...
> > > >
> > > > I can't speak for Helge, but in my case yes - WPA-TKIP.
> > >
> > > Same here. WPA-PSK & TKIP.
> >
> > So, I turned off encryption here and did not get any "invalid Michael
> > MIC" messages while doing a large apt-get upgrade overnight. I do get
> > random pauses but nothing else in my dmesg.
> >
> > Helge, can you confirm disabling encryption makes the reset go away?
>
>
> Yes, I can confirm this.
>
> Without encryption everything worked pretty OK.
>
> I only faced one very small hickup, but ath5k reconnected immediately again, so I don't think this is a real problem:
>
>
> wlan1: authenticated
> wlan1: associate with AP 00:50:18:3b:2b:04
>
> wlan1: RX AssocResp from 00:50:18:3b:2b:04 (capab=0x461 status=0 aid=1)
> wlan1: associated
> wlan1: No ProbeResp from current AP 00:50:18:3b:2b:04 - assume out of range
>
> wlan1: Initial auth_alg=0
> wlan1: authenticate with AP 00:50:18:3b:2b:04
> wlan1: RX authentication from 00:50:18:3b:2b:04 (alg=0 transaction=2 status=0)
> wlan1: authenticated
>
>
> Helge
>
Since we use software encryption for now we 'll need to trace this
inside base.c or higher on the stack. Anyone with similar problems
with other drivers that use software encryption ???
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
On Tuesday 25 March 2008, Bob Copeland wrote:
> On Tue, Mar 25, 2008 at 2:16 PM, Nick Kossifidis <[email protected]> wrote:
> > Hello ppl, sory for the delay ;-)
> >
> > Are you using encryption ? I haven't got such errors on my tests (it
> > might be that my setup is really simple) so far...
>
> I can't speak for Helge, but in my case yes - WPA-TKIP.
Same here. WPA-PSK & TKIP.
Helge