From: Carlos Alberto Lopez Perez <clopez@igalia.com>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 3.1+ iwlwifi lockup
Date: Sat, 26 Nov 2011 03:22:43 +0100 [thread overview]
Message-ID: <4ED04D73.7010703@igalia.com> (raw)
In-Reply-To: <1320179254.31823.130.camel@wwguy-huron>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On 01/11/11 21:27, Guy, Wey-Yi wrote:
> Any more information to help us understand how to re-produce the issue?
> without more data, it is really hard to root cause and fix it.
>
> Thanks
> Wey
This bug (or a related one) triggers on my laptop (Dell Latitude E6420)
since I switched from Kernel 3.0-debian to 3.1-debian (AMD64). I believe
that the bugs happens after waking up from the suspension-to-RAM.
Since I switched to 3.1 Kernel after waking up from suspension my laptop
freezes very often and I need to hard reboot it, this is really
annoying. This wasn't happening with 3.0 Kernel and I believe that
iwlagn is the cause.
I have an Intel Advanced-N 6205 (rev 34) wireless card.
The other day I was able to get the following kernel errors after waking
up from suspension with this 3.1 kernel[1]
This 3.1 Kernel is the Debian precompiled one (linux-image-3.1.0-1-amd64)
$ uname -r
3.1.0-1-amd64
[1] Find here the dmesg part that comes after the wakeup from suspension:
http://people.igalia.com/clopez/iwlagn_dmesg_3.1.log.txt
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2011-11-26 2:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 14:34 3.1+ iwlwifi lockup Dave Jones
2011-10-31 15:44 ` Guy, Wey-Yi
2011-11-01 20:27 ` Guy, Wey-Yi
2011-11-01 22:08 ` Dave Jones
2011-11-26 2:22 ` Carlos Alberto Lopez Perez [this message]
2011-11-22 20:15 ` wwguy
2011-11-22 20:47 ` Dave Jones
2011-11-22 19:58 ` Guy, Wey-Yi
2011-11-22 22:54 ` Dave Jones
2011-11-22 22:49 ` wwguy
2011-11-23 2:45 ` Dave Jones
2011-11-23 2:29 ` Guy, Wey-Yi
2011-11-23 3:34 ` Dave Jones
2011-11-23 2:56 ` Guy, Wey-Yi
2011-11-23 4:17 ` Dave Jones
2011-11-24 15:00 ` Emmanuel Grumbach
2011-11-25 12:11 ` Emmanuel Grumbach
2011-11-22 20:16 ` wwguy
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=4ED04D73.7010703@igalia.com \
--to=clopez@igalia.com \
--cc=davej@redhat.com \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@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).