From: mark gross <mgross@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Lutomirski <amluto@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Kyle McMartin <kyle@redhat.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
David Woodhouse <David.Woodhouse@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.29: can't resume from suspend with DMAR (intel iommu) enabled
Date: Wed, 25 Mar 2009 10:32:12 -0700 [thread overview]
Message-ID: <20090325173212.GA30701@linux.intel.com> (raw)
In-Reply-To: <20090324203259.GC26930@elte.hu>
On Tue, Mar 24, 2009 at 09:32:59PM +0100, Ingo Molnar wrote:
>
> (Cc:s added)
>
> * Andrew Lutomirski <amluto@gmail.com> wrote:
>
> > On vanilla 2.6.29 (on Ubuntu 8.10), on a Lenovo x200s, my system
> > is completely hosed on resume. It appears that even hard disk IO
> > didn't work (trying to do *anything* including getting a dmesg
> > trace just spewed sda io errors to the console). Hence no trace.
> > I did an alt-sysrq-b and the screen went blank and the machine
> > just started beeping at me.
> >
> > Resume works much better with intel_iommu=off. (I remember seeing
> > a patch go by that purported to fix resume with IOMMU enabled, but
> > it didn't work for me.)
> >
> > I'd be happy to try to make a better bug report if anyone has any
> > bright ideas.
>
> i have a Lenovo T500 that does not even boot with with DMAR enabled
> in the BIOS (it's default-off), i get this panic in early bootup:
>
> DMAR hardware is malfunctioning
That happens when the polling of the IOMMU registers fail to behave as
expected in the VT-d specification. Typically its been a bios issue
when this happens.
>
> So i dont get to test suspend/resume ;-)
>
> Ingo
next prev parent reply other threads:[~2009-03-25 17:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 19:58 2.6.29: can't resume from suspend with DMAR (intel iommu) enabled Andrew Lutomirski
2009-03-24 20:03 ` Rafael J. Wysocki
2009-03-24 20:32 ` Ingo Molnar
2009-03-24 20:36 ` Yu, Fenghua
2009-03-24 20:40 ` Kyle McMartin
2009-04-10 22:46 ` David Woodhouse
2009-04-10 23:21 ` Yu, Fenghua
2009-04-11 0:48 ` Suresh Siddha
2009-04-11 2:12 ` David Woodhouse
2009-03-24 22:36 ` [PATCH 1/2] Intel IOMMU Suspend/Resume Support for DMAR Fenghua Yu
2009-03-24 22:37 ` [PATCH 2/2] Intel IOMMU Suspend/Resume Support for Queued Invalidation Fenghua Yu
2009-03-25 17:32 ` mark gross [this message]
2009-03-25 17:38 ` 2.6.29: can't resume from suspend with DMAR (intel iommu) enabled Ingo Molnar
2009-03-25 17:53 ` David Woodhouse
2009-03-25 17:59 ` Ingo Molnar
2009-03-25 18:03 ` David Woodhouse
2009-03-25 18:07 ` Ingo Molnar
2009-03-25 18:10 ` David Woodhouse
2009-03-25 18:20 ` Ingo Molnar
2009-03-25 18:42 ` Ingo Molnar
2009-04-06 20:56 ` David Woodhouse
2009-04-07 7:56 ` Matthew Garrett
2009-04-07 11:10 ` David Woodhouse
2009-04-10 21:27 ` David Woodhouse
2009-04-11 6:04 ` David Woodhouse
2009-04-11 14:38 ` Kyle McMartin
2009-04-11 16:52 ` David Woodhouse
2009-04-11 17:14 ` Kyle McMartin
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=20090325173212.GA30701@linux.intel.com \
--to=mgross@linux.intel.com \
--cc=David.Woodhouse@intel.com \
--cc=amluto@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=yinghai@kernel.org \
/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.