[Xen-bugs] [Bug 150] Unknown interrupt on x86_64 Xen on ES7000 x86_64

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=150





------- Additional Comments From aravindh.puthiyaparambil@xxxxxxxxxx  
2005-08-10 19:27 -------
> 
> I found out that the "Unknown Interrupt" issue happens only when debug 
> is turned on in Xen (verbose & debug=y in Rules.mk). When debug is 
> turned off the systems dies in the middle of "Scrubbing Free RAM". I 
> have attached a serial output of the boot messages 
> (es7000_x86_64_nodebug_6065.txt). This could be Bugzilla #147.
> Should I be still trying to find the faulting address in the debug 
> case?
> 
I have the same problem "Unknown Interrupt" on a DP machine. Looks like #PF is
happening at => when xen is built with debug=y.

static void map_alloc(unsigned long first_page, unsigned long nr_pages) {
    ...
    curr_idx  = first_page / PAGES_PER_MAPWORD;
    start_off = first_page & (PAGES_PER_MAPWORD-1);
    end_idx   = (first_page + nr_pages) / PAGES_PER_MAPWORD;
    end_off   = (first_page + nr_pages) & (PAGES_PER_MAPWORD-1);

    if ( curr_idx == end_idx )
    {
        alloc_bitmap[curr_idx] &= -(1UL<<end_off) | ((1UL<<start_off)-1);
    }
    else
    {
        alloc_bitmap[curr_idx] &= (1UL<<start_off)-1;
        while ( ++curr_idx != end_idx ) alloc_bitmap[curr_idx] = 0;
 =>       alloc_bitmap[curr_idx] &= -(1UL<<end_off);
    }
}

If I change 
        while ( ++curr_idx != end_idx - 1 ) alloc_bitmap[curr_idx] = 0; I can
work around it.

Jun


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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