public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Takashi Iwai <tiwai@suse.de>,
	Arjan van de Ven <arjan@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [linux-pm] [2.6.30-rc1-git2 regressions] Hibernation broken and (minor but annoying) audio problem
Date: Fri, 10 Apr 2009 20:58:35 +0200	[thread overview]
Message-ID: <200904102058.36018.rjw@sisk.pl> (raw)
In-Reply-To: <200904101439.43480.rjw@sisk.pl>

On Friday 10 April 2009, Rafael J. Wysocki wrote:
> On Friday 10 April 2009, Linus Torvalds wrote:
> > 
> > On Fri, 10 Apr 2009, Rafael J. Wysocki wrote:
> > > 
> > > I'm seeing two problems with -git from today.
> > 
> > When today? A number of people apparently had module problems before 
> > commit 97c18e2c7a8e36d2d83d50ee070314aadac73a11 ("module: 
> > try_then_request_module must wait").
> > 
> > If you don't have that one, then that might explain both problems, in that 
> > a "second try" would work for modules (your sound issue), and that 
> > compiling things in would obviously avoid it (your storage driver thing).
> > 
> > But if you _do_ have that, then it's obviously something else ;)
> 
> Well, I do have that one. :-)

I've just verified that the resume-after-hibernation issue goes away after
reverting commit 9710794383ee5008d67f1a6613a4717bf6de47bc
(async: remove the temporary (2.6.29) "async is off by default" code) , so it
is async-related.

The audio issue still remains after the revert, so it is really different.

Thanks,
Rafael

  reply	other threads:[~2009-04-10 18:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 22:57 [2.6.30-rc1-git2 regressions] Hibernation broken and (minor but annoying) audio problem Rafael J. Wysocki
2009-04-09 23:06 ` Linus Torvalds
2009-04-10 12:39   ` Rafael J. Wysocki
2009-04-10 18:58     ` Rafael J. Wysocki [this message]
2009-04-10 19:17       ` [linux-pm] " Linus Torvalds
2009-04-11  0:06         ` Rafael J. Wysocki
2009-04-11  1:19           ` Linus Torvalds
2009-04-11  1:45             ` Arjan van de Ven
2009-04-11  2:10             ` Arjan van de Ven
2009-04-11 10:46               ` Rafael J. Wysocki
2009-04-11 19:38               ` Rafael J. Wysocki
2009-04-11 19:55                 ` Linus Torvalds
2009-04-11 20:05                   ` Arjan van de Ven
2009-04-12 18:06                     ` Rafael J. Wysocki
2009-04-12 18:27                       ` Arjan van de Ven
2009-04-11  1:53         ` Arjan van de Ven
2009-04-11  2:35     ` Len Brown
2009-04-11 18:11       ` Linus Torvalds
2009-04-11 19:00         ` Heinz Diehl
2009-04-11 19:16         ` Arjan van de Ven
2009-04-11 19:50           ` Linus Torvalds
2009-04-11 20:11             ` Arjan van de Ven
2009-04-11 20:18             ` Arkadiusz Miskiewicz
2009-04-14 12:09 ` Takashi Iwai
2009-04-14 21:12   ` Rafael J. Wysocki
2009-04-15 13:13     ` Takashi Iwai
2009-04-15 20:59       ` Rafael J. Wysocki
2009-04-15 21:05         ` Linus Torvalds
2009-04-16  6:05           ` Takashi Iwai
2009-04-16 20:18             ` Rafael J. Wysocki

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=200904102058.36018.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.org \
    /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