Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751663AbbECVmY (ORCPT ); Sun, 3 May 2015 17:42:24 -0400 Received: from cantor2.suse.de ([195.135.220.15]:46684 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751416AbbECVmQ (ORCPT ); Sun, 3 May 2015 17:42:16 -0400 Date: Sun, 3 May 2015 23:42:14 +0200 (CEST) From: Jiri Kosina To: "Grumbach, Emmanuel" cc: "piotr.karbowski@gmail.com" , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "ilw@linux.intel.com" , "Berg, Johannes" Subject: Re: iwlwifi getting stuck with current Linus' tree (646da63172) In-Reply-To: <1429812611.23202.4.camel@intel.com> Message-ID: References: <1429764440.4084.5.camel@intel.com> <1429780366.11859.1.camel@intel.com> <1429812611.23202.4.camel@intel.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 698 Lines: 19 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/