From: Arjan van de Ven <arjan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.linux-foundation.org, Takashi Iwai <tiwai@suse.de>,
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:53:59 -0700 [thread overview]
Message-ID: <49DFF837.9080009@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0904101204350.4583@localhost.localdomain>
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.
this is both a "yes and no" kind of thing. It already happened for many cases
(USB, SCSI (and thus libata) etc) but now it can happen for more new cases.
> 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).
>
this will work. It's a tad unfortunate that we basically end up synchronizing
at load time; maybe some time in the future we can make this opt-in/out ;-(
next prev parent reply other threads:[~2009-04-11 1:54 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 ` [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
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 [this message]
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=49DFF837.9080009@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--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