linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	markus@gutschke.com, Zhang Rui <rui.zhang@intel.com>,
	linux-kernel@vger.kernel.org,
	"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: Thu, 7 Aug 2014 19:54:15 +0200	[thread overview]
Message-ID: <20140807195415.03ca1027@absurd> (raw)
In-Reply-To: <20140806122548.GA10751@amd.pavel.ucw.cz>

Pavel Machek said:     (by the date of Wed, 6 Aug 2014 14:25:48 +0200)

> On Tue 2014-08-05 11:58:34, Janek Kozicki wrote:
> > Rafael J. Wysocki said:     (by the date of Tue, 05 Aug 2014 03:30:58 +0200)
> > 
> > > On Monday, August 04, 2014 09:06:52 AM Markus Gutschke wrote:
> > > > Thanks for checking in. And no, I have not heard from Zhang since my
> > > > last e-mail. I suspect he is still working on finding a solution. But
> > > > you are of course right, reverting the patch in the meantime might be
> > > > a good idea.
> > > 
> > > It has too many dependencies.  Besides, reverting it now (at the beginning of
> > > a merge window) won't be particularly useful anyway.
> > > 
> > > We need to fix it.
> > 
> > 
> > Hi, sorry for hijacking this thread, but apparently my other plead
> > for help got ignored in this very busy mailing list.
> > 
> > I have an up-to-date recently installed debian wheezy. I downloaded
> > https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.16.tar.xz and compiled it using:
> > 
> >   cp /boot/config-`uname -r` ./.config
> >   make menuconfig
> >   fakeroot make-kpkg --initrd --append-to-version=-vanilla.1 kernel_image kernel_headers -j38
> >   dpkg -i linux-image-3.16.0-vanilla.1_3.16.0-vanilla.1-10.00.Custom_amd64.deb linux-headers-3.16.0-vanilla.1_3.16.0-vanilla.1-10.00.Custom_amd64.deb
> > 
> > where .config was taken from debian /boot/config-3.14-0.bpo.1-amd64
> > 
> > my PC has 64GB of RAM, 32 Xeon E5-2687W cores and motherboard SuperMicro MBD-X9DRI
> > 
> > I just did 25 tries of suspend/resume cycle. I tried 4 different
> > methods of hibernation, you will find a full summary of my tries
> > (including how many failures for each method) in attached script
> > SLEEP.sh which I always used to perform hibernation.
> > 
> > The failure was always a reboot after resume had almost succeeded. In
> > cases when there was a success there was a following ---[cut
> >here]--- part:
> 
> The Intel audio driver seems to be requesting firmware... Can you
> rmmod snd_hda_codec_ca0132 and similar modules, and retry
> hibernation? 

Thanks a lot for your reply,

I did rmmod everything related to snd_hda_codec_ca0132 and then it
hanged during the suspend! There was something written on text
console, but I wasn't fast enough to photograph it. And I don't know
if it's written on the disk somewhere.

Now I'm following instructions from Rafael Wysocki and Takashi Iwai.
I hope these will help me getting out some useful debugging info.

-- 
Janek Kozicki                               http://janek.kozicki.pl/  |

  reply	other threads:[~2014-08-07 17:54 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                       ` 3.16 crashes on resume from Suspend-To-disk Janek Kozicki
2014-08-06 12:25                   ` Pavel Machek
2014-08-07 17:54                     ` Janek Kozicki [this message]
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=20140807195415.03ca1027@absurd \
    --to=janek_listy@wp.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@gutschke.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pavel@ucw.cz \
    --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).