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 15:21:15 +0100 [thread overview]
Message-ID: <20131101142115.GK17455@8bytes.org> (raw)
In-Reply-To: <CA+MoWDoDTFarOLUHgNmUFksRvV-R+7jufUwLbsS8ecaO+_m2kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Nov 01, 2013 at 02:21:07PM +0100, Peter Senna Tschudin wrote:
> On Fri, Nov 1, 2013 at 2:07 PM, Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org> wrote:
> > Which kernels have you tried? Does it happen with all of them or is
> > there a kernel-version where this started?
>
> I'm using 3.11.6-200.fc19.x86_64. I always had VT-d enabled, and
> suspend / resume never worked on Linux. I did not know that disabling
> VT-d could be a workaround to the resume issue until yesterday.
>
> Does this have anything in common to:
> https://bugzilla.redhat.com/show_bug.cgi?id=752613
This is probably not related. As far as I can see this issue was about
boot problem with discrete graphics while your problem is related to
suspend/resume.
The next thing I would try on your machine is to get some kernel debug
messages from resume. This might be hard to get, since your notebook
has probably no serial port. But you can try to boot with
no_console_suspend on the kernel cmdline and see if it gives you any
output on resume.
Maybe some of the VT-d guys can take a look too?
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 15:21:15 +0100 [thread overview]
Message-ID: <20131101142115.GK17455@8bytes.org> (raw)
In-Reply-To: <CA+MoWDoDTFarOLUHgNmUFksRvV-R+7jufUwLbsS8ecaO+_m2kQ@mail.gmail.com>
On Fri, Nov 01, 2013 at 02:21:07PM +0100, Peter Senna Tschudin wrote:
> On Fri, Nov 1, 2013 at 2:07 PM, Joerg Roedel <joro@8bytes.org> wrote:
> > Which kernels have you tried? Does it happen with all of them or is
> > there a kernel-version where this started?
>
> I'm using 3.11.6-200.fc19.x86_64. I always had VT-d enabled, and
> suspend / resume never worked on Linux. I did not know that disabling
> VT-d could be a workaround to the resume issue until yesterday.
>
> Does this have anything in common to:
> https://bugzilla.redhat.com/show_bug.cgi?id=752613
This is probably not related. As far as I can see this issue was about
boot problem with discrete graphics while your problem is related to
suspend/resume.
The next thing I would try on your machine is to get some kernel debug
messages from resume. This might be hard to get, since your notebook
has probably no serial port. But you can try to boot with
no_console_suspend on the kernel cmdline and see if it gives you any
output on resume.
Maybe some of the VT-d guys can take a look too?
Joerg
next prev parent reply other threads:[~2013-11-01 14:21 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
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 [this message]
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=20131101142115.GK17455@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.