linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.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, 1 Nov 2011 18:08:45 -0400	[thread overview]
Message-ID: <20111101220845.GA16080@redhat.com> (raw)
In-Reply-To: <1320179254.31823.130.camel@wwguy-huron>

On Tue, Nov 01, 2011 at 01:27:34PM -0700, Guy, Wey-Yi wrote:
 > Dave,
 > 
 > On Mon, 2011-10-31 at 07:34 -0700, Dave Jones wrote:
 > > I just got this trace, and a driver lockup that caused me to have to
 > > unload & reload the iwlwifi module to get networking back.
 > > hardware is..
 > > 04:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
 > > 
 > > This is new as of 3.1+  (This kernel was Linus' tree as of last night)
 > > 
 > >         
 > 
 > 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

Wasn't doing anything special.  ssh, firefox, git clones.

	Dave


  reply	other threads:[~2011-11-01 22:08 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 [this message]
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
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=20111101220845.GA16080@redhat.com \
    --to=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).