linux-kernel - Re: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1211815881.6140.19.camel@localhost.localdomain>
Date:	Mon, 26 May 2008 17:31:21 +0200
From:	Patrick <ragamuffin@...acomm.ch>
To:	Pavel Machek <pavel@...e.cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard
	Disk Corruption

> Can you try this one? It should prevent suspend in the broken cases,
> but allow it in mem=4G config.

Sure!

root@...ar:/usr/src/linux-2.6.25# patch -p1 < /home/pat/patch-2.6.26-rc3.gart-suspend
patching file arch/x86/kernel/pci-gart_64.c
Hunk #4 succeeded at 629 with fuzz 2 (offset 11 lines).

.....make; cp bzImage /boot; reboot....

without mem=4G:
...
[17180761.682783] CPU1 is down
[17180761.682968] Class suspend failed for gart0
[17180761.683321] PM: Some devices failed to power down
[17180761.683326] Enabling non-boot CPUs ...

with mem=4G:
...
[no change]

-> perfect! Behaves as you predicted.

logs are ... here: http://zefir.890m.com/dmesg/ *

Thanks for attacking the issue really quickly.

I'm ready to do further testing and will try to find enough
time to do one test a day during the week.

Cheers

* The other host's dns entry is gone, I guess that's because it
had too much requests and was taken down...? Hope this one survives!

--
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/