linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Florian Klink <flokli@flokli.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: commit 062bee448bd539580ef9f64efe50fdfe04eeb103 broke my iwlagn 5100
Date: Wed, 14 Jul 2010 08:28:48 -0700	[thread overview]
Message-ID: <1279121328.19725.27.camel@wwguy-ubuntu> (raw)
In-Reply-To: <e5d3a4df03d6582ddc18af249ed3a2f2@imap.flokli.de>

Hi Florian,

On Wed, 2010-07-14 at 03:06 -0700, Florian Klink wrote:
> Thanks ;-)
> 
> On Wed, 14 Jul 2010 12:00:55 +0200, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > [correct wey-yi's address, remove reinette]
> > 
> > On Wed, 2010-07-14 at 11:33 +0200, Florian Klink wrote:
> >> Hi,
> >>
> >> I hope I'm writing to the right addresses, this is my first kernel bug
> >> report :-)
> >>
> >> I regulary build linus' tree from git. One day, my wireless card was
> >> unable to connect to the access point. dmesg showed something like this:
> >>
> >> [  122.290949] wlan0: direct probe to 00:15:0c:xx:xx:xx (try 1)
> >> [  122.490158] wlan0: direct probe to 00:15:0c:xx:xx:xx (try 2)
> >> [  122.690057] wlan0: direct probe to 00:15:0c:xx:xx:xx (try 3)
> >> [  122.890031] wlan0: direct probe to 00:15:0c:xx:xx:xx timed out
> >>
> >> At first, I thought is was some link quality problem and tried it next
> >> to the access point, but it still didn't work.
> >> I booted another (older) kernel and with this one, the card was able to
> >> connect without any problems.
> >>
> >> I bisected the problem and came to commit
> >> 062bee448bd539580ef9f64efe50fdfe04eeb103
> >> iwlwifi: set TX_CMD_FLAG_PROT_REQUIRE_MSK in tx_flag
> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=062bee448bd539580ef9f64efe50fdfe04eeb103
> >>
> >> My wireless card is a Intel Corporation Wireless WiFi Link 5100.
> >>
> >> Will provide more info if needed.
> >>
Could you please load the iwlagn module with module parameter
debug=0x43fff and forward us the dmesg log

Thanks
Wey
> 


  reply	other threads:[~2010-07-14 15:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14  9:33 commit 062bee448bd539580ef9f64efe50fdfe04eeb103 broke my iwlagn 5100 Florian Klink
2010-07-14 10:00 ` Johannes Berg
2010-07-14 10:06   ` Florian Klink
2010-07-14 15:28     ` Guy, Wey-Yi [this message]
2010-07-14 16:36       ` Florian Klink
2010-07-14 17:27         ` Guy, Wey-Yi
2010-07-14 17:36           ` Johannes Berg
2010-07-14 17:44             ` Guy, Wey-Yi
  -- strict thread matches above, loose matches on Subject: below --
2010-07-16 23:22 Florian Klink
2010-07-16 23:49 ` Guy, Wey-Yi
2010-07-16 23:48   ` Florian Klink

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=1279121328.19725.27.camel@wwguy-ubuntu \
    --to=wey-yi.w.guy@intel.com \
    --cc=flokli@flokli.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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 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).