From: <samuel@sortiz.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: 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 00:41:59 +0100 [thread overview]
Message-ID: <d7a260e8d188b785d0d2be743c8c5461@localhost> (raw)
In-Reply-To: <20090122183448.GC3646@tuxdriver.com>
On Thu, 22 Jan 2009 13:34:48 -0500, "John W. Linville"
<linville@tuxdriver.com> wrote:
> On Thu, Jan 22, 2009 at 08:26:14PM +0200, Kalle Valo wrote:
>> Hello,
>>
>> I upgraded to the latest wireless-testing and my iwl3945 is now
>> broken. It can associate but no data is transfered after that. Tried
>> with open and wep modes. With dhcp I cannot get ip and with static ip
>> ping to the gateway doesn't work.
>>
>> Any hints?
>
> Lots of iwlwifi stuff merged yesterday...
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.
Cheers,
Samuel.
>
> Chatre, Reinette (1):
> iwl3945: add debugging for wrong command queue
>
> Helmut Schaa (2):
> iwl3945: fix some warnings when compiled without debug
> iwlagn: fix hw-rfkill while the interface is down
>
> Jay Sternberg (4):
> iwlwifi: correct Kconfig to prevent following entries from not
> indenting
> iwlwifi: remove static from 5000 structures
> iwlwifi: add recognition of Intel WiFi Link 6000 and 6050 Series
> iwlwifi: add recognition of Intel WiFi Link 100 Series
>
> Reinette Chatre (1):
> iwlwifi: return NETDEV_TX_OK from _tx ops
>
> Samuel Ortiz (3):
> iwl3945: Use iwl_txq_update_write_ptr
> iwlwifi: Add TFD library operations
> iwl3945: Use iwl-hcmd host command routines
>
> Winkler, Tomas (6):
> iwlwifi: make iwl-power.c more readable
> iwlwifi: fix iwl_mac_set_key and iwl3945_mac_set_key
> iwlwifi: kill iwl3945_scan_cancel and iwl3945_scan_cancel_timeout
> iwlwifi: kill scan39
> iwlwifi: remove unused or twice defined members in iwl_priv
> iwlwifi: eliminate power_data_39.
next prev parent reply other threads:[~2009-01-22 23: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 [this message]
2009-01-22 23:55 ` Larry Finger
2009-01-23 0:42 ` samuel
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=d7a260e8d188b785d0d2be743c8c5461@localhost \
--to=samuel@sortiz.org \
--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).