On Thu, 2010-10-07 at 10:57 +0100, Alan J. Wylie wrote:
> System: Supermicro SM-SC825TQ-R720LPB, 8GB RAM
> Motherboard: X8DTL
> Processor: 1 x Intel XEON E5506 quad core
> RAID controller: LSI MegaRAID SAS 8708
> Bisected (by hand) to between
> 69e50db2 (good) 22.214.171.124 "Merge commit 'v126.96.36.199' into xen/next-2.6.32"
> dda56688 (bad) "Merge branch 'xen/next' into xen/next-2.6.32"
> I don't know if it is of any relevance, but lshw hangs during DMI.
> The end of the strace is:
> mmap(NULL, 4080, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182228000
> munmap(0x7fc182228000, 4080) = 0
> mmap(NULL, 4096, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182228000
> munmap(0x7fc182228000, 4096) = 0
> mmap(NULL, 4112, PROT_READ, MAP_SHARED, 3, 0xff000) = 0x7fc182227000
> ^C--- SIGINT (Interrupt) @ 0 (0) ---
> and XEN then outputs large numbers of the following message:
> (XEN) mm.c:860:d0 Error getting mfn 15b3 (pfn 21973) from L1 entry
> 80000000015b3625 for l1e_owner=0, pg_owner=32753
> This patch to LSHW stops it hanging, the output of this lshw can be
> found later in this e-mail, along with grub.conf, /proc/cpuinfo, lshw,
> dmidecode and the console output for a crash and a good boot.
> diff -Nau -r lshw-B.02.14/src/core/dmi.cc
> --- lshw-B.02.14/src/core/dmi.cc 2009-02-12 22:53:09.000000000 +0000
> +++ lshw-B.02.14.patched/src/core/dmi.cc 2010-10-07 08:56:46.000000000
> @@ -1725,7 +1725,7 @@
> fp -= 16;
> - while (efi || (fp < 0xFFFFF))
> + while (efi || (fp < 0xFFFE0))
> fp += 16;
> mmoffset = fp % getpagesize();
> I've attempted to disassemble what I believe to be the crashing code:
> (XEN) RIP: e033:[<ffffffff8100bd47>]
> From System.map:
> ffffffff8100bd10 T get_phys_to_machine
> ffffffff8100bd4c t pin_pagetable_pfn
I see this exact same crash however, for me, it happens immediately at
boot, ie. xen crash starting dom0 in setup.S and reboot in 5 seconds. I
have tried all sorts of config fiddling and nothing seems to get it to
the stage of a printk from linux.
Only the XCP kernel gives me a functioning dom0 on this machine.
I don't really know what to suspect here - in my case it's possibly more
than one issue.
Xen-devel mailing list