linux-kernel - Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060730110847.GH1920@elf.ucw.cz>
Date:	Sun, 30 Jul 2006 13:08:47 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org, linux-pm@...l.org,
	alsa-devel@...a-project.org, mingo@...e.hu
Subject: Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/