[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1505040853590.17496@pobox.suse.cz>
Date: Mon, 4 May 2015 08:55:06 +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:
> > 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.
> >
>
> I am doing this all the time and I don't hit your problem. Without any
> logs I don't see how I can help here. Please try to catch logs of the
> crash. Thanks.
I have provided them in the very first e-mail to this thread; see
https://lkml.org/lkml/2015/4/22/601
If there is any way how to obtain more verbose / useful logs, please let
me know, I'll be happy to do that.
--
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/
Powered by blists - more mailing lists