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

Re: [Xen-users] xen 3.0 amd64 crash... seems to be tied into disk i/o,> 4 gig ram





Tom Brown wrote:
On Tue, 13 Dec 2005, Matt Ayres wrote:


Tom Brown wrote:
I just posted a followup comment on bug # 405...  what are you using for a
motherboard?

I use Tyan S881 and S882 motherboards.

I'm not getting any hits on google for "Tyan S881" ... ahh, s4881 and
s4882 ... that 4 makes a difference :)

hhmm, looks like that will likely have the same fragmented memory layout
that the supermicro's have, as each processor has locally attached memory.

ever tried to boot one of these without a 64bit or pae kernel? Does it
only see 1/4 of the memory? what does the boot time memory map look like?
e.g. (from dmesg)

BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable)
 BIOS-e820: 00000000bfff0000 - 00000000bffff000 (ACPI data)
 BIOS-e820: 00000000bffff000 - 00000000c0000000 (ACPI NVS)
 BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000140000000 (usable)

My second memory bank starts at 0x0000000100000000, which is 2^32
(4gig)


I have posted another panic to bug #402. I have everything so if Ian or another developer wants more info I have the vmlinux/System.map/config available.

My board shows:
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000020000000 (usable)


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


 


Rackspace

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