linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janek Kozicki <janek.listy.mailowe@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-kernel@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: 3.16 crashes on resume from Suspend-To-disk
Date: Wed, 13 Aug 2014 11:43:40 +0200	[thread overview]
Message-ID: <20140813114340.147b59e1@absurd> (raw)
In-Reply-To: <140743930.1Lg0eFFrXs@vostro.rjw.lan>

Rafael J. Wysocki said:     (by the date of Wed, 06 Aug 2014 01:15 +0200)

> Why don't you file a bug at bugzilla.kernel.org against hibernation/suspend and
> put that information into it?

I just did: https://bugzilla.kernel.org/show_bug.cgi?id=82291

I hope you can help me with that, if there's any more debugging to do please let me know.

best regards
Janek Kozicki

  parent reply	other threads:[~2014-08-13  9:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  1:51 3.16-rcX crashes on resume from Suspend-To-RAM Markus Gutschke
2014-07-17  6:50 ` Markus Gutschke
2014-07-17  8:58   ` Zhang Rui
2014-07-17 17:27     ` Markus Gutschke
2014-07-22  0:22       ` Zhang Rui
2014-07-26 15:52         ` Markus Gutschke
2014-08-04 14:16           ` Pavel Machek
2014-08-04 16:06             ` Markus Gutschke
2014-08-05  1:30               ` Rafael J. Wysocki
2014-08-05  9:58                 ` 3.16 crashes on resume from Suspend-To-disk Janek Kozicki
2014-08-05 17:07                   ` Janek Kozicki
2014-08-05 23:15                     ` Rafael J. Wysocki
2014-08-07  9:34                       ` Takashi Iwai
2014-08-08 16:25                         ` 3.16 crashes on resume from Suspend-To-disk, Intel pci_bus problem? Janek Kozicki
2014-08-08 16:29                           ` Janek Kozicki
2014-08-09  8:59                           ` Takashi Iwai
2014-08-09  9:56                             ` Janek Kozicki
2014-08-09 12:13                               ` Janek Kozicki
2014-08-13  9:43                       ` Janek Kozicki [this message]
2014-08-06 12:25                   ` 3.16 crashes on resume from Suspend-To-disk Pavel Machek
2014-08-07 17:54                     ` Janek Kozicki
2014-08-05  2:44               ` 3.16-rcX crashes on resume from Suspend-To-RAM Zhang Rui
2014-08-06 18:31                 ` Markus Gutschke
2014-08-06 18:56                   ` Rafael J. Wysocki
2014-08-06 19:03                     ` Markus Gutschke
2014-08-09 10:14                       ` Markus Gutschke
2014-08-12  8:26                         ` Zhang Rui
2014-08-12 16:11                           ` Markus Gutschke
2014-08-15 17:17                             ` Markus Gutschke
2014-08-16  0:46                               ` Rafael J. Wysocki
2014-08-16  9:54                                 ` Markus Gutschke
2014-08-18  1:11                                 ` Zhang Rui

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=20140813114340.147b59e1@absurd \
    --to=janek.listy.mailowe@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).