Re: [Xen-devel] Kernel panic while compiling kernel

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

> On Thursday 12 February 2004 10:44, Keir Fraser wrote:
> > Whoops. I forgot that in Xen 1.2, to get useful memory debugging you
> > will need to edit common/memory.c and enable MEM_LOG() (change '#if 0'
> > to '#if 1').
> 
> There were two compilation issues in that file after enablig that, I 
> quick-fixed id by adding two dummy parameteres (and formats) to the two 
> offending lines. Those were ones in form of MSG_LOG("text and no parms");
> 
> > I'll try to find some time to do a bit of testing myself today.
> 
> If it saves you some testing time here is the log with MSG_LOG turned on, 
> runlevel editor did the trick in DOM0 (didn't start other domain this time).

Okay, that could be useful.

Perhaps you could add the follwoing (I assume you knwo a bit of C):
 1. Extend the "Pfn already pinned" message to include every field in
 the page structure (e.g., page->flags, page->type_count, and so on).

 2. At the start of the switch case MMUEXT_PIN_L2_TABLE, add
    printk(" ********* L2 pin pfn == %08lx\n", pfn);

 3. At teh start o fthe switch case MMUEXT_UNPIN_TABLE, add
    if ( (page->flags & PG_type_mask) == PGT_l2_page_table )
      printk(" ********* L2 unpin pfn == %08lx\n", pfn);

This should let us see whether this is a Xenolinux or a Xen problem.

 -- Keir


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel