linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <samuel@sortiz.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Kalle Valo <kalle.valo@iki.fi>,
	linux-wireless@vger.kernel.org
Subject: Re: iwl3945 regression: associates but no data is transfered
Date: Fri, 23 Jan 2009 01:42:15 +0100	[thread overview]
Message-ID: <a0ea5baee379a280e5a06e81facbb631@localhost> (raw)
In-Reply-To: <4979077B.8090804@lwfinger.net>


On Thu, 22 Jan 2009 17:55:39 -0600, Larry Finger

<Larry.Finger@lwfinger.net>

wrote:

> samuel@sortiz.org wrote:

> 

>> The bad commit seems to be e32b1b9a33759e8a83ac566c4c43f23ed5d6343b,

>> which

>> is not iwlwifi related.

>> Even though it's an mlme commit, it doesnt seem to affect other drivers

>> (at

>> least b43 and ath5k).

>> I'll come up soon with a proper fix, but for now iwl3945 users should

>> revert that commit locally.

> 

> Something between 2.6.29-rc1 and -rc2 killed b43 and p54usb on my WPA2

> network. My rtl8187

> devices work fine.

> 

> I'm in the process of bisecting right now. Only 1500 commits to go.

Have you tried reverting that commit ?

I actually found that it does break ath5k as well...



Cheers,

Samuel.



  reply	other threads:[~2009-01-23  0:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 18:26 iwl3945 regression: associates but no data is transfered Kalle Valo
2009-01-22 18:34 ` John W. Linville
2009-01-22 23:41   ` samuel
2009-01-22 23:55     ` Larry Finger
2009-01-23  0:42       ` samuel [this message]
2009-01-23  1:06         ` Larry Finger
2009-01-23  5:32       ` Harvey Harrison
2009-01-23  0:07     ` Sedat Dilek
2009-01-23  1:20     ` Sedat Dilek
2009-01-22 19:41 ` Sedat Dilek

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=a0ea5baee379a280e5a06e81facbb631@localhost \
    --to=samuel@sortiz.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).