From: Jeremy Fitzhardinge <jeremy@goop.org>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: So I tried to use xentrace...
Date: Fri, 07 May 2010 22:03:04 -0700 [thread overview]
Message-ID: <4BE4F088.8040008@goop.org> (raw)
In-Reply-To: <4BE48332.6040209@eu.citrix.com>
On 05/07/2010 02:16 PM, George Dunlap wrote:
> Jeremy Fitzhardinge wrote:
>>>> (XEN) ----[ Xen-4.1-unstable x86_64 debug=y Not tainted ]----
>>>> (XEN) CPU: 1
>>>> (XEN) RIP: e008:[<ffff82c4801215b3>] check_lock+0x1b/0x45
>>>>
>>
>> This suggests the problem is with misusing a lock in the wrong interrupt
>> context, rather than anything to do with sizes.
>>
> Except that, it works for me if I use -S 32, and doesn't if I use -S
> 512 (on my 2-core box, equivalent # of pages to -S 256 on your 4-core
> box). :-) Try it, I suspect it will work.
Yes, it does. But I'm seeing some pretty odd things while xentrace is
running: first time all my SATA drives stopped responding, and the
second time my ethernet device started getting tx watchdog timeouts.
Perhaps the large amount of IO caused by xentrace is causing other bugs
to become apparent, but this has been an otherwise very stable system...
J
next prev parent reply other threads:[~2010-05-08 5:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 21:34 So I tried to use xentrace Jeremy Fitzhardinge
2010-04-30 21:43 ` Keir Fraser
2010-05-03 20:36 ` George Dunlap
2010-05-07 20:48 ` George Dunlap
2010-05-07 20:59 ` Jeremy Fitzhardinge
2010-05-07 21:16 ` George Dunlap
2010-05-08 5:03 ` Jeremy Fitzhardinge [this message]
2010-05-11 18:56 ` George Dunlap
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=4BE4F088.8040008@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).