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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1505032340090.17496@pobox.suse.cz>
Date:	Sun, 3 May 2015 23:42:14 +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)

Hi,

so over a past few days, I tried to perform a bisect, but failed as 
expected. The issue is not reliably enough reproducible for me, so I ended 
up with a completely bogus commit.

*However*, now that I have been following the causes and symptoms more 
closely (due to the bisect attempt), I have to confirm that the issue 
happens much more often when the machine is question is physically being 
moved when associated.

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