[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131101142115.GK17455@8bytes.org>
Date: Fri, 1 Nov 2013 15:21:15 +0100
From: Joerg Roedel <joro@...tes.org>
To: Peter Senna Tschudin <peter.senna@...il.com>
Cc: iommu@...ts.linux-foundation.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Seiji Aguchi <seiji.aguchi@....com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: VT-d and x2apic: broken resume after suspend to ram
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@...tes.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists