From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Call Trace after insertion of modules Date: Mon, 16 Apr 2012 10:25:27 -0400 Message-ID: <20120416142527.GC1903@phenom.dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Nupur Ghatnekar , konrad.wilk@oracle.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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