Re: early exception error

On Mon, 5 Jan 2009, Yinghai Lu wrote:

this seems to have solved the problem

can you post boot log and lspci -vvxxx ?

I will do this tomorrow


I do have another of these systems if there is any desire to do any more
troubleshooting (it would be really nice if things died with a better error
message for example)

good,
0. setup serial cable between your two system. use minicom in your
first system to capture serial message from second system
1. apply attached patch
2. we need full boot log of your second system. please boot with "
debug console=uart8250,io,0x3f8,115200n8 pci=earlydump"

it will take me a little bit of time to do this. the one I've been working with is now my desktop at work, now that the holidays are over I need to work with it instead of rebooting it, the other boxes are in a stack at home. getting at them is easy compared to figuring out where to set them up. I should have something setup within a couple of days.

David LangFrom: Yinghai Lu <yhlu.kernel@xxxxxxxxx>
Subject: [PATCH] mm: print out info about adding/removing active region

Signed-off-by: Yinghai Lu <yhlu.kernel@xxxxxxxxx>

---
mm/page_alloc.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)

Index: linux-2.6/mm/page_alloc.c
===================================================================
--- linux-2.6.orig/mm/page_alloc.c
+++ linux-2.6/mm/page_alloc.c
@@ -3626,8 +3626,7 @@ void __init add_active_range(unsigned in
{
int i;

- mminit_dprintk(MMINIT_TRACE, "memory_register",
- "Entering add_active_range(%d, %#lx, %#lx) "
+ printk(KERN_DEBUG "Adding active range (%d, %#lx, %#lx) "
"%d entries of %d used\n",
nid, start_pfn, end_pfn,
nr_nodemap_entries, MAX_ACTIVE_REGIONS);
@@ -3689,7 +3688,7 @@ void __init remove_active_range(unsigned
int i, j;
int removed = 0;

- printk(KERN_DEBUG "remove_active_range (%d, %lu, %lu)\n",
+ printk(KERN_DEBUG "Removing active range (%d, %#lx, %#lx)\n",
nid, start_pfn, end_pfn);

/* Find the old active region end and shrink */