From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k constantly drops network connection
Date: Sun, 21 Sep 2008 23:52:12 -0700 [thread overview]
Message-ID: <20080922065212.GC19580@tesla> (raw)
In-Reply-To: <e14212e0809201656j7b852517l9b2ce00551e89759@mail.gmail.com>
On Sat, Sep 20, 2008 at 04:56:30PM -0700, Partha Bagchi wrote:
> On Sat, Sep 20, 2008 at 7:48 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > On Sat, Sep 20, 2008 at 4:38 PM, Partha Bagchi <partha1b@gmail.com> wrote:
> >> On Sat, Sep 20, 2008 at 6:54 PM, Luis R. Rodriguez
> >> <lrodriguez@atheros.com> wrote:
> >>> On Sat, Sep 20, 2008 at 2:19 PM, Partha Bagchi <partha1b@gmail.com> wrote:
> >>>
> >>>> Don't forget, I already copied the ath9k subdrirectory from the latest
> >>>> tree and applied the patch and compiled it. Is there anything
> >>>> intrinsic about the 2.6.27 kernel that will help the connection?
> >>>
> >>> You get a new shiny mac80211 with all the patches that went in for it.
> >>> We can't add the new mac80211 to compat-wireless-old as you did with
> >>> ath9k as 2.6.27 had the struct net_device change quite a lot (new TX
> >>> multiqueue changes) and backporting this was a major pain in the ass.
> >>> Hence we have compat-wireless-old for <= 2.6.26 and compat-wireless
> >>> for >= 2.6.27.
> >>>
> >>> Still, if someone wants to go over all 2.6.27 mac80211 patches and
> >>> apply them to compat-wireless-old except for the TX MQ related ones,
> >>> that should work, but you'll have to find someone with enough
> >>> motivation to do it.
> >>>
> >>> Luis
> >>>
> >>
> >> Thanks. I see your point. I am not sure I can do the job of backporting.
> >>
> >> I will investigate updating the kernel from rawhide.
> >>
> >> One additional question. I seem to be dropping connection much faster
> >> (every 5 or 10 minutes) in the evening compared to the the morning and
> >> afternoon (every 30 to 40 minutes). Any theories on this?
> >
> > More noise when people get home perhaps, depends on where you live. We
> > haven't yet added ANI which should help with that, but work is
> > underway for it. ANI helps with adjusting the hardware due to noise,
> > it helps with reception.
> >
> > Luis
> >
>
> Thanks. Now I am having the weirdest thing happening. Suddenly, I am
> getting these messages (while my connection is up and running fine!):
> -------
> Sep 20 19:53:11 Bordeaux kernel: ForceXPAon: 0
> Sep 20 19:53:11 Bordeaux kernel: ForceXPAon: 0
> Sep 20 19:53:11 Bordeaux kernel: ForceXPAon: 0
> Sep 20 19:53:11 Bordeaux kernel: ForceXPAon: 0
Ignore these.
> Sep 20 19:53:12 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:53:29 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:53:45 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:53:58 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:54:09 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:54:17 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:54:32 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:54:42 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:54:54 Bordeaux dhclient: DHCPREQUEST on wlan1 to 192.168.1.1 port 67
> Sep 20 19:55:11 Bordeaux kernel: ForceXPAon: 0
Are you on 2.6.27-rc7? You'll still need the group key patch, which was
not merged in for rc7.
Luis
next prev parent reply other threads:[~2008-09-22 6:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 10:05 [ath9k-devel] ath9k constantly drops network connection Partha Bagchi
2008-09-17 19:10 ` Luis R. Rodriguez
2008-09-17 23:08 ` Partha Bagchi
2008-09-17 23:20 ` Luis R. Rodriguez
2008-09-18 10:04 ` Partha Bagchi
2008-09-18 10:09 ` Luis R. Rodriguez
2008-09-18 10:45 ` Partha Bagchi
2008-09-18 11:02 ` Mats Johannesson
2008-09-18 23:01 ` Partha Bagchi
2008-09-19 9:59 ` Partha Bagchi
2008-09-19 17:43 ` Luis R. Rodriguez
2008-09-19 22:30 ` Partha Bagchi
2008-09-19 23:49 ` Luis R. Rodriguez
2008-09-20 12:36 ` Partha Bagchi
2008-09-20 13:07 ` Partha Bagchi
2008-09-20 19:57 ` Luis R. Rodriguez
2008-09-20 20:31 ` Partha Bagchi
2008-09-20 20:54 ` Luis R. Rodriguez
2008-09-20 21:19 ` Partha Bagchi
2008-09-20 22:54 ` Luis R. Rodriguez
2008-09-20 23:38 ` Partha Bagchi
2008-09-20 23:48 ` Luis R. Rodriguez
2008-09-20 23:56 ` Partha Bagchi
2008-09-22 6:52 ` Luis R. Rodriguez [this message]
2008-09-18 2:46 ` Mats Johannesson
2008-09-18 8:36 ` Mats Johannesson
2008-09-18 8:46 ` Luis R. Rodriguez
2008-09-18 8:46 ` Luis R. Rodriguez
2008-09-18 9:00 ` Steven Noonan
2008-09-18 9:00 ` Steven Noonan
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=20080922065212.GC19580@tesla \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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.