All of lore.kernel.org
 help / color / mirror / Atom feed
* Call Trace after insertion of modules
@ 2012-03-23 17:43 Nupur Ghatnekar
  2012-04-16 14:25 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 2+ messages in thread
From: Nupur Ghatnekar @ 2012-03-23 17:43 UTC (permalink / raw)
  To: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 358 bytes --]

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?

-- 

Nupur Ghatnekar

[-- Attachment #1.2: Type: text/html, Size: 407 bytes --]

[-- Attachment #2: Screenshot at 2012-03-23 23:08:37.png --]
[-- Type: image/png, Size: 162513 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-04-16 14:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-23 17:43 Call Trace after insertion of modules Nupur Ghatnekar
2012-04-16 14:25 ` Konrad Rzeszutek Wilk

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.