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

Re: [Xen-devel] Xen0 crash dump (/dev/ram0 root) possibly of interest



Looks to me like it should work -- you have enough contiguous RAM to
store the initrd image. I just checked in new heap-initialisation code
that takes into account the e820 memory map. I think there may still
be a few bugs in it and you may be triggering one. It is worth trying
a debug build of Xen and seeing if that gives any more info about the
crash.

 -- Keir

> I'm continuing to work on making a new XenCD as previously discussed here.  
> In 
> the course of that work, I've generated (actually, currently stuck on) the 
> enclosed crash dump.  Thought I'd forward it for interest.
> 
> To head off questions, you'll see references to a very large initrd (~114 
> Mb). 
>     The Xen dump may or not be related to this unusual usage.  I've done both 
> large initrds, small initrds, and small initrds in the past which copy larger 
> filesystems to tmpfs.  I've done huge initrds with success before, outside of 
> Xen.  The numbers below are calculated automatically and should be big 
> enough, 
> though may not be aligned properly.
> 
> Mark Williamson: if you see this, could you forward me a copy of the Xen 1.2 
> CD you offered to do earlier?  I'd like to see to see which initrd techniques 
> you used, if any.
> 
> My GRUB config looks like:
> 
> title xen
> kernel /boot/xen dom0_mem=318464 com1=115200,8n1 console=com1,vga 
> ignorebiostables nmi=ignore sched=bvt conswitch=xy noreboot
> module /boot/xen0-vmlinuz ramdisk_size=203776 root=/dev/ram0 max_loop=96 rw 
> console=ttyS0 vga=extended
> module /boot/xen0-initrd
> 
> I can provide access to the ISO if anyone cares, though it's obviously 
> non-functional currently.
> 
>   __  __            ____    ___
>   \ \/ /___ _ __   |___ \  / _ \
>    \  // _ \ '_ \    __) || | | |
>    /  \  __/ | | |  / __/ | |_| |
>   /_/\_\___|_| |_| |_____(_)___/
> 
>   http://www.cl.cam.ac.uk/netos/xen
>   University of Cambridge Computer Laboratory
> 
>   Xen version 2.0 (jared@xxxxxxxxxxx) (gcc version 3.3.4 20040623 (Gentoo 
> Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) Thu Dec 30 10:51:11 PST 2004
>   Latest ChangeSet: 2004/12/30 18:27:27 1.1624 41d4488f9fINTxUzyjoq2FnTn5AvMQ
> 
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009f800 (usable)
> (XEN)  000000000009f800 - 00000000000a0000 (reserved)
> (XEN)  00000000000ca000 - 00000000000cc000 (reserved)
> (XEN)  00000000000dc000 - 00000000000e0000 (reserved)
> (XEN)  00000000000e4000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 000000001eef0000 (usable)
> (XEN)  000000001eef0000 - 000000001eefc000 (ACPI data)
> (XEN)  000000001eefc000 - 000000001ef00000 (ACPI NVS)
> (XEN)  000000001ef00000 - 000000001f000000 (usable)
> (XEN)  00000000fec00000 - 00000000fec10000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000fffe0000 - 0000000100000000 (reserved)
> (XEN) System RAM: 495MB (507452kB)
> (XEN) Xen heap: 10MB (10776kB)
> (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
> (XEN) CPU#0: Hyper-Threading is disabled
> (XEN) CPU caps: bfebfbff 00000000 00000000 00000000
> (XEN) Using scheduler: Borrowed Virtual Time (bvt)
> (XEN) Initializing CPU#0
> (XEN) Detected 1197.895 MHz processor.
> (XEN) Found and enabled local APIC!
> (XEN) enabled ExtINT on CPU#0
> (XEN) ESR value before enabling vector: 00000000
> (XEN) ESR value after enabling vector: 00000000
> (XEN) Using local APIC timer interrupts.
> (XEN) Calibrating APIC timer for CPU0...
> (XEN) ..... CPU speed is 1197.8705 MHz.
> (XEN) ..... Bus speed is 69.3984 MHz.
> (XEN) ..... bus_scale = 0x00004711
> (XEN) Time init:
> (XEN) .... System Time: 1451424ns
> (XEN) .... cpu_freq:    00000000:47666D94
> (XEN) .... scale:       00000001:AB6A9983
> (XEN) .... Wall Clock:  1104628571s 10000us
> (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfd9a0, last bus=1
> (XEN) PCI: Using configuration type 1
> (XEN) PCI: Probing PCI hardware
> (XEN) PCI: Probing PCI hardware (bus 00)
> (XEN) PCI: Using IRQ router PIIX/ICH [8086/7110] at 00:07.0
> (XEN) PCI: Cannot allocate resource region 4 of device 00:07.1
> (XEN) Limiting direct PCI/PCI transfers.
> (XEN) mtrr: v2.0 (20020519)
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found: 
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Kernel image:  00c00000->00ffcd48
> (XEN)  Initrd image:  00ffd000->08bbb000
> (XEN)  Dom0 alloc.:   08c00000->1c300000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: c0100000->c052a584
> (XEN)  Init. ramdisk: c052b000->c80e9000
> (XEN)  Phys-Mach map: c80e9000->c8136c00
> (XEN)  Page tables:   c8137000->c8159000
> (XEN)  Start info:    c8159000->c815a000
> (XEN)  Boot stack:    c815a000->c815b000
> (XEN)  TOTAL:         c0000000->c8400000
> (XEN)  ENTRY ADDRESS: c0100000
> (XEN) Scrubbing DOM0 RAM: ....done.
> (XEN) Initrd len 0x7bbe000, start at 0xc052b000
> (XEN) Scrubbing Free RAM: ......done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-x' three times to switch input to 
> Xen).
> Linux version 2.6.10-xen0 (jared@bear) (gcc version 3.3.4 20040623 (Gentoo 
> Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #1 Thu Dec 30 11:13:55 PST 2004
> BIOS-provided physical RAM map:
>   Xen: 0000000000000000 - 0000000013700000 (usable)
> 311MB LOWMEM available.
> DMI not present.
> Built 1 zonelists
> Kernel command line: ramdisk_size=203776 root=/dev/ram0 max_loop=96 rw 
> console=ttyS0 vga=extended
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 32768 bytes)
> Xen reported: 1197.895 MHz processor.
> Using tsc for high-res timesource
> Console: colour VGA+ 80x25
> (XEN) BUG at domain.c:152
> (XEN) CPU:    0
> (XEN) EIP:    0808:[<fc50603e>]
> (XEN) EFLAGS: 00201296
> (XEN) eax: 00000000   ebx: fc5fd9e0   ecx: 00000000   edx: fc4b8f00
> (XEN) esi: 000d98f0   edi: c04f5200   ebp: 00000000   esp: fc503f9c
> (XEN) ds: 0810   es: 0810   fs: 0810   gs: 0810   ss: 0810
> (XEN) Stack trace from ESP=fc503f9c:
> (XEN) fc529841 fc529882 00000098 000d98f0 [fc527ae6] 00000808 fc5fd9e0 
> 00000000
> (XEN)        00000001 00000000 c8159200 c04f5200 00000000 00020000 000d98f0 
> 00000061
> (XEN)        000098f0 00201246 c04a1fb4 00000069 0000007b 0000007b 00000000 
> 00000000
> (XEN)        fc5fd9e0
> (XEN) Call Trace from ESP=fc503f9c: [<fc527ae6>]
> 
> ****************************************
> CPU0 FATAL TRAP: vector = 6 (invalid operand)
> [error_code=0000]
> Aieee! CPU0 is toast...
> ****************************************
> 
> Reboot in five seconds...
> (XEN) Reboot disabled on cmdline: require manual reset
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel


 


Rackspace

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