All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Peter Senna Tschudin
	<peter.senna-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	Seiji Aguchi <seiji.aguchi-7rDLJAbr9SE@public.gmane.org>
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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

WARNING: multiple messages have this Message-ID (diff)
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



  parent reply	other threads:[~2013-11-01 13:07 UTC|newest]

Thread overview: 9+ 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
     [not found] ` <CA+MoWDqoBxuFhBsf_rVBT1C8=mwj02hXgPfuWnjY4yeVa-84cA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-01 13:07   ` Joerg Roedel [this message]
2013-11-01 13:07     ` Joerg Roedel
2013-11-01 13:21     ` Peter Senna Tschudin
     [not found]       ` <CA+MoWDoDTFarOLUHgNmUFksRvV-R+7jufUwLbsS8ecaO+_m2kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-01 14:21         ` Joerg Roedel
2013-11-01 14:21           ` Joerg Roedel
2013-11-01 15:47           ` Peter Senna Tschudin
     [not found]             ` <CA+MoWDq4jYCD9zGaPA_Z4AL3Rj6hu4-rMEofn=8uWEGP6Tdruw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-01 16:02               ` Joerg Roedel
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-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=peter.senna-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=seiji.aguchi-7rDLJAbr9SE@public.gmane.org \
    --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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.