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

Re: [Xen-devel] dump with xen-unstable & linux 3.2.17

I've bisected this to the following commit in the xen-unstable git tree.

I'll be able to dive in a little deeper tomorrow.
If you see anything here that looks suspicious to the crash
referenced... let me know.


e4a31205766d518276d0fbc1780bcd63db1a502d is the first bad commit
commit e4a31205766d518276d0fbc1780bcd63db1a502d
Author: Keir Fraser <keir@xxxxxxx>
Date:   Thu Mar 22 12:20:13 2012 +0000

    Introduce system_state variable.

    Use it to replace x86-specific early_boot boolean variable.

    Also use it to detect suspend/resume case during cpu offline/online
    to avoid unnecessarily breaking vcpu and cpupool affinities.

    Signed-off-by: Keir Fraser <keir@xxxxxxx>
    Acked-by: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>


or, if you prefer mercurial:

On Tue, May 22, 2012 at 2:26 PM, Ben Guthro <ben@xxxxxxxxxx> wrote:
> OK, I'll compare what got committed with our old patches against 4.0 &
> see if there are any obvious differences.
> Tom Goetz wrote those, originally - and he's on vacation - so
> specifics about them may have to wait until he returns.
> On Tue, May 22, 2012 at 2:00 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@xxxxxxxxxx> wrote:
>> On Tue, May 22, 2012 at 01:55:25PM -0400, Ben Guthro wrote:
>>> Are you referring to kernel, or Xen patches?
>> Xen.
>>> I'm currently seeing the issue in question with the xen-unstable tip
>>> none of our patches pushed...
>> I pushed the serial ones.
>>> ...or are you suggesting that the patch, as committed is incorrect?
>> I just tried to suspend and resume Xen 4.1 with and without serial console
>> and it only works when there is no serial console.
>> I think something is buggy. Not sure what (this was with a normal
>> built-in motherboard serial port).

Xen-devel mailing list



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