All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mats Johannesson <spamcan1@abrasax.se>
To: Sujith <m.sujith@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ath9k] 2.6.28-rc7-wl Kernel panic when "iwlist ath0 scan" as root
Date: Sun, 7 Dec 2008 17:29:58 +0100	[thread overview]
Message-ID: <20081207172958.333e88e4@loke.fish.not> (raw)
In-Reply-To: <18747.60039.401701.441103@localhost.localdomain>

On Sun, 7 Dec 2008 20:53:51 +0530 Sujith wrote:
[...]
["This" snipped since I couldn't identify the line/lines doing it]

> This indicates that HT40 has been chosen.
> 
> The problem is this:
> 
> After association, ath9k has to set the appropriate channel width on
> doing a scan and mac80211 comes back to the home channel. Currently
> there is no such means to do that, and this why pinging fails.
> 
> We'll work on a solution, but until then you would have to choose
> HT20 in your AP.

All protocols are affected ping, whatever lies below telnet and http
through lynx was dead as well.

Ok, I'll try this version out a bit first with heavy p2p-transfers. If
it survives I might stick with it (2.6.28-rc6-wl died after awhile)
otherwise I'll go back to my all time favourite 2.6.27-rc5.

Wicd manager seems to keep a static list of APs in the environment I've
already scanned, so the issue is normally of no concern.

/Mats

      reply	other threads:[~2008-12-07 16:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06 10:34 [ath9k] 2.6.28-rc7-wl Kernel panic when "iwlist ath0 scan" as root Mats Johannesson
2008-12-06 12:45 ` Mats Johannesson
2008-12-06 14:25   ` John W. Linville
2008-12-06 15:13     ` Mats Johannesson
2008-12-06 14:52 ` Sujith
2008-12-06 17:05   ` Mats Johannesson
2008-12-06 17:52     ` Sujith
2008-12-06 19:22       ` Mats Johannesson
2008-12-07  3:02         ` Sujith
2008-12-07 14:04           ` Mats Johannesson
2008-12-07 15:23             ` Sujith
2008-12-07 16:29               ` Mats Johannesson [this message]

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=20081207172958.333e88e4@loke.fish.not \
    --to=spamcan1@abrasax.se \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m.sujith@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 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.