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

Re: [Xen-devel] Xen-4.3 and -unstable regression from changeset "numa-sched: leave node-affinity alone if not in 'auto' mode"

On gio, 2013-11-28 at 12:31 +0000, Andrew Cooper wrote:
> Hello,

> I have recently positivly identified
> b54a623efbcf5bff25c55117add1b4427b4e2f1b as causing a boot failure.
> Serial log is attached.  The crash is completely deterministic, and is
> from an IBM xSeries 3530 M4 server.
> Given the crash and bad patch, I suspect it is more to do with the
> NUMA/memory layout than the specifics of the server.
> Dario: Being your patch, do you have any ideas?
Wow... Not out of the top of my head... Can you try (or tell me how to
do that on that box) the attached debug patch?

I know it's gross, but given where and how early the crash happens, it
shouldn't be too bad, and it would hopefully at least tell if
d->node_affinity contains garbage.


<<This happens because I choose it to happen!>> (Raistlin Majere)
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

Attachment: node_affinity.patch
Description: Text Data

Attachment: signature.asc
Description: This is a digitally signed message part

Xen-devel mailing list



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