mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Rafael J. Wysocki" <rjw@suse.com>
Cc: linux-pm@lists.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 18:19:44 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904101817100.4583@localhost.localdomain> (raw)
In-Reply-To: <200904110206.33525.rjw@suse.com>



On Sat, 11 Apr 2009, Rafael J. Wysocki wrote:
> 
> On Friday 10 April 2009, Linus Torvalds wrote:
> > 
> > On Fri, 10 Apr 2009, Rafael J. Wysocki wrote:
> > > 
> > > 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.
> > 
> > Arjan? Clearly all the necessary fixes weren't found..
> > 
> > There _is_ a module loading problem wrt initmem - I think you found that 
> > and we added a hack for it for the ACPI battery driver. I wonder if we're 
> > hitting a similar issue now with module discovery: modules that use 
> > "async_schedule()" to do their discovery asynchronously are now not 
> > necessarily fully "done" when the module is loaded. 
> > 
> > And so, anything that expected the devices to be available after module 
> > load (like they used to) would be screwed.
> > 
> > IOW, maybe something like the totally untested patch appended here (that 
> > should also allow us to make the ACPI battery code to go back to using 
> > __init).
> 
> I tested it and it worked.

Hmm.

I'm not 100% sure that patch is good.

The reason? I think it's going to deadlock if an async caller ends up 
wanting to load a module, because then the nestecd 
"async_synchronize_full()" will basically want to wait for itself.

So it's a good test-patch, and maybe no async caller ever loads a module, 
but it makes me a bit nervous.

But the fact that it fixes things for you at least means that the _reason_ 
for the problem is know, and maybe there are alternative solutions. Arjan?

		Linus

  reply	other threads:[~2009-04-11  1:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 22:57 Rafael J. Wysocki
2009-04-09 23:06 ` Linus Torvalds
2009-04-10 12:39   ` Rafael J. Wysocki
2009-04-10 18:58     ` [linux-pm] " Rafael J. Wysocki
2009-04-10 19:17       ` Linus Torvalds
2009-04-11  0:06         ` Rafael J. Wysocki
2009-04-11  1:19           ` Linus Torvalds [this message]
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=alpine.LFD.2.00.0904101817100.4583@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --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=rjw@suse.com \
    --cc=tiwai@suse.de \
    /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

Powered by JetHome