linux-kernel - Re: 3.1+ iwlwifi lockup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111101220845.GA16080@redhat.com>
Date:	Tue, 1 Nov 2011 18:08:45 -0400
From:	Dave Jones <davej@...hat.com>
To:	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: 3.1+ iwlwifi lockup

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/