linux-kernel - Re: [Alsa-devel] 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: <20060731140304.GA3399@elf.ucw.cz>
Date:	Mon, 31 Jul 2006 16:03:05 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Jiri Slaby <jirislaby@...il.com>,
	Andrew Morton <akpm@...l.org>, linux-pm@...l.org,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
	mingo@...e.hu
Subject: Re: [Alsa-devel] swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1]

Hi!

> > If the driver is compiled in, its .suspend() routine gets called before the
> > suspend image is restored and puts the card in a state that confuses
> > the .resume() called after the image has been restored.
> > 
> > I think snd_emu10k1_suspend() should reset the device if state == PMSG_PRETHAW .
> 
> Hm, do we need such inconsitent behavior?  I mean, for most drivers,
> it doesn't matter whether it's built-in or a module: simply shutdown
> at suspend, and initialize at resume.

That's of course the other (and better) solution.
									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/