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: <1321991916.11647.77.camel@wwguy-huron>
Date:	Tue, 22 Nov 2011 11:58:36 -0800
From:	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>
To:	Dave Jones <davej@...hat.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

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


--
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/