From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Dave Jones <davej@redhat.com>
Cc: 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: Tue, 22 Nov 2011 11:58:36 -0800 [thread overview]
Message-ID: <1321991916.11647.77.camel@wwguy-huron> (raw)
In-Reply-To: <20111122204741.GA3764@redhat.com>
Hi Dave,
Not sure what happens, feel like memory corruption but not sure. the
contain of the command is totally bogus.
Could you please test and send update, it is part of "3.2+rc2+
Regressions from 3.0 and 3.1" reports
Thanks
Wey
On Tue, 2011-11-22 at 12:47 -0800, Dave Jones wrote:
> On Tue, Nov 22, 2011 at 12:15:02PM -0800, wwguy wrote:
> > Hi Dave,
> >
> > Sorry for taking so long.
> > it is a bogus command from the firmware which driver try to process it
> > and cause problem. I am not sure how it happen. But could you please try
> > the patch I attach here.
> >
> > For now I am just ignore the command, but not sure it is good enough,
> > might has to reload the firmware, but not sure.
>
> I can try the patch. Though FYI, I've not seen this bug again since I reported it.
>
> > Do you have a bugzilla# I can reference to?
>
> no.
>
> Dave
next prev parent reply other threads:[~2011-11-22 20:54 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
2011-11-22 20:15 ` wwguy
2011-11-22 20:47 ` Dave Jones
2011-11-22 19:58 ` Guy, Wey-Yi [this message]
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=1321991916.11647.77.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=davej@redhat.com \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).