From: Andi Kleen <andi@firstfloor.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
kernel list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: iommu breaks usb after resume
Date: Fri, 21 Mar 2008 14:54:18 +0100 [thread overview]
Message-ID: <20080321135418.GB2346@one.firstfloor.org> (raw)
In-Reply-To: <20080320111429.GA14764@elf.ucw.cz>
On Thu, Mar 20, 2008 at 12:14:29PM +0100, Pavel Machek wrote:
> Hi!
>
> On 64-bit machine with 4GB ram (8core from amd), iommu breaks USB
> after swsusp. iommu=soft fixes that issue.
>
> I guess iommu handling in arch/x86/kernel/ should have some
> suspend/resume support, as it manipulates hardware registers...?
AGP suspend/resume should already handle restoring of the aperture
and the IOMMU code uses the same. It has not other state. It might not work
when the AGP driver is not compiled in/loaded though (I suspect
that is what happened to you) One simple fix would be to just enforce
that in Kconfig when suspend/resume is enabled.
-Andi
next prev parent reply other threads:[~2008-03-21 13:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 11:14 iommu breaks usb after resume Pavel Machek
2008-03-21 13:27 ` Ingo Molnar
2008-03-21 13:54 ` Andi Kleen [this message]
2008-03-26 10:21 ` Pavel Machek
2008-03-26 13:00 ` Andi Kleen
2008-03-26 22:54 ` Pavel Machek
2008-03-26 23:00 ` Ingo Molnar
2008-03-26 23:05 ` Pavel Machek
2008-03-27 5:53 ` Andi Kleen
2008-03-27 8:41 ` Pavel Machek
2008-03-27 8:42 ` Pavel Machek
2008-03-27 8:47 ` (eats disks) " Pavel Machek
2008-03-27 9:59 ` Pavel Machek
2008-03-27 11:49 ` Andi Kleen
2008-03-27 13:29 ` Pavel Machek
2008-03-27 13:34 ` Andi Kleen
2008-03-27 20:30 ` Rafael J. Wysocki
2008-03-27 23:40 ` Pavel Machek
2008-03-27 23:52 ` Rafael J. Wysocki
2008-03-28 13:50 ` 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=20080321135418.GB2346@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.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 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.