| 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: <20080525203921.GB18781@elf.ucw.cz> Date: Sun, 25 May 2008 22:39:21 +0200 From: Pavel Machek <pavel@...e.cz> To: Patrick <ragamuffin@...acomm.ch> Cc: linux-kernel@...r.kernel.org Subject: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption Hi! > > iommu problem? Try it with mem=3G. > > YES! :-) How did you know? Guess how... I hit it myself. > So how are we going to get this fixed??? Write a patch, submit it? ;-). Okay, I guess I should do the patch, but I can't test it easily. If you can do testing/some development, I guess I can try to cook up something. (But no, I'm not an IOMMU expert). > Should the IOMMU be reinitialized after resume? Or should the bios do it > but doesn't? ** On the m2a-vm, the "GART" seems to be used as iommu, > so... :-) ??? It is a Linux bug. BIOS could be more helpful, but... this is a Linux problem. > I put some kernel message logs here: > http://zefir.freesitespace.net/dmesg/ > One log without mem=4G will also be there shortly, where you will see > the messages concerning the iommu (which seems to be unused right > now). Yep, they are similar to what I see. > ???** Seems, the SB600 is not to blame - alas sorry for the subject. Subject is easy to change ;-). 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