xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ben Guthro <ben.guthro@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Malcolm Crossley <malcolm.crossley@citrix.com>,
	Ben Guthro <ben@guthro.net>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] ns16550: delay resume until dom0 ACPI has a chance to run
Date: Thu, 17 Jan 2013 07:04:17 -0500	[thread overview]
Message-ID: <-7156672500108411140@unknownmsgid> (raw)
In-Reply-To: <50F7EA1102000078000B6BD5@nat28.tlf.novell.com>

On Jan 17, 2013, at 6:09 AM, Jan Beulich <JBeulich@suse.com> wrote:

>>>> On 16.01.13 at 22:48, Ben Guthro <ben@guthro.net> wrote:
>> On Wed, Jan 16, 2013 at 4:40 PM, Malcolm Crossley
>> <malcolm.crossley@citrix.com> wrote:
>>
>>> Do these laptops (T430/T530) have built in serial?
>>
>> They seem to have the hardware for it, but no actual serial connector
>> out of the machine.
>> This hardware provides the legacy port that Xen initializes in
>> xen/arch/x86/setup.c __start_xen()
>>
>> When the resume happened, it was getting stuck in __ns16550_poll()
>> because it thought that the
>> LSR register was 0xFF - and had lots of data to read. It got stuck in
>> that while loop, and never
>> exited.
>
> So before acking the patch I'd like to understand how we end up
> in that loop even when no serial console is in use. Assuming that's
> because the post-IRQ initialization (mostly) unconditionally inserts
> the timer, that shouldn't be an issue on -unstable (as post-IRQ
> init of the individual drivers doesn't get called anymore when no
> respective command line option was present, and likewise their
> suspend/resume handlers don't get called anymore in that case).
> In which case backporting from -unstable would be preferable
> over putting custom stuff on the 4.x branches (albeit we likely
> still want the change here to have a way to resume with serial
> console, but the impact would be quite different).
>
> Jan
>

Admittedly, I have been doing my testing on 4.2.y

I can try unstable today to see if it makes a difference in this path.

  reply	other threads:[~2013-01-17 12:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 20:20 [PATCH] ns16550: delay resume until dom0 ACPI has a chance to run Ben Guthro
2013-01-16 21:24 ` Pasi Kärkkäinen
2013-01-16 21:31   ` Ben Guthro
2013-01-16 21:40     ` Malcolm Crossley
2013-01-16 21:48       ` Ben Guthro
2013-01-16 21:54         ` Pasi Kärkkäinen
2013-01-17 11:09         ` Jan Beulich
2013-01-17 12:04           ` Ben Guthro [this message]
2013-01-17 13:37             ` Ben Guthro
2013-01-18 15:53               ` Konrad Rzeszutek Wilk
2013-01-18 20:07                 ` Ben Guthro
2013-04-22 13:51           ` Ben Guthro
2013-04-23  6:40             ` Jan Beulich
2013-04-23 18:56               ` Ben Guthro
2013-01-16 21:52       ` Pasi Kärkkäinen

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=-7156672500108411140@unknownmsgid \
    --to=ben.guthro@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=ben@guthro.net \
    --cc=malcolm.crossley@citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).