From: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
To: David Becker <becker@cs.duke.edu>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, xen-devel@lists.sourceforge.net
Subject: Re: network_alloc_rx_buffers panic
Date: Thu, 23 Sep 2004 21:47:57 +0100 [thread overview]
Message-ID: <20040923204757.GD21242@cl.cam.ac.uk> (raw)
In-Reply-To: <20040923204152.GN921@cs.duke.edu>
On Thu, Sep 23, 2004 at 04:41:52PM -0400, David Becker wrote:
>
> " debugging in the Xen buil dthen you may get soem useful diagnostic
> " info.
>
> I dunno if its useful, but after xenU panics the output in xm dmesg now
> has this line repeated for the length of the dmesg buffer:
>
> 0 (XEN) (file=traps.c, line=399) Page fault: fc52e2a4 -> fc52e2a6
This is most likely a get_user or put_user faulting. Could you
run gdb on your xen image and then check which function these addresses
are in: disas 0xfc52e2a4 will tell you...
christian
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next prev parent reply other threads:[~2004-09-23 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 13:08 network_alloc_rx_buffers panic David Becker
2004-09-23 13:47 ` Keir Fraser
2004-09-23 20:41 ` David Becker
2004-09-23 20:47 ` Christian Limpach [this message]
2004-09-23 21:03 ` David Becker
2004-09-23 22:07 ` Ian Pratt
2004-09-23 22:21 ` Ian Pratt
2004-09-24 13:28 ` David Becker
2004-09-24 15:05 ` Christian Limpach
2004-09-26 1:45 ` David Becker
2004-09-26 9:15 ` Ian Pratt
2004-09-26 12:20 ` David Becker
2004-09-26 16:07 ` Keir Fraser
2004-09-28 10:05 ` Christian Limpach
2004-09-28 10:23 ` Keir Fraser
2004-09-28 11:29 ` David Becker
2004-09-23 14:03 ` Mark A. Williamson
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=20040923204757.GD21242@cl.cam.ac.uk \
--to=christian.limpach@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=becker@cs.duke.edu \
--cc=xen-devel@lists.sourceforge.net \
/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.