public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "jkosina@suse.cz" <jkosina@suse.cz>
Cc: "piotr.karbowski@gmail.com" <piotr.karbowski@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>,
	"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: iwlwifi getting stuck with current Linus' tree (646da63172)
Date: Mon, 4 May 2015 04:32:06 +0000	[thread overview]
Message-ID: <1430713926.3388.1.camel@intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1505032340090.17496@pobox.suse.cz>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 821 bytes --]

On Sun, 2015-05-03 at 23:42 +0200, Jiri Kosina wrote:
> 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.
> 

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.

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2015-05-04  4:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 20:42 iwlwifi getting stuck with current Linus' tree (646da63172) Jiri Kosina
2015-04-23  4:47 ` Grumbach, Emmanuel
2015-04-23  8:15   ` Jiri Kosina
2015-04-23  9:12     ` Grumbach, Emmanuel
2015-04-23  9:15       ` Jiri Kosina
2015-04-23 12:48         ` Piotr Karbowski
2015-04-23 18:10           ` Grumbach, Emmanuel
2015-05-03 21:42             ` Jiri Kosina
2015-05-04  4:32               ` Grumbach, Emmanuel [this message]
2015-05-04  6:55                 ` Jiri Kosina
2015-05-04  7:02                   ` Grumbach, Emmanuel
2015-05-07  8:54                     ` Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1430713926.3388.1.camel@intel.com \
    --to=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=jkosina@suse.cz \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=piotr.karbowski@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox