linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
	yi.zhu@intel.com, reinette.chatre@intel.com,
	linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
	Jan-Espen Pettersen <sigsegv@radiotube.org>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: new: regression iwl3945/mac80211 endless after suspend associate/deassociate loop
Date: Tue, 2 Sep 2008 16:20:48 +0300	[thread overview]
Message-ID: <20080902132045.GD19172@google.com> (raw)
In-Reply-To: <20080901160658.GA11063@google.com>

On Mon, Sep 01, 2008 at 07:06:58PM +0300, Michael S. Tsirkin wrote:
> Starting with 2.6.27-rc5, my T60p sometimes fails to associate
> with an access point after suspend to ram/resume.
> 
> This does not seem to ever happen on 2.6.27-rc4.
> 
> When this happens, I observe the following messages in dmesg:
> (AP mac masked out with XX):
> 
> ...
>  
> Reverting 8ab65b03b7893da4a49009e7e356e36e27b0c407 seems to make
> the card associate properly after suspend, for me.

FYI I created a bugzilla entry to track this:
http://bugzilla.kernel.org/show_bug.cgi?id=11476

-- 
MST




      parent reply	other threads:[~2008-09-02 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 16:07 new: regression iwl3945/mac80211 endless after suspend associate/deassociate loop Michael S. Tsirkin
2008-09-02  1:38 ` Zhu Yi
2008-09-02  6:10   ` Johannes Berg
2008-09-02 13:04     ` Michael S. Tsirkin
2008-09-02 13:30       ` Dan Williams
2008-09-02 14:58         ` Michael S. Tsirkin
2008-09-02 15:06           ` John W. Linville
2008-09-02 20:53             ` Michael S. Tsirkin
2008-09-02 15:10           ` Dan Williams
2008-09-02 17:24             ` Jouni Malinen
2008-09-02 20:50               ` Michael S. Tsirkin
2008-09-03 12:07                 ` Jouni Malinen
2008-09-02 13:18   ` Michael S. Tsirkin
2008-09-02 13:20 ` Michael S. Tsirkin [this message]

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=20080902132045.GD19172@google.com \
    --to=m.s.tsirkin@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@intel.com \
    --cc=rjw@sisk.pl \
    --cc=sigsegv@radiotube.org \
    --cc=yi.zhu@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).