[ath9k-devel] ath9k constantly drops network connection

[Luis R. Rodriguez <lrodriguez@atheros.com>]

On Sat, Sep 20, 2008 at 01:31:48PM -0700, Partha Bagchi wrote:
> On Sat, Sep 20, 2008 at 3:57 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > On Sat, Sep 20, 2008 at 6:07 AM, Partha Bagchi <partha1b@gmail.com> wrote:
> >> --snip---
> >>>
> >>> Currently the network has been up for 24 minutes. I will let you know
> >>> how long it will last.
> >>>
> >>> Thanks again.
> >>>
> >>> Partha
> >>>
> >>
> >> The connection died after 54 minutes. But I was able to restore with
> >> NetworkManager.
> >>
> >> BTW, why all the ForceXPAon: 0 messages?
> >
> > All I can see right now is we are setting this for our newer chipsets
> > during reset, it should only be printed during debug but right now it
> > *always* prints, so we'll fix that. Since it *always* happens it
> > shouldn't be bad, but I don't have documentation on what this is right
> > now so I can't tell you what it is for sure.
> >
> > Can you do me a favor of pasting the output of:
> >
> > sudo dmesg -c > /dev/null
> > sudo rmmod ath9k
> > sudo modprobe ath9k
> > sudo dmesg -c
> >
> > Also, what type of box do you have (standard PC, MacBook, MacBook Pro), etc?
> >
> > I have to say that since this is on 2.6.26 we haven't tested this
> > thoroughly but will try to help you get it working right anyway.
> >
> >  Luis
> >
> 
> Hi Luis,
> 
> In reply to your questions, I have a Sony VGN-FW139E laptop. Please
> let me know if you want the output of
> lspci.
> 
> Here is the output you asked for.
> -------
> [root at Bordeaux ~]# dmesg -c > /dev/null
> [root at Bordeaux ~]# rmmod ath9k
> [root at Bordeaux ~]# modprobe ath9k
> [root at Bordeaux ~]# dmesg
> ACPI: PCI interrupt for device 0000:06:00.0 disabled
> ath9k: driver unloaded
> ath9k: 0.1
> ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 19 (level, low) -> IRQ 19
> PCI: Setting latency timer of device 0000:06:00.0 to 64
> phy4: Selected rate control algorithm 'ath9k_rate_control'
> Registered led device: ath9k-phy4:radio
> Registered led device: ath9k-phy4:assoc
> Registered led device: ath9k-phy4:tx
> Registered led device: ath9k-phy4:rx
> phy4: Atheros 9280: mem=0xf8b20000, irq=19

OK yea this is one of our newer chipsets :)
Is this a laptop? What model? Where you buy it?

> udev: renamed network interface wlan0 to wlan1
> ForceXPAon: 0
> ADDRCONF(NETDEV_UP): wlan1: link is not ready
> ForceXPAon: 0
> ForceXPAon: 0
> ForceXPAon: 0
> ForceXPAon: 0
> wlan1: authenticate with AP 00:14:bf:85:52:fd
> wlan1: authenticated
> wlan1: associate with AP 00:14:bf:85:52:fd
> wlan1: RX AssocResp from 00:14:bf:85:52:fd (capab=0x401 status=0 aid=1)
> wlan1: associated
> ForceXPAon: 0
> ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
> wlan1: disassociating by local choice (reason=3)
> [root at Bordeaux ~]#
> ------
> 
> I will be happy to use the 2.6.27 kernel from rawhide if it will help
> my connection.

Yeah sure, I'd like to help you on 26 but 27 should work better
as that is where we are doing most of our testing. Keep in mind
the group key patch still needs to be applied.

  Luis