All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: Help with debugging intermittent crash on resume from hibernation
Date: Fri, 17 Apr 2015 21:13:14 -0700	[thread overview]
Message-ID: <87bnimhy5h.fsf@vostro.rath.org> (raw)
In-Reply-To: <1429329703.4034.4.camel@gmail.com> (Mike Galbraith's message of "Sat, 18 Apr 2015 06:01:43 +0200")

On Apr 17 2015, Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
> On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
>> 
>> Is there anything I can do to help debug this issue?
>
> You could try to bisect it, but judging from the problem description, 
> that could be more like a career than a troubleshooting session.

Furthermore, I have yet to find a kernel version that does *not* exhibit
the problem (I went back to 3.14).

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Nikolaus Rath <Nikolaus@rath.org>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: Help with debugging intermittent crash on resume from hibernation
Date: Fri, 17 Apr 2015 21:13:14 -0700	[thread overview]
Message-ID: <87bnimhy5h.fsf@vostro.rath.org> (raw)
In-Reply-To: <1429329703.4034.4.camel@gmail.com> (Mike Galbraith's message of "Sat, 18 Apr 2015 06:01:43 +0200")

On Apr 17 2015, Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
> On Fri, 2015-04-17 at 20:15 -0700, Nikolaus Rath wrote:
>> 
>> Is there anything I can do to help debug this issue?
>
> You could try to bisect it, but judging from the problem description, 
> that could be more like a career than a troubleshooting session.

Furthermore, I have yet to find a kernel version that does *not* exhibit
the problem (I went back to 3.14).

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

  reply	other threads:[~2015-04-18  5:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14  3:02 Help with debugging intermittent crash on resume from hibernation Nikolaus Rath
2015-03-20  3:21 ` Nikolaus Rath
2015-03-20  3:21   ` Nikolaus Rath
2015-03-20  3:57   ` Mike Galbraith
2015-04-18  3:15     ` Nikolaus Rath
2015-04-18  3:15       ` Nikolaus Rath
2015-04-18  4:01       ` Mike Galbraith
2015-04-18  4:13         ` Nikolaus Rath [this message]
2015-04-18  4:13           ` Nikolaus Rath
2015-04-18  4:45           ` Mike Galbraith

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=87bnimhy5h.fsf@vostro.rath.org \
    --to=nikolaus@rath.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=umgwanakikbuti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.