[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] BUG at domain.c:144


  • To: "Christopher S. Aker" <caker@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Fri, 8 Apr 2005 09:00:45 +0100
  • Delivery-date: Fri, 08 Apr 2005 08:00:41 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcU7+PtyJA6fPYAwRt6KxWogkiFBhQAFnquQ
  • Thread-topic: [Xen-devel] BUG at domain.c:144

> 1.1784 - BUGs
> 1.1779 - BUGs
> 1.1777 - BUGs
> 1.1774 - boots correctly
> 
> There are only four changesets between 1.1774 and 1.1777, and 
> of course one of them is huge -- the 2.6.11 merge.  Also, the 
> objdump didn't tell me anything useful.  I have the objdump 
> and the stack trace if anyone wants them.  I think I'm at the 
> end of my abilities to narrow it down any further.

Thanks Chris, this is very useful.

It would be helpful if you could use a debug=y build of Xen and add a
show_guest_stack() just before the BUG(). Further, it might be revealing
to hack the following into linux-2.6.11-xen0/kernel/printk.c:vprintk to
see how far the dom0 boot it is getting.

        /* Emit the output into the temporary buffer */
        printed_len = vscnprintf(printk_buf, sizeof(printk_buf), fmt,
args);
+ HYPERVISOR_console_io( CONSOLEIO_write, strlen(printk_buf),
printk_buf))

Is there anything 'unusual' about the machine you're using?

Thanks,
Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.