linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn fails to associate on 2.6.36-rc2
Date: Mon, 23 Aug 2010 10:14:32 -0400	[thread overview]
Message-ID: <20100823141432.GA29902@infradead.org> (raw)
In-Reply-To: <1282572681.20674.3.camel@wwguy-ubuntu>

On Mon, Aug 23, 2010 at 07:11:21AM -0700, Guy, Wey-Yi wrote:
> it is kind of strange, the connection can stay if you have background
> ping going?

Yes (that's on a kernel up to 2.6.35). Otherwise it drops a lot, up
to ca 2.6.32 it kept working.  See the linux-wireless archives for my
report from back then.

> could you give more description on your problem, band/channel/...
> you also can turn on the debug flag debug=0x43fff to capture the current
> status of iwlwifi. it do require you compile kernel with full debugging
> support.

I don't know what you mean with full kernel debugging.  iwlagn
debugging, mac80211 debugging?  Just tell me the options and I'll run
with it.

  reply	other threads:[~2010-08-23 14:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 11:02 iwlagn fails to associate on 2.6.36-rc2 Christoph Hellwig
2010-08-23 14:11 ` Guy, Wey-Yi
2010-08-23 14:14   ` Christoph Hellwig [this message]
2010-08-23 14:42     ` Guy, Wey-Yi
2010-08-23 16:32       ` Christoph Hellwig
2010-08-23 17:00         ` Guy, Wey-Yi
2010-08-23 19:32           ` Christoph Hellwig
2010-08-23 19:34             ` Guy, Wey-Yi
2010-08-24  1:03           ` lance lassetter
2010-08-24  7:51             ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2010-08-24 22:47 lance lassetter
2010-08-25  7:35 ` Johannes Berg
2010-08-28  0:03   ` lance lassetter

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=20100823141432.GA29902@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.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).