public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 17:02:06 +0100	[thread overview]
Message-ID: <20131101160206.GM17455@8bytes.org> (raw)
In-Reply-To: <CA+MoWDq4jYCD9zGaPA_Z4AL3Rj6hu4-rMEofn=8uWEGP6Tdruw@mail.gmail.com>

On Fri, Nov 01, 2013 at 04:47:47PM +0100, Peter Senna Tschudin wrote:
> Only serial ports over USB:
> usb 2-1.3.2: pl2303 converter now attached to ttyUSB0
> 
> The issue with no_console_suspend is that the monitor is powered off
> on suspend and never resume after that. The external monitor enters in
> power save mode during suspend and also never resume. Do you know if
> replacing my wifi/bt card by this:
> 
> http://www.startech.com/Cards-Adapters/Serial-Cards-Adapters/2-Port-RS232-Mini-PCI-Express-Serial-Card-16950-UART~MPEX2S952
> 
> would enable to use the serial console for seeing kernel debug messages?

Who knows, depends on the BIOS in your machine, I guess. But I would say
there is a at least a better chance with this than with a USB-Serial
adapter.


	Joerg



      reply	other threads:[~2013-11-01 16:02 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
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 [this message]

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=20131101160206.GM17455@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