Re: [Xen-devel] network_alloc_rx_buffers panic

[Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>]

> 
> " Could you try updating to the latest version, with writable pagetables
> " reenabled.  Keir has spotted an incorrect check in the writable
> 
> xen is faulting the same as the previous pull.
> 
> objdump shows the fault address 0xfc52f5b4 in the same function as
> the previous pull.

The page faults that are getting logged may well turn out to be
harmless. However, it would be interesting to see the call trace
leading up to the page fault, so that we can see what's causing
it.

Please could you add something akin to the following to the
relevant printk:

{
        extern void show_trace(unsigned long *esp);             
        unsigned long *esp;
        __asm__ __volatile__ ("movl %%esp,%0" : "=r" (esp) : );
        show_trace(esp);
}

It would be very useful to see the panic message coming out of
the domain. If you leave an 'xm console' connected to the domain
there's a good chance that you'll capture it.

Thanks,
Ian


-------------------------------------------------------
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel