From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nupur Ghatnekar <nupurghatnekar@gmail.com>, konrad.wilk@oracle.com
Cc: xen-devel@lists.xensource.com
Subject: Re: Call Trace after insertion of modules
Date: Mon, 16 Apr 2012 10:25:27 -0400 [thread overview]
Message-ID: <20120416142527.GC1903@phenom.dumpdata.com> (raw)
In-Reply-To: <CAO8_4VqSr_jdN+pkgoA_sxmtDsQzvJ+8U=tLqtqHYtRjzqcoPQ@mail.gmail.com>
On Fri, Mar 23, 2012 at 11:13:03PM +0530, Nupur Ghatnekar wrote:
> Hello,
>
> I have written a small split device driver which caters to xenbus devices...
> attached is the call trace i got in the frontend driver.
> all i did was, inform the frontend when the backend was probed. after that,
> i got the attached call trace.
> Sorry i cant print it.. its looping continuously.
> Can you help me with debugging this?
You can post the driver - that might give us an idea what is wrong.
>
> --
>
> Nupur Ghatnekar
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-04-16 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 17:43 Call Trace after insertion of modules Nupur Ghatnekar
2012-04-16 14:25 ` Konrad Rzeszutek Wilk [this message]
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=20120416142527.GC1903@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=nupurghatnekar@gmail.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 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.