[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] S3 resume issues

>>> On 16.01.13 at 12:05, Ben Guthro <ben@xxxxxxxxxx> wrote:
> On Wed, Jan 16, 2013 at 5:57 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>> And to me this
>>>> would also imply that if you run without serial console, there
>>>> wouldn't be an issue.
>>> I thought this as well - but if I read the code correctly, it seems
>>> that the ns16550 is set up for the legacy devices in
>>> xen/arch/x86/setup.c _start_xen(), regardless of whether serial is
>>> configured on the command line (if the hardware exists):
>>>     /* We initialise the serial devices very early so we can get debugging.
>>> */
>>>     ns16550.io_base = 0x3f8;
>>>     ns16550.irq     = 4;
>>>     ns16550_init(0, &ns16550);
>>>     ns16550.io_base = 0x2f8;
>>>     ns16550.irq     = 3;
>>>     ns16550_init(1, &ns16550);
>> Yeah, but serial_resume() doesn't call their resume handlers
>> unless their state is serial_initialized, which it can get to only
>> through serial_parse_handle() seeing the right handle.
> hmm, OK, I guess I missed that part.
> I'll look closer today, to see if there is something in the config
> space of this device that isn't getting preserved.

Config space of a non-PCI device?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.