From: Malcolm Crossley <malcolm.crossley@citrix.com>
To: Ben Guthro <ben@guthro.net>
Cc: Jinsong Liu <jinsong.liu@intel.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: S3 resume issues
Date: Tue, 15 Jan 2013 18:32:54 +0000 [thread overview]
Message-ID: <50F5A0D6.3080709@citrix.com> (raw)
In-Reply-To: <CAOvdn6Wx4PEY23n=nm9FL=_XkckSzn+FnWOdE23FYgTBxWz-nA@mail.gmail.com>
On 15/01/13 18:22, Ben Guthro wrote:
> On Tue, Jan 15, 2013 at 1:17 PM, Malcolm Crossley
> <malcolm.crossley@citrix.com> wrote:
>> You get 0xFF when there is nothing responding to the ioport. If the 16550 is
>> on a PCI card then it could be the PCI connection has not been setup again
>> after the resume and you can't get to that ioport range.
> This is not a PCI card, it is on onboard card (io base 0x3f8)
>
> Ben
Interesting, it may be the serial device requires some ACPI method to be
called to initialise/enable it correctly.
A serial port on a HP Elitebook 8570p we have seems to not initialise
the serial port after the BIOS has started. The serial only starts
working when the Linux kernel runs the ACPI enable method (halfway
through the kernel boot) . I've tried to decompile the ACPI AML and it
looks like it's enabling the serial via a microcontroller.
It could be you have a similar microcontroller based serial port on your
system which can only be initialised via ACPI.
It might be worth checking that the io decode windows are enabled on the
panther point chipset for the 0x3f8 port ranges. Check that bits 0-2 are
0 at address 0x80 and that bit 0 is 0 at address 0x82 in PCI device 0:1f
config space.
Malcolm
next prev parent reply other threads:[~2013-01-15 18:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 13:08 S3 resume issues Ben Guthro
2013-01-02 15:15 ` Malcolm Crossley
2013-01-02 15:31 ` Ben Guthro
2013-01-02 16:46 ` Ben Guthro
2013-01-02 20:35 ` Malcolm Crossley
2013-01-02 20:50 ` Ben Guthro
2013-01-03 10:19 ` Jan Beulich
2013-01-03 16:33 ` Ben Guthro
2013-01-03 17:08 ` Jan Beulich
2013-01-03 17:28 ` Ben Guthro
2013-01-03 21:26 ` Ben Guthro
2013-01-04 8:34 ` Jan Beulich
2013-01-11 20:32 ` Ben Guthro
2013-01-14 22:00 ` Ben Guthro
2013-01-15 8:33 ` Jan Beulich
2013-01-15 12:55 ` Ben Guthro
2013-01-15 18:10 ` Ben Guthro
2013-01-15 18:17 ` Malcolm Crossley
2013-01-15 18:22 ` Ben Guthro
2013-01-15 18:32 ` Malcolm Crossley [this message]
2013-01-15 18:38 ` Ben Guthro
2013-01-15 18:39 ` Malcolm Crossley
2013-01-16 16:16 ` Ben Guthro
2013-01-16 9:35 ` Jan Beulich
[not found] ` <CAOvdn6V6N1V9ZYbARTJPEgSvxPe83pSiO6TmxBLy1LJEkods6A@mail.gmail.com>
2013-01-16 10:57 ` Jan Beulich
2013-01-16 11:05 ` Ben Guthro
2013-01-16 11:09 ` Jan Beulich
2013-01-16 11:17 ` Ben Guthro
2013-01-02 17:14 ` Pasi Kärkkäinen
2013-01-02 17:20 ` Ben Guthro
2013-01-16 2:18 ` Tomasz Wroblewski
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=50F5A0D6.3080709@citrix.com \
--to=malcolm.crossley@citrix.com \
--cc=JBeulich@suse.com \
--cc=ben@guthro.net \
--cc=jinsong.liu@intel.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 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.