| 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
| ||
|
Message-ID: <20070218002903.GF14773@elf.ucw.cz> Date: Sun, 18 Feb 2007 01:29:03 +0100 From: Pavel Machek <pavel@....cz> To: Pierre Ossman <drzeus-mmc@...eus.cx>, Greg KH <greg@...ah.com> Cc: Alex Dubov <oakad@...oo.com>, linux-kernel@...r.kernel.org Subject: Re: [mmc] incorrect behavior on resume On Sun 2007-02-18 00:35:33, Pierre Ossman wrote: > Alex Dubov wrote: > > And today: yet another problem with mmc. > > It so happens that after resume mmc layer issues requests to the device before mmc_resume_host is > > called at all. Moreover, this prevents the machine from resuming, unless worked around, because > > software timer does not work at this stage of the resume and interrupts may not be delivered (if > > card was removed, for example). > > Now this sounds incredibly broken. A child device should never be resumed before > its parent. Pavel, can you comment? No, child devices should not be resumed before their parents. Is it true child? What bus is mmc on? Timer should be resumed fairly early...? Can you confirm that rmmod/insmod of mmc around suspend fixes the issue? But this is greg's area. 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/
Powered by blists - more mailing lists