From: Joerg Roedel <joro@8bytes.org>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: iommu@lists.linux-foundation.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Seiji Aguchi <seiji.aguchi@hds.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: VT-d and x2apic: broken resume after suspend to ram
Date: Fri, 1 Nov 2013 14:07:10 +0100 [thread overview]
Message-ID: <20131101130702.GA3348@8bytes.org> (raw)
In-Reply-To: <CA+MoWDqoBxuFhBsf_rVBT1C8=mwj02hXgPfuWnjY4yeVa-84cA@mail.gmail.com>
Hi Peter,
On Fri, Nov 01, 2013 at 01:37:36PM +0100, Peter Senna Tschudin wrote:
> I have one notebook that is failing to resume after suspend to ram.
> I've filled a bug report back on the 2.6.41 days:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=787299
>
> The issue is that trying to resume after suspending to ram freezes the
> computer. The resume starts well, but then it hangs.
>
> Yesterday I found that this may be related to VT-d / x2apic. If I
> disable VT-d on the BIOS, suspend / resume works fine. If I enable
> VT-d and pass nox2apic as boot parameter to Kernel suspend and resume
> works fine. I would like some pointers to fix this issue. Can you help
> me?
>
> Only when I have VT-d enabled, dmesg gives me additional output:
> [ 0.023913] IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
> [ 0.024080] Enabled IRQ remapping in x2apic mode
> [ 0.024081] Enabling x2apic
> [ 0.024082] Enabled x2apic
> [ 0.024087] Switched APIC routing to cluster x2apic.
>
> The notebook is Toshiba R830-10p with i7-2620M.
Which kernels have you tried? Does it happen with all of them or is
there a kernel-version where this started?
Joerg
next prev parent reply other threads:[~2013-11-01 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 12:37 VT-d and x2apic: broken resume after suspend to ram Peter Senna Tschudin
2013-11-01 13:07 ` Joerg Roedel [this message]
2013-11-01 13:21 ` Peter Senna Tschudin
2013-11-01 14:21 ` Joerg Roedel
2013-11-01 15:47 ` Peter Senna Tschudin
2013-11-01 16:02 ` Joerg Roedel
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=20131101130702.GA3348@8bytes.org \
--to=joro@8bytes.org \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peter.senna@gmail.com \
--cc=seiji.aguchi@hds.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox