From: Zhu Yi <yi.zhu@intel.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Jiri Slaby <jirislaby@gmail.com>, Michal Hocko <mhocko@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: BUG: scheduling while atomic: iwl3945/0/3680/0x00000002 during resume from suspend
Date: Tue, 11 Nov 2008 11:54:15 +0800 [thread overview]
Message-ID: <1226375655.2604.330.camel@debian.sh.intel.com> (raw)
In-Reply-To: <200811101049.01759.borntraeger@de.ibm.com>
On Mon, 2008-11-10 at 17:49 +0800, Christian Borntraeger wrote:
> Am Montag, 10. November 2008 schrieb Zhu Yi:
> > On Mon, 2008-11-10 at 01:42 +0800, Jiri Slaby wrote:
> > > I think the same as:
> > > http://marc.info/?l=linux-wireless&m=122254514501379&w=2
> >
> > Yup. Try this fix.
> >
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commit;h=605b6cd038c5002f8dcbd3695aa934a130257af4
>
> I got a similar one on
> 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN
> [Kedron] Network Connection (rev 61)
>
> with a pretty decent git: 2.6.28-rc3-00255-g6209344.
> This version contains the fix for iwlwifi, but I still see this bug.
I see. This is a different bug. I'll comment on the previous thread.
Thanks,
-yi
next prev parent reply other threads:[~2008-11-11 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 14:14 BUG: scheduling while atomic: iwl3945/0/3680/0x00000002 during resume from suspend Michal Hocko
2008-11-09 17:42 ` Jiri Slaby
2008-11-10 1:12 ` Zhu Yi
2008-11-10 9:49 ` Christian Borntraeger
2008-11-11 3:54 ` Zhu Yi [this message]
2008-11-10 17:18 ` Michal Hocko
2008-11-20 17:40 ` Michal Hocko
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=1226375655.2604.330.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=borntraeger@de.ibm.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=reinette.chatre@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).