From: reinette chatre <reinette.chatre@intel.com>
To: drago01 <drago01@gmail.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] [PATCH v2.6.29] iwlwifi: save PCI state before suspend, restore after resume
Date: Mon, 09 Feb 2009 11:29:32 -0800 [thread overview]
Message-ID: <1234207772.11530.164.camel@rc-desk> (raw)
In-Reply-To: <f6ca9fed0902091117k7326e51ag8469887cb1a99d53@mail.gmail.com>
On Mon, 2009-02-09 at 11:17 -0800, drago01 wrote:
> On Tue, Feb 3, 2009 at 7:20 PM, Reinette Chatre
> <reinette.chatre@intel.com> wrote:
> > This is the right thing to do and fixes the following warning:
> > [...]
>
> With 2.6.29-rc4-git1 (which has this patch) I sometimes get:
>
> iwl3945: Wait for START_ALIVE timeout after 2000ms.
> iwl3945 0000:07:00.0: PCI INT A disabled
>
> After resume with results into no working wireless until the module is reloaded.
> I am not sure if this patch is the culprit (have not tried to revert
> it), but that's the only change that might have caused this (with rc3
> it was working fine, it just triggered the warning that this patch
> supposed to solve).
That patch is the culprit. Please see current status at
http://bugzilla.kernel.org/show_bug.cgi?id=12656
Reinette
next prev parent reply other threads:[~2009-02-09 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 18:20 [PATCH v2.6.29] iwlwifi: save PCI state before suspend, restore after resume Reinette Chatre
2009-02-09 19:17 ` [ipw3945-devel] " drago01
2009-02-09 19:29 ` reinette chatre [this message]
2009-02-09 19:31 ` drago01
2009-02-09 19:51 ` Helmut Schaa
2009-02-10 19:08 ` reinette chatre
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=1234207772.11530.164.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=drago01@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
/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).