From: Andi Kleen <andi@firstfloor.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Patrick <ragamuffin@datacomm.ch>, Pavel Machek <pavel@suse.cz>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption
Date: Wed, 11 Jun 2008 17:04:29 +0200 [thread overview]
Message-ID: <484FE97D.4040805@firstfloor.org> (raw)
In-Reply-To: <200806111638.50933.rjw@sisk.pl>
> Well, I was hoping to be able to get this patch into 2.6.26, as I don't really
> like the temporary hack, preventing the affected systems from resuming
> at all, that we have in there, but it seems to be too late. :-(
I agree with you that this patch would be far better than the hack.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Patrick <ragamuffin@datacomm.ch>, Pavel Machek <pavel@suse.cz>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption
Date: Wed, 11 Jun 2008 17:04:29 +0200 [thread overview]
Message-ID: <484FE97D.4040805@firstfloor.org> (raw)
In-Reply-To: <200806111638.50933.rjw@sisk.pl>
> Well, I was hoping to be able to get this patch into 2.6.26, as I don't really
> like the temporary hack, preventing the affected systems from resuming
> at all, that we have in there, but it seems to be too late. :-(
I agree with you that this patch would be far better than the hack.
-Andi
next prev parent reply other threads:[~2008-06-11 15:04 UTC|newest]
Thread overview: 37+ 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
2008-05-29 18:51 ` Patrick
2008-05-29 21:05 ` Patrick
2008-06-03 22:33 ` Rafael J. Wysocki
2008-06-03 22:33 ` Rafael J. Wysocki
2008-06-06 13:20 ` Pavel Machek
2008-06-06 13:20 ` Pavel Machek
2008-06-08 22:36 ` Rafael J. Wysocki
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-12 9:34 ` Ingo Molnar
2008-06-10 10:03 ` Rafael J. Wysocki
2008-06-09 22:10 ` Rafael J. Wysocki
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 [this message]
2008-06-11 15:04 ` Andi Kleen
2008-07-03 17:35 ` Patrick
2008-07-03 17:35 ` Patrick
2008-08-07 8:17 ` Pavel Machek
2008-08-07 8:17 ` Pavel Machek
2008-08-08 22:40 ` Patrick
2008-09-02 8:05 ` Pavel Machek
2008-09-02 8:05 ` Pavel Machek
2008-08-08 22:53 ` YOUR SPAM FILTER IS BROCKEN -- was " Patrick
2008-06-11 11:58 ` Patrick
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=484FE97D.4040805@firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=ragamuffin@datacomm.ch \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.