linux-wireless.vger.kernel.org archive mirror
 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: Sat, 6 Dec 2008 20:22:37 +0100	[thread overview]
Message-ID: <20081206202237.578b3783@loke.fish.not> (raw)
In-Reply-To: <18746.48068.593834.660064@localhost.localdomain>

On Sat, 6 Dec 2008 23:22:04 +0530 Sujith wrote:
> Mats Johannesson wrote:
> > It fixes the kernel panic with root "iwlist ath0 scan" but after
> > that the network dies without a sign of any kind (iwlist, ifconfig
> > etc is normal, nothing in logs). Tried several times. Boot -> ping
> > local and remote machine OK -> "iwlist ath0 scan" -> ping
> > nonfunctional: 'no route to host' or some such message.
> > 
> 
> Ok, thanks for testing.
> 
> Can you check if this patch makes the connection stable ?
> Please apply on top of the earlier patch.

Sorry to say, no change. After root scan telnet gives "no route to
host" and ping just reports 100% packet loss. But iwconfig keeps
updating its info regarding link quality and signal strength, like:
Link Quality=82/100  Signal level:-42 dBm

/Mats

  reply	other threads:[~2008-12-06 19:22 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 [this message]
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

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=20081206202237.578b3783@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 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).