linux-kernel - Re: iwlwifi getting stuck with current Linus' tree (646da63172)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LNX.2.00.1505071052290.8186@pobox.suse.cz>
Date:	Thu, 7 May 2015 10:54:52 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	"Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>
cc:	"piotr.karbowski@...il.com" <piotr.karbowski@...il.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"Berg, Johannes" <johannes.berg@...el.com>
Subject: Re: iwlwifi getting stuck with current Linus' tree (646da63172)

On Mon, 4 May 2015, Grumbach, Emmanuel wrote:

> Sorry, my bad. I lost context here... So I really don't know what to 
> say. I can't see any iwlwifi commit that could be causing this, OTOH, 
> bisection didn't bring any results. You can try to unregister the device 
> from PCI and then to rescan. It worked for some people. Other than that, 
> I can't do much. Did you update your BIOS before you started to see this 
> failure?

Well, this kept getting worse and worse. Newer kernels were much "better" 
provoking the HW crashes, but a few days ago I started seeing it even with 
very old kernels, which used to be rock stable.

I first ruled out a firmware update to be the cause.

So I dismanlted the notebook and replaced the wifi chip with another one 
(also driven by iwlwifi), and no failure after 2 days so far.

So it might turn out that this particular one was a red herring. If it 
happens again even with the replaced chip, I'll report back. Sorry for the 
noise.

-- 
Jiri Kosina
SUSE Labs
--
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/