* x86-64 xen broken with May4th xen-unstable build
@ 2005-05-04 22:29 Jerone Young
2005-05-06 21:57 ` David F Barrera
0 siblings, 1 reply; 7+ messages in thread
From: Jerone Young @ 2005-05-04 22:29 UTC (permalink / raw)
To: xen-devel
There are two things that happened in the May 4th build.
1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
This can easily be resolved by commenting out "c-xen-obj-
$(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
removed from i386 and no one told x86-64 about it ...that's why he
always misses the party :-)
2) When booting dom0, I can nolonger bootup and the domain crashes not
far in the bootup:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xf'(XEN) PHYSICAL
MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000010000000->0000000020000000 (62464 pages to
be allocat)(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff80519086
(XEN) Init. ramdisk: ffffffff8051a000->ffffffff8051a000
(XEN) Phys-Mach map: ffffffff8051a000->ffffffff80597000
(XEN) Page tables: ffffffff80597000->ffffffff8059e000
(XEN) Start info: ffffffff8059e000->ffffffff8059f000
(XEN) Boot stack: ffffffff8059f000->ffffffff805a0000
(XEN) TOTAL: ffffffff80000000->ffffffff80800000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Scrubbing Free RAM: ....................................done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
Xen: 0000000000000000 - 000000001f400000 (usable)
kernel direct mapping tables upto ffff88001f400000 @ 59e000-69a000
Linux version 2.6.11-xen0 (root@xen64) (gcc version 3.4.3 20050227 (Red
Hat 3.4.3-25Registering memory for bootmem: from 800000, size =
1ec00000
Built 1 zonelists
Kernel command line: ro root=/dev/sda1
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 2193.760 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 495616k/512000k available (2474k kernel code, 7872k reserved,
880k data, 40)(XEN) BUG at domain.c:136
(XEN) CPU: 0
(XEN) EIP: 0810:[<ffff830000107369>]
(XEN) EFLAGS: 0000000000010282
(XEN) rax: 0000000000000000 rbx: ffff830000ffbb00 rcx:
00000000000003f8 rdx: 6(XEN) rsi: 000000000000000a rdi:
ffff830000158474 rbp: ffff830000ff4080 rsp: 0(XEN) r8:
0000000000000036 r9: 0000000000001687 r10: 0000000000000001 r11:
5(XEN) r12: ffff830000155ea0 r13: ffff830000155e80 r14:
0000000000000000 r15: 0(XEN) Stack trace from RSP=ffff830000105f00:
(XEN) 0000000000000810 ffff830000ff4080 ffff830000ff4080
[ffff830000107459] [ff
(XEN) ffffffff80100038 ffffffff803d1c80 00000000ffff8b19
0000000000000000 ffff8
(XEN) 000000007fb67903 0000000000000002 0000000000000355
0000000000010000 00000
(XEN) ffffffff804b3f80 000000000000082b 000000000000082b
0000000000000000 00000
(XEN) Call Trace from RSP=ffff830000105f00:
(XEN) [<ffff830000107459>] [<ffff830000133f86>] [<ffff830000133ea3>]
****************************************
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
****************************************
Reboot in five seconds...
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: x86-64 xen broken with May4th xen-unstable build
@ 2005-05-04 23:11 Nakajima, Jun
2005-05-06 16:47 ` Jerone Young
0 siblings, 1 reply; 7+ messages in thread
From: Nakajima, Jun @ 2005-05-04 23:11 UTC (permalink / raw)
To: Jerone Young, xen-devel
Jerone Young wrote:
> There are two things that happened in the May 4th build.
>
> 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
> This can easily be resolved by commenting out "c-xen-obj-
> $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> removed from i386 and no one told x86-64 about it ...that's why he
> always misses the party :-)
>
>
> 2) When booting dom0, I can nolonger bootup and the domain crashes not
> far in the bootup:
Can you try debug-version of xen and show the output? (i.e. made by
"make debug=y"). I bet that xen is complaining about something. I'm
working on cleaning up the initial mapping, and that might be helpful
there (I haven't delivered anything recently yet ;-).
Jun
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xf'(XEN) PHYSICAL
> MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000010000000->0000000020000000 (62464 pages
> to be allocat)(XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: ffffffff80100000->ffffffff80519086
> (XEN) Init. ramdisk: ffffffff8051a000->ffffffff8051a000
> (XEN) Phys-Mach map: ffffffff8051a000->ffffffff80597000
> (XEN) Page tables: ffffffff80597000->ffffffff8059e000
> (XEN) Start info: ffffffff8059e000->ffffffff8059f000
> (XEN) Boot stack: ffffffff8059f000->ffffffff805a0000
> (XEN) TOTAL: ffffffff80000000->ffffffff80800000
> (XEN) ENTRY ADDRESS: ffffffff80100000
> (XEN) Scrubbing Free RAM: ....................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> Xen: 0000000000000000 - 000000001f400000 (usable)
> kernel direct mapping tables upto ffff88001f400000 @ 59e000-69a000
> Linux version 2.6.11-xen0 (root@xen64) (gcc version 3.4.3 20050227
> (Red Hat 3.4.3-25Registering memory for bootmem: from 800000, size =
> 1ec00000
> Built 1 zonelists
> Kernel command line: ro root=/dev/sda1
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 65536 bytes)
> Xen reported: 2193.760 MHz processor.
> Using tsc for high-res timesource
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Memory: 495616k/512000k available (2474k kernel code, 7872k reserved,
> 880k data, 40)(XEN) BUG at domain.c:136
> (XEN) CPU: 0
> (XEN) EIP: 0810:[<ffff830000107369>]
> (XEN) EFLAGS: 0000000000010282
> (XEN) rax: 0000000000000000 rbx: ffff830000ffbb00 rcx:
> 00000000000003f8 rdx: 6(XEN) rsi: 000000000000000a rdi:
> ffff830000158474 rbp: ffff830000ff4080 rsp: 0(XEN) r8:
> 0000000000000036 r9: 0000000000001687 r10: 0000000000000001
> r11: 5(XEN) r12: ffff830000155ea0 r13: ffff830000155e80 r14:
> 0000000000000000 r15: 0(XEN) Stack trace from RSP=ffff830000105f00:
> (XEN) 0000000000000810 ffff830000ff4080 ffff830000ff4080
> [ffff830000107459] [ff
> (XEN) ffffffff80100038 ffffffff803d1c80 00000000ffff8b19
> 0000000000000000 ffff8
> (XEN) 000000007fb67903 0000000000000002 0000000000000355
> 0000000000010000 00000
> (XEN) ffffffff804b3f80 000000000000082b 000000000000082b
> 0000000000000000 00000
> (XEN) Call Trace from RSP=ffff830000105f00:
> (XEN) [<ffff830000107459>] [<ffff830000133f86>]
> [<ffff830000133ea3>]
>
> ****************************************
> CPU0 FATAL TRAP: vector = 6 (invalid operand)
> [error_code=0000]
> Aieee! CPU0 is toast...
> ****************************************
>
> Reboot in five seconds...
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: x86-64 xen broken with May4th xen-unstable build
[not found] <mailman.1115245832.5358@unix-os.sc.intel.com>
@ 2005-05-06 0:45 ` Arun Sharma
2005-05-06 17:04 ` Jerone Young
0 siblings, 1 reply; 7+ messages in thread
From: Arun Sharma @ 2005-05-06 0:45 UTC (permalink / raw)
To: Jerone Young; +Cc: xen-devel
Jerone Young wrote:
> There are two things that happened in the May 4th build.
>
> 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
> This can easily be resolved by commenting out "c-xen-obj-
> $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> removed from i386 and no one told x86-64 about it ...that's why he
> always misses the party :-)
>
This might be a better fix?
--- 1.2/linux-2.6.11-xen-sparse/arch/xen/x86_64/pci/Makefile
2005-04-02 12:27:09 -08:00
+++ edited/linux-2.6.11-xen-sparse/arch/xen/x86_64/pci/Makefile
2005-05-05 15:43:11 -07:00
@@ -12,7 +12,7 @@
c-obj-y += fixup.o
c-obj-$(CONFIG_ACPI_PCI) += acpi.o
c-obj-y += legacy.o common.o
-c-xen-obj-$(CONFIG_PCI_DIRECT)+= direct.o
+c-obj-$(CONFIG_PCI_DIRECT)+= direct.o
c-xen-obj-y += irq.o
# mmconfig has a 64bit special
c-obj-$(CONFIG_PCI_MMCONFIG) += mmconfig.o
-Arun
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: x86-64 xen broken with May4th xen-unstable build
2005-05-04 23:11 Nakajima, Jun
@ 2005-05-06 16:47 ` Jerone Young
0 siblings, 0 replies; 7+ messages in thread
From: Jerone Young @ 2005-05-06 16:47 UTC (permalink / raw)
To: Nakajima, Jun; +Cc: xen-devel
Here is output from todays bk build with debug:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0'(XEN) PHYSICAL
MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000010000000->0000000020000000 (62464 pages to
be alloc)(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff8051b086
(XEN) Init. ramdisk: ffffffff8051c000->ffffffff8051c000
(XEN) Phys-Mach map: ffffffff8051c000->ffffffff80599000
(XEN) Page tables: ffffffff80599000->ffffffff805a0000
(XEN) Start info: ffffffff805a0000->ffffffff805a1000
(XEN) Boot stack: ffffffff805a1000->ffffffff805a2000
(XEN) TOTAL: ffffffff80000000->ffffffff80800000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Scrubbing Free RAM: ....................................done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen). Xen: 0000000000000000 - 000000001f400000 (usable)
kernel direct mapping tables upto ffff88001f400000 @ 5a0000-69c000
Linux version 2.6.11-xen0 (root@xen64) (gcc version 3.4.3 20050227 (Red
Hat 3.4.35Registering memory for bootmem: from 800000, size = 1ec00000
Built 1 zonelists
Kernel command line: ro root=/dev/sda1
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 2193.807 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 495616k/512000k available (2475k kernel code, 7872k reserved,
881k data, )(XEN) (file=traps.c, line=342) Page fault: ffff830000143405
-> ffff8300001096b0
(XEN) debugtrace_dump() starting
(XEN) debugtrace_dump() finished
(XEN) BUG at domain.c:125
(XEN) CPU: 0
(XEN) EIP: 0810:[<ffff8300001095ce>]
(XEN) EFLAGS: 0000000000010282
(XEN) rax: 0000000000000000 rbx: ffff8300001abb00 rcx:
00000000000003f8 rdxc(XEN) rsi: 000000000000000a rdi:
ffff83000016c474 rbp: 0000000000000000 rsp0(XEN) r8:
0000000000000035 r9: 0000000000002c8d r10: 0000000000000001 r11b
(XEN) r12: 00000001320a87a1 r13: ffff830000ff2080 r14:
ffff830000169e80 r150(XEN) Stack trace from RSP=ffff830000107f00:
(XEN) 0000000000000810 ffff830000ff2080 0000000000000000
[ffff8300001096b9] [
(XEN) ffffffff80100038 ffffffff803d2100 00000000ffff8b19
0000000000000000 fff
(XEN) 000000009e51942f 0000000000000002 0000000000000355
0000000000010000 000
(XEN) ffffffff804b5f80 000000000000082b 000000000000082b
0000000000000000 000
(XEN) Call Trace from RSP=ffff830000107f00:
(XEN) [<ffff8300001096b9>] [<ffff8300001433a6>] [<ffff8300001432c3>]
(XEN) debugtrace_dump() starting
(XEN) debugtrace_dump() finished
****************************************
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
****************************************
Reboot in five seconds...
On Wed, 2005-05-04 at 16:11 -0700, Nakajima, Jun wrote:
> Jerone Young wrote:
> > There are two things that happened in the May 4th build.
> >
> > 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> > symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
> > This can easily be resolved by commenting out "c-xen-obj-
> > $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> > removed from i386 and no one told x86-64 about it ...that's why he
> > always misses the party :-)
> >
> >
> > 2) When booting dom0, I can nolonger bootup and the domain crashes not
> > far in the bootup:
>
> Can you try debug-version of xen and show the output? (i.e. made by
> "make debug=y"). I bet that xen is complaining about something. I'm
> working on cleaning up the initial mapping, and that might be helpful
> there (I haven't delivered anything recently yet ;-).
>
> Jun
>
> > (XEN) *** LOADING DOMAIN 0 ***
> > (XEN) Xen-ELF header found:
> > 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xf'(XEN) PHYSICAL
> > MEMORY ARRANGEMENT:
> > (XEN) Dom0 alloc.: 0000000010000000->0000000020000000 (62464 pages
> > to be allocat)(XEN) VIRTUAL MEMORY ARRANGEMENT:
> > (XEN) Loaded kernel: ffffffff80100000->ffffffff80519086
> > (XEN) Init. ramdisk: ffffffff8051a000->ffffffff8051a000
> > (XEN) Phys-Mach map: ffffffff8051a000->ffffffff80597000
> > (XEN) Page tables: ffffffff80597000->ffffffff8059e000
> > (XEN) Start info: ffffffff8059e000->ffffffff8059f000
> > (XEN) Boot stack: ffffffff8059f000->ffffffff805a0000
> > (XEN) TOTAL: ffffffff80000000->ffffffff80800000
> > (XEN) ENTRY ADDRESS: ffffffff80100000
> > (XEN) Scrubbing Free RAM: ....................................done.
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> > input to Xen).
> > Xen: 0000000000000000 - 000000001f400000 (usable)
> > kernel direct mapping tables upto ffff88001f400000 @ 59e000-69a000
> > Linux version 2.6.11-xen0 (root@xen64) (gcc version 3.4.3 20050227
> > (Red Hat 3.4.3-25Registering memory for bootmem: from 800000, size =
> > 1ec00000
> > Built 1 zonelists
> > Kernel command line: ro root=/dev/sda1
> > Initializing CPU#0
> > PID hash table entries: 2048 (order: 11, 65536 bytes)
> > Xen reported: 2193.760 MHz processor.
> > Using tsc for high-res timesource
> > Console: colour VGA+ 80x25
> > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> > Memory: 495616k/512000k available (2474k kernel code, 7872k reserved,
> > 880k data, 40)(XEN) BUG at domain.c:136
> > (XEN) CPU: 0
> > (XEN) EIP: 0810:[<ffff830000107369>]
> > (XEN) EFLAGS: 0000000000010282
> > (XEN) rax: 0000000000000000 rbx: ffff830000ffbb00 rcx:
> > 00000000000003f8 rdx: 6(XEN) rsi: 000000000000000a rdi:
> > ffff830000158474 rbp: ffff830000ff4080 rsp: 0(XEN) r8:
> > 0000000000000036 r9: 0000000000001687 r10: 0000000000000001
> > r11: 5(XEN) r12: ffff830000155ea0 r13: ffff830000155e80 r14:
> > 0000000000000000 r15: 0(XEN) Stack trace from RSP=ffff830000105f00:
> > (XEN) 0000000000000810 ffff830000ff4080 ffff830000ff4080
> > [ffff830000107459] [ff
> > (XEN) ffffffff80100038 ffffffff803d1c80 00000000ffff8b19
> > 0000000000000000 ffff8
> > (XEN) 000000007fb67903 0000000000000002 0000000000000355
> > 0000000000010000 00000
> > (XEN) ffffffff804b3f80 000000000000082b 000000000000082b
> > 0000000000000000 00000
> > (XEN) Call Trace from RSP=ffff830000105f00:
> > (XEN) [<ffff830000107459>] [<ffff830000133f86>]
> > [<ffff830000133ea3>]
> >
> > ****************************************
> > CPU0 FATAL TRAP: vector = 6 (invalid operand)
> > [error_code=0000]
> > Aieee! CPU0 is toast...
> > ****************************************
> >
> > Reboot in five seconds...
>
>
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: x86-64 xen broken with May4th xen-unstable build
2005-05-06 0:45 ` x86-64 xen broken with May4th xen-unstable build Arun Sharma
@ 2005-05-06 17:04 ` Jerone Young
0 siblings, 0 replies; 7+ messages in thread
From: Jerone Young @ 2005-05-06 17:04 UTC (permalink / raw)
To: Arun Sharma; +Cc: xen-devel
This patch is a better fix. Use the general Linux one instead of xen's.
Could you submit this into CVS?
On Thu, 2005-05-05 at 17:45 -0700, Arun Sharma wrote:
> Jerone Young wrote:
> > There are two things that happened in the May 4th build.
> >
> > 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> > symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
> > This can easily be resolved by commenting out "c-xen-obj-
> > $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> > removed from i386 and no one told x86-64 about it ...that's why he
> > always misses the party :-)
> >
>
> This might be a better fix?
>
> --- 1.2/linux-2.6.11-xen-sparse/arch/xen/x86_64/pci/Makefile
> 2005-04-02 12:27:09 -08:00
> +++ edited/linux-2.6.11-xen-sparse/arch/xen/x86_64/pci/Makefile
> 2005-05-05 15:43:11 -07:00
> @@ -12,7 +12,7 @@
> c-obj-y += fixup.o
> c-obj-$(CONFIG_ACPI_PCI) += acpi.o
> c-obj-y += legacy.o common.o
> -c-xen-obj-$(CONFIG_PCI_DIRECT)+= direct.o
> +c-obj-$(CONFIG_PCI_DIRECT)+= direct.o
> c-xen-obj-y += irq.o
> # mmconfig has a 64bit special
> c-obj-$(CONFIG_PCI_MMCONFIG) += mmconfig.o
>
> -Arun
>
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: x86-64 xen broken with May4th xen-unstable build
2005-05-04 22:29 Jerone Young
@ 2005-05-06 21:57 ` David F Barrera
0 siblings, 0 replies; 7+ messages in thread
From: David F Barrera @ 2005-05-06 21:57 UTC (permalink / raw)
To: xen-devel
Jerone,
I am seeing the same thing you reported on an HS20 (EMT64).
David
On Wed, 2005-05-04 at 17:29 -0500, Jerone Young wrote:
> There are two things that happened in the May 4th build.
>
> 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
> This can easily be resolved by commenting out "c-xen-obj-
> $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> removed from i386 and no one told x86-64 about it ...that's why he
> always misses the party :-)
>
>
> 2) When booting dom0, I can nolonger bootup and the domain crashes not
> far in the bootup:
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xf'(XEN) PHYSICAL
> MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000010000000->0000000020000000 (62464 pages to
> be allocat)(XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: ffffffff80100000->ffffffff80519086
> (XEN) Init. ramdisk: ffffffff8051a000->ffffffff8051a000
> (XEN) Phys-Mach map: ffffffff8051a000->ffffffff80597000
> (XEN) Page tables: ffffffff80597000->ffffffff8059e000
> (XEN) Start info: ffffffff8059e000->ffffffff8059f000
> (XEN) Boot stack: ffffffff8059f000->ffffffff805a0000
> (XEN) TOTAL: ffffffff80000000->ffffffff80800000
> (XEN) ENTRY ADDRESS: ffffffff80100000
> (XEN) Scrubbing Free RAM: ....................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> Xen: 0000000000000000 - 000000001f400000 (usable)
> kernel direct mapping tables upto ffff88001f400000 @ 59e000-69a000
> Linux version 2.6.11-xen0 (root@xen64) (gcc version 3.4.3 20050227 (Red
> Hat 3.4.3-25Registering memory for bootmem: from 800000, size =
> 1ec00000
> Built 1 zonelists
> Kernel command line: ro root=/dev/sda1
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 65536 bytes)
> Xen reported: 2193.760 MHz processor.
> Using tsc for high-res timesource
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Memory: 495616k/512000k available (2474k kernel code, 7872k reserved,
> 880k data, 40)(XEN) BUG at domain.c:136
> (XEN) CPU: 0
> (XEN) EIP: 0810:[<ffff830000107369>]
> (XEN) EFLAGS: 0000000000010282
> (XEN) rax: 0000000000000000 rbx: ffff830000ffbb00 rcx:
> 00000000000003f8 rdx: 6(XEN) rsi: 000000000000000a rdi:
> ffff830000158474 rbp: ffff830000ff4080 rsp: 0(XEN) r8:
> 0000000000000036 r9: 0000000000001687 r10: 0000000000000001 r11:
> 5(XEN) r12: ffff830000155ea0 r13: ffff830000155e80 r14:
> 0000000000000000 r15: 0(XEN) Stack trace from RSP=ffff830000105f00:
> (XEN) 0000000000000810 ffff830000ff4080 ffff830000ff4080
> [ffff830000107459] [ff
> (XEN) ffffffff80100038 ffffffff803d1c80 00000000ffff8b19
> 0000000000000000 ffff8
> (XEN) 000000007fb67903 0000000000000002 0000000000000355
> 0000000000010000 00000
> (XEN) ffffffff804b3f80 000000000000082b 000000000000082b
> 0000000000000000 00000
> (XEN) Call Trace from RSP=ffff830000105f00:
> (XEN) [<ffff830000107459>] [<ffff830000133f86>] [<ffff830000133ea3>]
>
> ****************************************
> CPU0 FATAL TRAP: vector = 6 (invalid operand)
> [error_code=0000]
> Aieee! CPU0 is toast...
> ****************************************
>
> Reboot in five seconds...
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: x86-64 xen broken with May4th xen-unstable build
@ 2005-05-10 2:14 Nakajima, Jun
0 siblings, 0 replies; 7+ messages in thread
From: Nakajima, Jun @ 2005-05-10 2:14 UTC (permalink / raw)
To: David F Barrera, xen-devel
This is a side-effect of having full ACPI/PCI support in dom0 (enabled
on x86 first), and Arun and I are working on 2).
Jun
-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of David F
Barrera
Sent: Friday, May 06, 2005 2:58 PM
To: xen-devel
Subject: Re: [Xen-devel] x86-64 xen broken with May4th xen-unstable
build
Jerone,
I am seeing the same thing you reported on an HS20 (EMT64).
David
On Wed, 2005-05-04 at 17:29 -0500, Jerone Young wrote:
> There are two things that happened in the May 4th build.
>
> 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
> This can easily be resolved by commenting out "c-xen-obj-
> $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> removed from i386 and no one told x86-64 about it ...that's why he
> always misses the party :-)
>
>
> 2) When booting dom0, I can nolonger bootup and the domain crashes not
> far in the bootup:
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xf'(XEN) PHYSICAL
> MEMORY ARRANGEMENT:
> (XEN) Dom0 alloc.: 0000000010000000->0000000020000000 (62464 pages
to
> be allocat)(XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) Loaded kernel: ffffffff80100000->ffffffff80519086
> (XEN) Init. ramdisk: ffffffff8051a000->ffffffff8051a000
> (XEN) Phys-Mach map: ffffffff8051a000->ffffffff80597000
> (XEN) Page tables: ffffffff80597000->ffffffff8059e000
> (XEN) Start info: ffffffff8059e000->ffffffff8059f000
> (XEN) Boot stack: ffffffff8059f000->ffffffff805a0000
> (XEN) TOTAL: ffffffff80000000->ffffffff80800000
> (XEN) ENTRY ADDRESS: ffffffff80100000
> (XEN) Scrubbing Free RAM: ....................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> Xen: 0000000000000000 - 000000001f400000 (usable)
> kernel direct mapping tables upto ffff88001f400000 @ 59e000-69a000
> Linux version 2.6.11-xen0 (root@xen64) (gcc version 3.4.3 20050227
(Red
> Hat 3.4.3-25Registering memory for bootmem: from 800000, size =
> 1ec00000
> Built 1 zonelists
> Kernel command line: ro root=/dev/sda1
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 65536 bytes)
> Xen reported: 2193.760 MHz processor.
> Using tsc for high-res timesource
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Memory: 495616k/512000k available (2474k kernel code, 7872k reserved,
> 880k data, 40)(XEN) BUG at domain.c:136
> (XEN) CPU: 0
> (XEN) EIP: 0810:[<ffff830000107369>]
> (XEN) EFLAGS: 0000000000010282
> (XEN) rax: 0000000000000000 rbx: ffff830000ffbb00 rcx:
> 00000000000003f8 rdx: 6(XEN) rsi: 000000000000000a rdi:
> ffff830000158474 rbp: ffff830000ff4080 rsp: 0(XEN) r8:
> 0000000000000036 r9: 0000000000001687 r10: 0000000000000001
r11:
> 5(XEN) r12: ffff830000155ea0 r13: ffff830000155e80 r14:
> 0000000000000000 r15: 0(XEN) Stack trace from RSP=ffff830000105f00:
> (XEN) 0000000000000810 ffff830000ff4080 ffff830000ff4080
> [ffff830000107459] [ff
> (XEN) ffffffff80100038 ffffffff803d1c80 00000000ffff8b19
> 0000000000000000 ffff8
> (XEN) 000000007fb67903 0000000000000002 0000000000000355
> 0000000000010000 00000
> (XEN) ffffffff804b3f80 000000000000082b 000000000000082b
> 0000000000000000 00000
> (XEN) Call Trace from RSP=ffff830000105f00:
> (XEN) [<ffff830000107459>] [<ffff830000133f86>]
[<ffff830000133ea3>]
>
> ****************************************
> CPU0 FATAL TRAP: vector = 6 (invalid operand)
> [error_code=0000]
> Aieee! CPU0 is toast...
> ****************************************
>
> Reboot in five seconds...
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2005-05-10 2:14 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <mailman.1115245832.5358@unix-os.sc.intel.com>
2005-05-06 0:45 ` x86-64 xen broken with May4th xen-unstable build Arun Sharma
2005-05-06 17:04 ` Jerone Young
2005-05-10 2:14 Nakajima, Jun
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 23:11 Nakajima, Jun
2005-05-06 16:47 ` Jerone Young
2005-05-04 22:29 Jerone Young
2005-05-06 21:57 ` David F Barrera
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.