From: Charles Duffy <cduffy@spamcop.net>
To: xen-devel@lists.xensource.com
Subject: Re: Oops in xen 3.0.2 dequeue_signal [was: Re: DomU Oopsing on xen-3.0-testing changeset 8259]
Date: Mon, 26 Jun 2006 16:15:24 -0500 [thread overview]
Message-ID: <44A04E6C.9020501@spamcop.net> (raw)
In-Reply-To: <49d22db6cf52e95faf921257860e9a0a@cl.cam.ac.uk>
Keir Fraser wrote:
> Does it always crash in __dequeue_signal()?
Yes.
> 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).
next prev parent reply other threads:[~2006-06-26 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 19:03 DomU Oopsing on xen-3.0-testing changeset 8259 Charles Duffy
2006-06-19 13:12 ` Oops in xen 3.0.2 dequeue_signal [was: Re: DomU Oopsing on xen-3.0-testing changeset 8259] Charles Duffy
2006-06-19 13:59 ` Keir Fraser
2006-06-26 21:15 ` Charles Duffy [this message]
2006-07-18 20:20 ` Charles Duffy
2006-06-19 14:00 ` Keir Fraser
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=44A04E6C.9020501@spamcop.net \
--to=cduffy@spamcop.net \
--cc=xen-devel@lists.xensource.com \
/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.