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

Re: [Xen-devel] Oops in xen 3.0.2 dequeue_signal [was: Re: DomU Oopsing on xen-3.0-testing changeset 8259]

Keir Fraser wrote:
Does it always crash in __dequeue_signal()?


You might have to add some tracing in there to find out exactly which
part of the function it is crashing in.

Any way to do that with less performance impact than adding printks to what I presume is a quite-commonly-called method? This system is used by internal personnel; while its performance and uptime aren't critical, it would be a good thing if they weren't impacted more than necessary.

Also, try upgrading to 3.0-testing tip and see if you still get the problem.

Should it be adequate to upgrade this DomU only, or is there cause to also upgrade the hypervisor and Dom0?

(I'm also building a kernel with debug symbols; I anticipate that this will let me get an annotated disassembled copy of the source in question, and thus figure out which line of source maps to the instruction offset from the top of the method we're in... at least, in theory).

Xen-devel mailing list



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