From: Patrick <ragamuffin@datacomm.ch>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption
Date: Thu, 29 May 2008 20:44:01 +0200 [thread overview]
Message-ID: <1212086641.4625.56.camel@localhost.localdomain> (raw)
In-Reply-To: <20080527112236.GA13957@elf.ucw.cz>
Hi!
> This goes on top of the second patch... it makes it work.
>
> Pavel
>
All right. It works! :-) Thank you very much!
I'll describe how I tested:
So far you sent 3 Patches to the list. As I couldn't apply the second
one to my v2.6.26-rc4 tree i had to get git and then your tree. Now I
have a git working tree with two branches *master* and *pavel*,
corresponding to torvalds/linux-2.6 and pavel/work respectively.
I made *pavel* the current branch and issued the following command:
git diff v2.6.26-rc4 arch/x86/kernel/aperture_64.c \
arch/x86/kernel/k8.c \
arch/x86/kernel/pci-gart_64.c \
drivers/char/agp/generic.c \
include/asm-x86/gart.h \
> /home/pat/suspend-vs-iommu.patch
The result is on http://zefir.890m.com/dmesg/
I applied this patch to my old v2.6.26-rc4 tree and recompiled a new
kernel there *, put it in place and rebooted. I suspended several times
since then and put a kernel log of one normal boot process with suspend
from console while X is running (radeonhd) on the site mentioned before.
I'm running debian testing / ubuntu hardy mixed system and used
kernel .config from linux-headers-2.6.25-2-amd64.deb (debian unstable)
with "make oldconfig" and defaults on new options.
The diff is nearly 500 lines long, but i it could be narrowed, I guess.
For me it works perfectly like this though. If you want me to do any
further tests, just say so. I'm trying to get to know git a bit better
and hope to be able to help again sometime. It's great fun! :-)
Cheers
* I get
"ACPI: Unable to turn cooling device [ffff81012fa5cdd0] 'off'" every two
seconds and "fancontrol" isn't working any more... going to send a
acpidump to the acpi group. Maybe i'll find out myself as well...
investigating. Not sure if it's caused by the patch.
next prev parent reply other threads:[~2008-05-29 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 12:10 SB600 AHCI: Hard Disk Corruption Patrick
2008-05-25 12:16 ` Patrick
2008-05-25 17:38 ` Pavel Machek
2008-05-25 20:08 ` Patrick
2008-05-25 20:39 ` >3G => iommu => suspend problems -- was " Pavel Machek
2008-05-25 21:10 ` Pavel Machek
2008-05-26 15:31 ` Patrick
2008-05-27 11:22 ` Pavel Machek
2008-05-29 18:44 ` Patrick [this message]
2008-05-29 18:51 ` Patrick
2008-05-29 21:05 ` Patrick
2008-06-03 22:33 ` Rafael J. Wysocki
2008-06-06 13:20 ` Pavel Machek
2008-06-08 22:36 ` Rafael J. Wysocki
[not found] ` <20080609124630.GA28799@elte.hu>
2008-06-09 22:10 ` [PATCH] x86 GART: Add resume handling (was: Re: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption) Rafael J. Wysocki
2008-06-10 10:03 ` Rafael J. Wysocki
2008-06-12 9:34 ` Ingo Molnar
2008-06-11 11:43 ` >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption Patrick
2008-06-11 14:38 ` Rafael J. Wysocki
2008-06-11 15:04 ` Andi Kleen
2008-07-03 17:35 ` Patrick
2008-08-07 8:17 ` Pavel Machek
2008-08-08 22:40 ` Patrick
2008-09-02 8:05 ` Pavel Machek
2008-05-27 10:23 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1212086641.4625.56.camel@localhost.localdomain \
--to=ragamuffin@datacomm.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox