From: Jon Wikne <Jon.Wikne@cern.ch>
To: linux-wireless@vger.kernel.org
Cc: Mohammed Shafi <shafi.wireless@gmail.com>, Jon Wikne <Jon.Wikne@cern.ch>
Subject: Re: Mysterious hangs - cfg80211 - ath9k
Date: Tue, 19 Jun 2012 20:52:28 +0200 [thread overview]
Message-ID: <4FE0CA6C.3080002@cern.ch> (raw)
In-Reply-To: <CAD2nsn1U0UHjrDp7vh7rfvTP=BLB3FA+zLV9sgt1_T7gVvAYgg@mail.gmail.com>
On 06/19/2012 11:39 AM, Mohammed Shafi wrote:
> On Tue, Jun 19, 2012 at 1:34 PM, Jon Wikne<Jon.Wikne@cern.ch> wrote:
>> Hi List,
>>
>> I am experiencing a puzzling problem with WLAN on a Toshiba Qosmio
>> F750 laptop, running CERN SLC 5.8 (mostly identical to RHEL 5.8),
>> but with kernel 2.6.39.4. (The kernel that came with the distro did
>> not work properly with WLAN on this machine at all.)
>
> please quickly try
> http://linuxwireless.org/en/users/Download#Where_to_download_bleeding_edge
I tried to install compat-wireless-2012-05-10. It worked for 4½ hours,
then same problem.
Maybe there is something wrong with my understanding here, but I do not
see why the "cfg80211: Calling CRDA to update world regulatory domain"
should occur hours after the connection has been established, and what
triggers it, apparently at random....
> or the latest wireless testing tree
> http://linuxwireless.org/en/developers/Documentation/git-guide#Cloning_latest_wireless-testing
Is there a reason to believe it could make a difference if I try
this too?
Regards,
-- Jon Wikne
next prev parent reply other threads:[~2012-06-19 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 8:04 Mysterious hangs - cfg80211 - ath9k Jon Wikne
2012-06-19 9:39 ` Mohammed Shafi
2012-06-19 18:52 ` Jon Wikne [this message]
2012-06-28 14:03 ` Jon Wikne
2012-06-28 14:22 ` Mohammed Shafi
2012-06-28 15:42 ` Jon Wikne
2012-06-29 6:19 ` Mohammed Shafi
2012-10-10 9:38 ` Jon Wikne
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=4FE0CA6C.3080002@cern.ch \
--to=jon.wikne@cern.ch \
--cc=linux-wireless@vger.kernel.org \
--cc=shafi.wireless@gmail.com \
/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 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).