From: Pavel Machek <pavel@suse.cz>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-pm@osdl.org,
alsa-devel@alsa-project.org, mingo@elte.hu
Subject: Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]
Date: Sun, 30 Jul 2006 13:08:47 +0200 [thread overview]
Message-ID: <20060730110847.GH1920@elf.ucw.cz> (raw)
In-Reply-To: <44CC8FD3.5030403@gmail.com>
Hi!
> >Please try to revert git-alsa.patch and see if the emu10k1-related problem
> >goes away.
>
> Wow, it didn't helped, I find out there is a difference between in-kernel
> and modules version of the driver. When compiled as modules
> (loaded/unloaded) suspending (and resuming) is working ok (enabled higmem
> and preempt back -- still no smp), when compiled in-kernel (see the config
> diff below), it doesn't resume.
Yes, that sometimes happens. You could work around it by catching
PM_EVENT_PRETHAW message and resetting the hardware in this case. Or
just fix the resume routine.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-07-30 11:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060727015639.9c89db57.akpm@osdl.org>
2006-07-29 17:58 ` swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1] Jiri Slaby
2006-07-29 18:59 ` Rafael J. Wysocki
2006-07-29 23:06 ` Jiri Slaby
2006-07-29 23:10 ` Rafael J. Wysocki
2006-07-29 23:59 ` Jiri Slaby
2006-07-30 0:03 ` Jiri Slaby
2006-07-29 23:22 ` Pavel Machek
2006-07-29 23:58 ` Jiri Slaby
2006-07-30 0:06 ` Pavel Machek
2006-07-30 7:31 ` Rafael J. Wysocki
2006-07-30 8:08 ` Jiri Slaby
2006-07-30 9:28 ` Rafael J. Wysocki
2006-07-30 10:54 ` Jiri Slaby
2006-07-30 11:08 ` Pavel Machek [this message]
2006-07-30 11:34 ` Rafael J. Wysocki
2006-07-31 13:59 ` Takashi Iwai
2006-07-31 14:03 ` [Alsa-devel] " Pavel Machek
2006-07-30 11:36 ` James Courtier-Dutton
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=20060730110847.GH1920@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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