thr3ads.net - Xen devel - [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86

If this information is useful, please help other people find it:
Share via:

Puthiyaparambil, Aravindh

2005-Aug-08 18:10 UTC

[Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

I am getting an "Unknown Interrupt" message with changeset 6050 on the
ES7000 x86_64 box running x86_64 SLES9 SP2 RC3. The system dies after
that. Any idea why this could be happening?
I am not sure if this is related to
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=122.

When I tried the same changeset on my Dell PowerEdge 470 box I am seeing
something totally different and very scary :-)
Is anybody else seeing this?

I have included both serial console outputs.

Thanks,
Aravindh

------------------------------------------------------------------------
ES7000 x86_64

 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ ''_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0-devel (root@) (gcc version 3.3.3 (SuSE Linux)) Mon Aug
8 18:21:36 EDT 2005
 Latest ChangeSet: Mon Aug  8 10:39:29 2005
f586b9ecd47476357b685707e21c7fc274cbd51c

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009dc00 (usable)
(XEN)  000000000009dc00 - 00000000000a0000 (reserved)
(XEN)  00000000000ce000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000037ea0000 (usable)
(XEN)  0000000037ea0000 - 0000000037edf000 (ACPI data)
(XEN)  0000000037edf000 - 0000000037f00000 (ACPI NVS)
(XEN)  0000000037f00000 - 00000000e8000000 (usable)
(XEN)  00000000f8000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000110000000 (usable)
(XEN) System RAM: 3967MB (4062452kB)
(XEN) Xen heap: 14MB (14544kB)
(XEN) Unknown interrupt


------------------------------------------------------------------------
--
Dell PowerEdge 470

__  __            _____  ___         _                _
 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ ''_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0-devel (root@) (gcc version 3.3.3 (SuSE Linux)) Mon Aug
8 13:53
:19 EDT 2005
 Latest ChangeSet: Mon Aug  8 10:39:29 2005
f586b9ecd47476357b685707e21c7fc274cbd51c

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007fe8ac00 (usable)
(XEN)  000000007fe8ac00 - 000000007fe8cc00 (ACPI NVS)
(XEN)  000000007fe8cc00 - 000000007fe8ec00 (ACPI data)
(XEN)  000000007fe8ec00 - 0000000080000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fed00400 (reserved)
(XEN)  00000000fed20000 - 00000000feda0000 (reserved)
(XEN)  00000000fee00000 - 00000000fef00000 (reserved)
(XEN)  00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2046MB (2095272kB)
(XEN) Xen heap: 14MB (14616kB)
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 DELL                                  ) @
0x00000000000fe
bf0
(XEN) ACPI: RSDT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcb83
(XEN) ACPI: FADT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcbd7
(XEN) ACPI: SSDT (v001   DELL    st_ex 0x00001000 MSFT 0x0100000d) @
0x00000000f
ffc7674
(XEN) ACPI: MADT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcc4b
(XEN) ACPI: BOOT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fccd5
(XEN) ACPI: ASF! (v016 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fccfd
(XEN) ACPI: MCFG (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcd64
(XEN) ACPI: HPET (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcda2
(XEN) ACPI: DSDT (v001   DELL    dt_ex 0x00001000 MSFT 0x0100000d) @
0x000000000
0000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
(XEN) Processor #7 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x0a] address[0xfec80800] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec80800, GSI 48-71
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 3 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2992.843 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 2/6 eip 90000
(XEN) Initializing CPU#2
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU2: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 3/7 eip 90000
(XEN) Initializing CPU#3
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU3: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 4 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE0xffffffff80000000,LOADER=generic''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000020000000->0000000040000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80100000->ffffffff805a4085
(XEN)  Init. ramdisk: ffffffff805a5000->ffffffff80b25400
(XEN)  Phys-Mach map: ffffffff80b26000->ffffffff80ba6000
(XEN)  Page tables:   ffffffff80ba6000->ffffffff80bb1000
(XEN)  Start info:    ffffffff80bb1000->ffffffff80bb2000
(XEN)  Boot stack:    ffffffff80bb2000->ffffffff80bb3000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
(XEN)  ENTRY ADDRESS: ffffffff80100000
(XEN) Initrd len 0x580400, start at 0xffffffff805a5000
(XEN) Scrubbing Free RAM: ...................Assertion ''tsc_elapsed32
!0'' fail
ed, line 821, file time.c
(XEN) BUG at time.c:821
(XEN) Assertion ''tsc_elapsed32 != 0'' failed, line 821, file
time.c
(XEN) BUG at time.c:821
(XEN) Assertion ''tsc_elapsed32 != 0'' failed, line 821, file
time.c
(XEN) CPU:    2
(XEN) EIP:    e010:[<ffff8300001369d9>]BUG at time.c:821
(XEN)  local_time_calibration+0x479/0x600
(XEN) EFLAGS: 0000000000010282
(XEN) rax: 0000000000000000   rbx: 000000007fffffff   rcx:
000000000000167a   rd
x: 000000000000167a
(XEN) rsi: 0000000000000001   rdi: ffff8300000b8fa0   rbp:
0000000000000000   rs
p: ffff830000fefde0
(XEN) r8:  0000000000000001   r9:  0000000000000017   r10:
ffff8300000b8000   r1
1: 000000000000167b
(XEN) r12: 00000000fffff18a   r13: 0000000000403612   r14:
000000003b9aca00   r1
5: 0000000000000000
(XEN) Xen stack trace from rsp=ffff830000fefde0:
(XEN)    .CPU:    1
(XEN) EIP:    e010:[<ffff8300001369d9>]0000000000000000 CPU:    3
(XEN) EIP:    e010:[<ffff8300001369d9>]000000003bdb5d96 0000000000000002
8000000
000179180 00000000dbeea490 00000000298badd9 0000000200180400
ffff830000180500
(XEN)    ffff830000136560 0000000000000000 ffff830000180400
0000000000000100 000
000003bdc1f5a ffff830000109345 0000000000000100 ffff830000180400
(XEN)    0000000000000002 ffff830000189880 ffff83000018a780
ffff830000189780 000
0000000000002 0000000000000000 0000000000000000 ffff830000118caa
(XEN)    000000ef00000000 0000000000000100 ffffffffffffc000
0000000000000002 fff
f8300001a6f10 ffff830000124c1c 0000000000000002 ffff830000ff2080
(XEN)    ffff830000feff28 0000000000000000 0000000000000000
ffff830000124cf0 000
0000000000000 00000000ffffffff 0000000000000000 ffff830000161af8
(XEN)    00000000a5a5a5a5 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000002
ffff830000ff2080
(XEN) Xen call trace from rsp=ffff830000fefde0:
(XEN)     local_time_calibration+0x479/0x600
(XEN) [<ffff830000136560>] local_time_calibration+0x479/0x600
(XEN) EFLAGS: 0000000000010282
(XEN)  local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>]rax: 0000000000000000   rbx: 000000007fffffff
rcx: 0
00000000000161f   rdx: 000000000000161f
(XEN) rsi: 0000000000000001   rdi: ffff8300000b8fa0   rbp:
0000000000000000   rs
p: ffff830000ff7de0
(XEN) r8:  0000000000000001   r9:  0000000000000017   r10:
ffff8300000b8000   r1
1: 0000000000001620
(XEN)  ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118caa>]EFLAGS: 0000000000010282
(XEN)  do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c1c>]rax: 0000000000000000   rbx: 000000007fffffff
rcx: 0
000000000001706   rdx: 0000000000001706
(XEN)  idle_loop+0xac/0xd0
(XEN) [<ffff830000124cf0>]rsi: 0000000000000001   rdi: ffff8300000b8fa0
rbp: 0
000000000000000   rsp: ffff830000febde0
(XEN) r12: 00000000ffffd0cd   r13: 0000000000400b83   r14:
000000003b9aca00   r1
5: 0000000000000000
(XEN) Xen stack trace from rsp=ffff830000ff7de0:
(XEN)     startup_cpu_idle_loop+0xb0/0xc0
(XEN) [<ffff830000161af8>]r8:  0000000000000001   r9:  0000000000000038
r10: f
fff8300000b8000   r11: 0000000000001707
(XEN) 0000000000000000 r12: 00000000ffffcf2b   r13: 0000000000403241
r14: 0000
00003b9aca00   r15: 0000000000000000
(XEN)  start_secondary+0xb8/0xc0
(XEN) Xen stack trace from rsp=ffff830000febde0:
(XEN)
(XEN) ffff83000012a203 000000003bdb58aa 0000000000000003
8000000000179180 000000
00dbee9bbe
****************************************
Panic on CPU2:
CPU2 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
000000003bdb2d5d 0000000000000001 00000000298c0e7f 8000000000179180
00000000dbee
1591 00000000298b962d 0000000100180400 ffff830000180480
(XEN)    ffff830000136560 0000000000000000 0000000300180400
ffff830000180400 000
0000000000080 ffff830000180580
(XEN)    000000003bdbe2f9 ffff830000136560 0000000000000000
ffff830000180400 000
0000000000180 000000003bdc1ab3 ffff830000109345 0000000000000180
ffff83000018040
0 ffff830000109345
(XEN)    0000000000000003 ffff830000189900 ffff83000018a780
ffff830000189780 000
0000000000003 0000000000000080 .ffff830000180400
(XEN)    0000000000000000 0000000000000000 ffff830000118caa
(XEN)    0000000000000001 ffff830000189800 ffff83000018a780
000000ef00000000 000
0000000000180 ffff830000189780 0000000000000001 0000000000000000
000000000000000
0 ffffffffffffc000 ffff830000118caa
(XEN)    0000000000000003 ffff8300001a6f10 ffff830000124c1c
0000000000000003 fff
f830000ff0080 000000ef00000000
(XEN)    ffff830000febf28 0000000000000000 0000000000000000
ffff830000124cf0 000
0000000000000 0000000000000080 ffffffffffffc000 00000000ffffffff
000000000000000
0 ffff830000161af8
(XEN)    0000000000000001 00000000a5a5a5a5 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
000000000000000
0 ffff8300001a6f10
(XEN)    ffff830000124c1c 0000000000000001 ffff830000ffa080
(XEN)    ffff830000ff7f28 0000000000000000 0000000000000000
0000000000000000 fff
f830000124cf0 0000000000000000 0000000000000000 0000000000000000
000000000000000
0 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 00000000ffffffff 0000000000000000 ffff830000161af8
(XEN)    00000000a5a5a5a5 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
000000000000000
0 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000003 fff
f830000ff0080
(XEN)
(XEN)    0000000000000000 0000000000000000 0000000000000000 Xen call
trace from
rsp=ffff830000febde0:
(XEN)    0000000000000000 [<ffff83000012a203>]0000000000000000
do_IRQ+0x1a3/0x2
10
(XEN) done.
(XEN) [<ffff830000136560>]*** Serial input -> DOM0 (type
''CTRL-a'' three
times to
 switch input to Xen).
(XEN) 0000000000000000  local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>]0000000000000000 0000000000000000
ac_timer_softirq_ac
tion+0x185/0x300
(XEN)
(XEN)    0000000000000000 0000000000000000 0000000000000000
[<ffff830000118caa>]
0000000000000000 0000000000000000 0000000000000000 0000000000000000
000000000000
0000  do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c1c>]
(XEN)     idle_loop+0xac/0xd0
(XEN) [<ffff830000124cf0>]0000000000000000 0000000000000000
0000000000000001 fff
f830000ffa080  startup_cpu_idle_loop+0xb0/0xc0
(XEN)
(XEN)    [<ffff830000161af8>]
(XEN)  start_secondary+0xb8/0xc0
(XEN) Xen call trace from rsp=ffff830000ff7de0:
(XEN)
(XEN) [<ffff830000136560>]
****************************************
Panic on CPU3:
CPU3 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
 local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>] ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118caa>] do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c1c>] idle_loop+0xac/0xd0
(XEN) [<ffff830000124cf0>] startup_cpu_idle_loop+0xb0/0xc0
(XEN) [<ffff830000161af8>] start_secondary+0xb8/0xc0
(XEN)

****************************************
Panic on CPU1:
CPU1 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
Linux version 2.6.12.3-xen0 (root@xenbox) (gcc version 3.3.3 (SuSE
Linux)) #1 Mo
n Aug 8 13:56:03 EDT 2005
kernel direct mapping tables upto ffff880020000000 @ 1000000-1102000
Registering memory for bootmem: from  1200000, size = 1ee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24])
IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47
ACPI: IOAPIC (id[0x0a] address[0xfec80800] gsi_base[48])
IOAPIC[2]: apic_id 10, version 32, address 0xfec80800, GSI 48-71
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)
Built 1 zonelists
Kernel command line: root=/dev/system/root64 console=tty0
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
Xen reported: 748.176 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Memory: 496896k/524288k available (2753k kernel code, 8872k reserved,
1160k data
, 268k init)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU:                   Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
checking if image is initramfs...it isn''t (bad gzip magic numbers);
looks like a
n initrd
NET: Registered protocol family 16
PCI: Using configuration type 1
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 9 10 11 12 15)
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn''t work, try "pci=routeirq".  If it
helps, post a
report
Grant table initialized
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
Simple Boot Flag at 0x7a set to 0x1
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
Initializing Cryptographic API
Real Time Clock Driver v1.12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
(XEN) Assertion ''tsc_elapsed32 != 0'' failed, line 821, file
time.c
(XEN) BUG at time.c:821
(XEN) CPU:    0
(XEN) EIP:    e010:[<ffff8300001369d9>]
local_time_calibration+0x479/0x600
(XEN) EFLAGS: 0000000000010286
(XEN) rax: 0000000000000000   rbx: 000000007fffffff   rcx:
00000000000033d7   rd
x: 00000000000033d7
(XEN) rsi: 0000000000000001   rdi: 00000000000002e3   rbp:
0000000000000000   rs
p: ffff830000107e10
(XEN) r8:  0000000000000000   r9:  0000000000000000   r10:
00000000000033c6   r1
1: 00000000000033d8
(XEN) r12: 00000000ffff5420   r13: 000000003b9add18   r14:
000000003b9aca00   r1
5: 0000000000000000
(XEN) Xen stack trace from rsp=ffff830000107e10:
(XEN)    0000000000000282 0000000077365bc9 0000000000000000
8000000000000000 000
000018d8fa06e 00000000db2e6e4b 0000000000180400 ffff830000180400
(XEN)    ffff830000136560 0000000000000000 ffff830000180400
0000000000000000 000
0000077371ab3 ffff830000109345 0000000000000000 ffff830000180400
(XEN)    0000000000000000 ffff830000189780 ffff83000018a780
ffff830000189780 000
0000000000000 ffff830000fe0080 ffff830000188200 ffff830000118caa
(XEN)    000000ef00000000 0000000000000000 ffffffffffffc000
0000000000000000 fff
f8300001a6f10 ffff830000124c1c ffff830000118636 ffff830000107f28
(XEN)    ffff830000179b00 ffff830000fe0080 ffff830000fe0080
ffffffff80541fb0 000
0ffffffff8010 00000000ffffffff ffffffff80100038 ffffffff8042c900
(XEN)    0000000000020800 0000000000000286 0000000000000001
00000000ffff8b30 000
00000ffff8b34 0000000000000000 ffffffff80110b3e 0000000000000000
(XEN)    00000000ffff8b34 0000000000000001 0000010000000000
ffffffff80110b3e 000
000000000e033 0000000000000286 ffffffff80541f80 000000000000e02b
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 ffff830000179b00
(XEN) Xen call trace from rsp=ffff830000107e10:
(XEN)    [<ffff830000136560>] local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>] ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118caa>] do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c1c>] idle_loop+0xac/0xd0
(XEN) [<ffff830000118636>] do_block+0x46/0x50
(XEN)

****************************************
Panic on CPU0:
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
(XEN) (file=extable.c, line=77) Pre-exception: ffff8300001278f2 ->
0000000000000
000
(XEN) CPU:    1
(XEN) EIP:    e010:[<ffff8300001278f2>]
call_function_interrupt+0x12/0x30
(XEN) EFLAGS: 0000000000010096
(XEN) rax: 0000000000000004   rbx: 0000000000000003   rcx:
0000000000000020   rd
x: 0000000000000202
(XEN) rsi: 0000000000000000   rdi: 0000000000000000   rbp:
ffff830000124aa0   rs
p: ffff830000ff7000
(XEN) r8:  0000ffff0000ffff   r9:  0000000000000000   r10:
00ff00ff00ff00ff   r1
1: 0000000000000000
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14:
0000000000000000   r1
5: 0000000000000000
(XEN) Xen stack trace from rsp=ffff830000ff7000:
(XEN)    0000ffff0000ffff 0000000000000004 0000000000000020
0000000000000202 000
0000000000000 0000000000000000 000000fb00000000 ffff83000013556d
(XEN)    000000000000e010 0000000000000296 ffff830000ff7068
0000000000000000 000
0000000000202 ffff830000124aa0 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 ffff83000017f160
ffff830000124aa0 000
0000000000000 0000000000000000 ffff830000124b08 0000000000000000
(XEN)    0000000000000003 ffff830000124aa0 ffff830000135470
0000000000000000 fff
f830000127908 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffff830000124aa0 0000000000000003
0000000000000000 00f
f00ff00ff00ff 0000000000000000 ffff830000fef788 0000000000000000
(XEN)    ffff830000172180 ffff8300001a9aa8 0000000000000000
0000000000000009 000
000fb00000000 ffff830000124ad4 000000000000e010 0000000000000296
(XEN)    ffff830000ff7198 0000000000000000 ffff830000124acc
0000000000000000 000
0000000000003 ffff830000124aa0 ffff830000135470 0000000000000000
(XEN)    ffff830000127908 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 ffff830000124aa0 0000000000000003 0000000000000000
(XEN)    00ff00ff00ff00ff 0000000000000000 ffff830000feb7a8
0000000000000000 fff
f830000172180 ffff8300001a9aa8 0000000000000000 0000000000000009
(XEN)    000000fb00000000 ffff830000124ad4 000000000000e010
0000000000000292 fff
f830000ff7278 0000000000000000 ffff830000124acc 0000000000000000
(XEN)    0000000000000003 ffff830000124aa0 ffff830000135470
0000000000000000 fff
f830000127908 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffff830000124aa0 0000000000000003
0000000000000000 00f
f00ff00ff00ff 0000000000000000 0000ffff0000ffff 0000000000000004
(XEN)    0000000000000020 0000000000000202 0000000000000000
0000000000000000 000
000fb00000000 ffff83000013556d 000000000000e010 0000000000000296
(XEN)    ffff830000ff7358 0000000000000000 0000000000000202
ffff830000124aa0 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    ffff83000017f160 ffff830000124aa0 0000000000000000
0000000000000000 fff
f830000124b08 0000000000000000 0000000000000003 ffff830000124aa0
(XEN)    ffff830000135470 0000000000000000 ffff830000127908
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 ffff830000124aa0
(XEN)    0000000000000003 0000000000000000 00ff00ff00ff00ff
0000000000000000 000
0ffff0000ffff 0000000000000004 0000000000000020 0000000000000202
(XEN)    0000000000000000 0000000000000000 000000fb00000000
ffff83000013556d 000
000000000e010 0000000000000296 ffff830000ff7488 0000000000000000
(XEN)    0000000000000202 ffff830000124aa0 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 ffff83000017f160 ffff830000124aa0
(XEN)    0000000000000000 0000000000000000 ffff830000124b08
0000000000000000 000
0000000000003 ffff830000124aa0 ffff830000135470 0000000000000000
(XEN) Xen call trace from rsp=ffff830000ff7000:
(XEN)    [<ffff83000013556d>] smp_call_function+0xad/0x160
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124b08>] machine_restart+0x68/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN)
(XEN)    [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124ad4>] machine_restart+0x34/0xd0
(XEN) [<ffff830000124acc>] machine_restart+0x2c/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN)
(XEN)    [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124ad4>] machine_restart+0x34/0xd0
(XEN) [<ffff830000124acc>] machine_restart+0x2c/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN)
(XEN)    [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff83000013556d>] smp_call_function+0xad/0x160
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124b08>] machine_restart+0x68/0xd0
(XEN)
(XEN)    [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN) [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff83000013556d>] smp_call_function+0xad/0x160
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN)
(XEN)    [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124b08>] machine_restart+0x68/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN) [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN)
(XEN)    [<ffff83000013556d>] smp_call_function+0xad/0x160
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124b08>] machine_restart+0x68/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN) [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff83000010a109>] __bitmap_weight+0x169/0x1a0
(XEN)
(XEN)    [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff8300001354f2>] smp_call_function+0x32/0x160
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124b08>] machine_restart+0x68/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN)
(XEN)    [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff83000013556d>] smp_call_function+0xad/0x160
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000124b08>] machine_restart+0x68/0xd0
(XEN)
(XEN)    [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN) [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN) [<ffff83000013556d>] smp_call_function+0xad/0x160
(XEN) [<ffff830000124aa0>] machine_restart+0x0/0xd0
(XEN)
(XEN)    [<ffff830000124b08>] machine_restart+0x68/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN) [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff830000124ad4>] machine_restart+0x34/0xd0
(XEN) [<ffff830000124acc>] machine_restart+0x2c/0xd0
(XEN) [<ffff830000135470>] smp_call_function_interrupt+0x50/0x60
(XEN)
(XEN)    [<ffff830000127908>] call_function_interrupt+0x28/0x30
(XEN) [<ffff8300001214ec>] __udelay+0x2c/0x40
(XEN) [<ffff83000011b1bd>] panic+0x7dd/0x870
(XEN) [<ffff83000011ce03>] __serial_putc+0xa3/0xf0
(XEN) [<ffff8300001394e0>] show_trace+0xd0/0xe0
(XEN) [<ffff830000139596>] show_stack+0xa6/0xb0
(XEN)
(XEN)    [<ffff83000013766d>] do_trap+0xfd/0x120
(XEN) [<ffff8300001451d5>] error_code+0x45/0x58
(XEN) [<ffff8300001369d9>] local_time_calibration+0x479/0x600
(XEN) [<ffff830000136560>] local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>] ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118caa>] do_softirq+0xaa/0xc0
(XEN)
(XEN)    [<ffff830000124c1c>] idle_loop+0xac/0xd0
(XEN) [<ffff830000124cf0>] startup_cpu_idle_loop+0xb0/0xc0
(XEN) [<ffff830000161af8>] start_secondary+0xb8/0xc0
(XEN)
(XEN) ************************************
(XEN) CPU1 FATAL TRAP 8 (double fault), ERROR_CODE 0000, IN INTERRUPT
CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************

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

Keir Fraser

2005-Aug-08 18:33 UTC

head link

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

On 8 Aug 2005, at 19:10, Puthiyaparambil, Aravindh wrote:
> I am getting an "Unknown Interrupt" message with changeset 6050
on the
> ES7000 x86_64 box running x86_64 SLES9 SP2 RC3. The system dies after
> that. Any idea why this could be happening?
> I am not sure if this is related to
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=122.
Definitely a different bug, but this one shouldn;t be hard to track 
down. Probably you are talking a page fault very early during boot. I''d
suggest working out where this occurs by adding printk statements 
(probably paging_init() in arch/x86/x86_64/mm.c would be a good place 
to start).
> When I tried the same changeset on my Dell PowerEdge 470 box I am 
> seeing
> something totally different and very scary :-)
> Is anybody else seeing this?
I think the HPET on your system is not working for some reason! Please 
try removing the call to init_hpet() from init_platform_timer() in 
arch/x86/time.c -- just fall back to init_pit(). You should then see 
''Platform timer is xxxMHz PIT'' rather than ''Platform
timer is xxxMHz
HPET'' in Xen''s boot log.

If that fixes your problem (very likely) then we can try and work out 
why the HPET is failing to work. Perhaps see whether native Linux 
successfully uses it, for example.

  -- Keir


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

Puthiyaparambil, Aravindh

2005-Aug-08 22:54 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

> 
> > I am getting an "Unknown Interrupt" message with changeset
6050 on
the> > ES7000 x86_64 box running x86_64 SLES9 SP2 RC3. The system dies
after> > that. Any idea why this could be happening?
> > I am not sure if this is related to
> > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=122.
> 
> Definitely a different bug, but this one shouldn;t be hard to track
> down. Probably you are talking a page fault very early during boot.
I''d> suggest working out where this occurs by adding printk statements
> (probably paging_init() in arch/x86/x86_64/mm.c would be a good place
> to start).
I put a few printks in paging_init and friends. This is the call tree
that I mapped out.
 
paging_init()->alloc_domheap_pages()->alloc_heap_pages()-> map_alloc() 

It looks like the page fault/interrupt is happening in map_alloc(). I
see that alloc_heap_pages() and map_alloc() are called before without
any issues. Not sure why it is tripping up now. Any ideas?
> 
> > When I tried the same changeset on my Dell PowerEdge 470 box I am
> > seeing
> > something totally different and very scary :-)
> > Is anybody else seeing this?
> 
> I think the HPET on your system is not working for some reason! Please
> try removing the call to init_hpet() from init_platform_timer() in
> arch/x86/time.c -- just fall back to init_pit(). You should then see
> ''Platform timer is xxxMHz PIT'' rather than
''Platform timer is xxxMHz
> HPET'' in Xen''s boot log.
> 
> If that fixes your problem (very likely) then we can try and work out
> why the HPET is failing to work. Perhaps see whether native Linux
> successfully uses it, for example.
I tried that patch. The serial output now shows "Platform timer is
1.193MHz PIT" but that does not fix the problem. I am still getting
those fatal errors.

Aravindh

---------------------------------------------------------------------
DELL POWEREDGE 470

_
 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ ''_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0-devel (root@) (gcc version 3.3.3 (SuSE Linux)) Mon Aug
8 15:19
:07 EDT 2005
 Latest ChangeSet: Mon Aug  8 10:39:29 2005
f586b9ecd47476357b685707e21c7fc274cb
d51c

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007fe8ac00 (usable)
(XEN)  000000007fe8ac00 - 000000007fe8cc00 (ACPI NVS)
(XEN)  000000007fe8cc00 - 000000007fe8ec00 (ACPI data)
(XEN)  000000007fe8ec00 - 0000000080000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fed00400 (reserved)
(XEN)  00000000fed20000 - 00000000feda0000 (reserved)
(XEN)  00000000fee00000 - 00000000fef00000 (reserved)
(XEN)  00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2046MB (2095272kB)
(XEN) Xen heap: 14MB (14616kB)
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 DELL                                  ) @
0x00000000000fe
bf0
(XEN) ACPI: RSDT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcb83
(XEN) ACPI: FADT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcbd7
(XEN) ACPI: SSDT (v001   DELL    st_ex 0x00001000 MSFT 0x0100000d) @
0x00000000f
ffc7674
(XEN) ACPI: MADT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcc4b
(XEN) ACPI: BOOT (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fccd5
(XEN) ACPI: ASF! (v016 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fccfd
(XEN) ACPI: MCFG (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcd64
(XEN) ACPI: HPET (v001 DELL    WS 470  0x00000007 ASL  0x00000061) @
0x000000000
00fcda2
(XEN) ACPI: DSDT (v001   DELL    dt_ex 0x00001000 MSFT 0x0100000d) @
0x000000000
0000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
(XEN) Processor #7 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x0a] address[0xfec80800] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec80800, GSI 48-71
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 3 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2992.806 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 2/6 eip 90000
(XEN) Initializing CPU#2
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU2: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 3/7 eip 90000
(XEN) Initializing CPU#3
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU3: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE0xffffffff80000000,LOADER=generic''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000020000000->0000000040000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80100000->ffffffff805a4085
(XEN)  Init. ramdisk: ffffffff805a5000->ffffffff80b25400
(XEN)  Phys-Mach map: ffffffff80b26000->ffffffff80ba6000
(XEN)  Page tables:   ffffffff80ba6000->ffffffff80bb1000
(XEN)  Start info:    ffffffff80bb1000->ffffffff80bb2000
(XEN)  Boot stack:    ffffffff80bb2000->ffffffff80bb3000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
(XEN)  ENTRY ADDRESS: ffffffff80100000
(XEN) Initrd len 0x580400, start at 0xffffffff805a5000
(XEN) Scrubbing Free RAM: ...................Assertion ''tsc_elapsed32
!0'' fail
ed, line 821, file time.c
(XEN) Assertion ''tsc_elapsed32 != 0'' failed, line 821, file
time.c
(XEN) Assertion ''tsc_elapsed32 != 0'' failed, line 821, file
time.c
(XEN) BUG at time.c:821
(XEN) BUG at time.c:821
(XEN) CPU:    2
(XEN) EIP:    e010:[<ffff830000136909>]CPU:    3
(XEN) EIP:    e010:[<ffff830000136909>]
local_time_calibration+0x479/0x600
(XEN) EFLAGS: 0000000000010282
(XEN) rax: 0000000000000000   rbx: 000000007fffffff   rcx:
00000000000016a3   rd
x: 00000000000016a3
(XEN) rsi: 0000000000000001   rdi: ffff8300000b8fa0   rbp:
0000000000000000   rs
p: ffff830000fefde0
(XEN) r8:  0000000000000001   r9:  0000000000000017   r10:
ffff8300000b8000   r1
1: 00000000000016a4
(XEN) r12: 00000000ffffcee5   r13: 00000000003da083   r14:
000000003b9aca00   r1
5: 0000000000000000
(XEN) Xen stack trace from rsp=ffff830000fefde0:
(XEN)    0000000000000000 000000003bd8f5be 0000000000000002
8000000000178c80 000
000011363b24e 0000000061010fd2 0000000200180400 ffff830000180500
(XEN)    ffff830000136490 0000000000000000 ffff830000180400 BUG at
time.c:821
(XEN)  local_time_calibration+0x479/0x600
(XEN) 0000000000000100 000000003bd9b83f ffff830000109345
0000000000000100 ffff83
0000180400 .CPU:    1
(XEN) EIP:    e010:[<ffff830000136909>]EFLAGS: 0000000000010282
(XEN)
(XEN)    0000000000000002 ffff830000189880 ffff83000018a780
ffff830000189780 000
0000000000002 0000000000000000 0000000000000000 ffff830000118caa
(XEN)    000000ef00000000 0000000000000100 ffffffffffffc000
0000000000000002 fff
f8300001a6f10 ffff830000124c1c 0000000000000002 ffff830000ff2080
(XEN)    ffff830000feff28 0000000000000000 0000000000000000
ffff830000124cf0 000
0000000000000 00000000ffffffff 0000000000000000 ffff830000161a28
(XEN)    00000000a5a5a5a5 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000002
ffff830000ff2080
(XEN) Xen call trace from rsp=ffff830000fefde0:
(XEN)    rax: 0000000000000000   rbx: 000000007fffffff   rcx:
00000000000016bb
 rdx: 00000000000016bb
(XEN) [<ffff830000136490>] local_time_calibration+0x479/0x600
(XEN)  local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>]rsi: 0000000000000001   rdi: ffff8300000b8fa0
rbp: 0
000000000000000   rsp: ffff830000febde0
(XEN)  ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118caa>]r8:  0000000000000001   r9:  0000000000000017
r10: f
fff8300000b8000   r11: 00000000000016bc
(XEN)  do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c1c>]r12: 00000000ffffd22b   r13: 00000000003d8cde
r14: 0
00000003b9aca00   r15: 0000000000000000
(XEN)  idle_loop+0xac/0xd0
(XEN) [<ffff830000124cf0>]Xen stack trace from rsp=ffff830000febde0:
(XEN)     startup_cpu_idle_loop+0xb0/0xc0
(XEN) [<ffff830000161a28>]ffff83000012a203 000000003bd8c70d
0000000000000003 800
0000000178c80  start_secondary+0xb8/0xc0
(XEN) 00000001136375f4 0000000061011d44 0000000300180400
ffff830000180580
(XEN)
(XEN) ffff830000136490 0000000000000000 ffff830000180400 EFLAGS:
000000000001028
2
(XEN) rax: 0000000000000000   rbx: 000000007fffffff   rcx:
0000000000001a07   rd
x: 0000000000001a07
(XEN) 0000000000000180
****************************************
Panic on CPU2:
CPU2 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
000000003bd9888e rsi: 0000000000000001   rdi: ffff8300000b8fa0   rbp:
0000000000
000000   rsp: ffff830000ff7de0
(XEN) ffff830000109345 r8:  0000000000000001   r9:  000000000000004d
r10: ffff
8300000b8000   r11: 0000000000001a08
(XEN) r12: 00000000ffffbe86   r13: 00000000003d68db   r14:
000000003b9aca00   r1
5: 0000000000000000
(XEN) 0000000000000180 Xen stack trace from rsp=ffff830000ff7de0:
(XEN)    ffff830000180400 0000000000000000
(XEN)    000000003bd8a648 0000000000000003 ffff830000189900
ffff83000018a780 fff
f830000189780 0000000000000003 0000000000000000 0000000000000000
ffff830000118ca
a 0000000000000001
(XEN)    000000ef00000000 0000000000000180 ffffffffffffc000
0000000000000003 fff
f8300001a6f10 8000000000178c80 ffff830000124c1c 0000000000000003
ffff830000ff008
0
(XEN)    00000001136320f7 000000006100f82d 0000000100180400
ffff830000febf28 000
0000000000000 0000000000000000 ffff830000124cf0 0000000000000000
00000000fffffff
f ffff830000180480
(XEN)    ffff830000136490 0000000000000000 ffff830000180400
0000000000000080 000
000003bd95f49 ffff830000109345 0000000000000000 .0000000000000080
ffff8300001804
00
(XEN)    0000000000000001 ffff830000161a28 ffff830000189800
ffff83000018a780
(XEN)    00000000a5a5a5a5 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 ffff830000189780 0000000000000000 0000000000000000
000000000000000
0
(XEN)    0000000000000001 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
000000000000000
0 0000000000000000 0000000000000000 ffff830000118caa
(XEN)
(XEN)    000000ef00000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
000000000000000
0 0000000000000080
(XEN)    0000000000000000 0000000000000000 0000000000000003
ffff830000ff0080
(XEN) ffffffffffffc000 Xen call trace from rsp=ffff830000febde0:
(XEN)    [<ffff83000012a203>]0000000000000001  do_IRQ+0x1a3/0x210
(XEN) ffff8300001a6f10 [<ffff830000136490>]ffff830000124c1c
local_time_calibrat
ion+0x0/0x600
(XEN) 0000000000000001 ffff830000ffa080
(XEN)    [<ffff830000109345>]ffff830000ff7f28
ac_timer_softirq_action+0x185/0x3
00
(XEN) 0000000000000000 [<ffff830000118caa>]0000000000000000
do_softirq+0xaa/0xc
0
(XEN) ffff830000124cf0 [<ffff830000124c1c>]0000000000000000
idle_loop+0xac/0xd0
(XEN) 00000000ffffffff [<ffff830000124cf0>]0000000000000000
startup_cpu_idle_lo
op+0xb0/0xc0
(XEN) ffff830000161a28
(XEN)    [<ffff830000161a28>]
(XEN)    done.
(XEN) 00000000a5a5a5a5  start_secondary+0xb8/0xc0
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen
).
(XEN)
(XEN) 0000000000000000 0000000000000000 0000000000000000
****************************************
Panic on CPU3:
CPU3 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000001
ffff830000ffa080
(XEN) Xen call trace from rsp=ffff830000ff7de0:
(XEN)    [<ffff830000136490>] local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>] ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118caa>] do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c1c>] idle_loop+0xac/0xd0
(XEN) [<ffff830000124cf0>] startup_cpu_idle_loop+0xb0/0xc0
(XEN) [<ffff830000161a28>] start_secondary+0xb8/0xc0
(XEN)

****************************************
Panic on CPU1:
CPU1 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
Linux version 2.6.12.3-xen0 (root@xenbox) (gcc version 3.3.3 (SuSE
Linux)) #2 Mo
n Aug 8 15:02:25 EDT 2005
kernel direct mapping tables upto ffff880020000000 @ 1000000-1102000
Registering memory for bootmem: from  1200000, size = 1ee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xfec80000] gsi_base[24])
IOAPIC[1]: apic_id 9, version 32, address 0xfec80000, GSI 24-47
ACPI: IOAPIC (id[0x0a] address[0xfec80800] gsi_base[48])
IOAPIC[2]: apic_id 10, version 32, address 0xfec80800, GSI 48-71
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)
Built 1 zonelists
Kernel command line: root=/dev/system/root64 console=tty0
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
Xen reported: 748.173 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Memory: 496896k/524288k available (2753k kernel code, 8872k reserved,
1160k data
, 268k init)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU:                   Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
checking if image is initramfs...it isn''t (bad gzip magic numbers);
looks like a
n initrd
NET: Registered protocol family 16
PCI: Using configuration type 1
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 9 10 11 12 15)
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn''t work, try "pci=routeirq".  If it
helps, post a
report
Grant table initialized
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
Simple Boot Flag at 0x7a set to 0x1
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
Initializing Cryptographic API
Real Time Clock Driver v1.12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
(XEN) Assertion ''tsc_elapsed32 != 0'' failed, line 821, file
time.c
(XEN) BUG at time.c:821
(XEN) CPU:    0
(XEN) EIP:    e010:[<ffff830000136909>]
local_time_calibration+0x479/0x600
(XEN) EFLAGS: 0000000000010286
(XEN) rax: 0000000000000000   rbx: 000000007fffffff   rcx:
00000000000033d5   rd
x: 00000000000033d5
(XEN) rsi: 0000000000000001   rdi: 00000000000002c3   rbp:
0000000000000000   rs
p: ffff830000107e10
(XEN) r8:  0000000000000000   r9:  0000000000000000   r10:
00000000000033c4   r1
1: 00000000000033d6
(XEN) r12: 00000000ffff4f37   r13: 000000003b9ac373   r14:
000000003b9aca00   r1
5: 0000000000000000
(XEN) Xen stack trace from rsp=ffff830000107e10:
(XEN)    0000000000000282 000000007736464b 0000000000000000
8000000000000000 000
00001c50c2f94 0000000112ab36bf 0000000000180400 ffff830000180400
(XEN)    ffff830000136490 0000000000000000 ffff830000180400
0000000000000000 000
000007737056b ffff830000109345 0000000000000000 ffff830000180400
(XEN)    0000000000000000 ffff830000189780 ffff83000018a780
ffff830000189780 000
0000000000000 ffff830000fe0080 ffff830000188200 ffff830000118caa
(XEN)    000000ef00000000 0000000000000000 ffffffffffffc000
0000000000000000 fff
f8300001a6f10 ffff830000124c1c ffff830000118636 ffff830000107f28
(XEN)    ffff830000179600 ffff830000fe0080 ffff830000fe0080
ffffffff80541fb0 000
0ffffffff8010 00000000ffffffff ffffffff80100038 ffffffff8042c900
(XEN)    0000000000020800 0000000000000286 0000000000000001
00000000ffff8b30 000
00000ffff8b34 0000000000000000 ffffffff80110b3e 0000000000000000
(XEN)    00000000ffff8b34 0000000000000001 0000010000000000
ffffffff80110b3e 000
000000000e033 0000000000000286 ffffffff80541f80 000000000000e02b
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 000
0000000000000 ffff830000179600
(XEN) Xen call trace from rsp=ffff830000107e10:
(XEN)    [<ffff830000136490>] local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>] ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118caa>] do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c1c>] idle_loop+0xac/0xd0
(XEN) [<ffff830000118636>] do_block+0x46/0x50
(XEN)

****************************************
Panic on CPU0:
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...

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

Keir Fraser

2005-Aug-09 07:35 UTC

head link

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

On 8 Aug 2005, at 23:54, Puthiyaparambil, Aravindh wrote:
> I put a few printks in paging_init and friends. This is the call tree
> that I mapped out.
>
> paging_init()->alloc_domheap_pages()->alloc_heap_pages()->
map_alloc()
>
> It looks like the page fault/interrupt is happening in map_alloc(). I
> see that alloc_heap_pages() and map_alloc() are called before without
> any issues. Not sure why it is tripping up now. Any ideas?
Not really. Perhaps some part of the bitmap is not properly mapped? I 
think you''ll have to add a bunch more tracing -- find out what address 
is actually faulting and work backwards to see why it''s not mapped. If 
it looks like it should be valid then maybe look at the code that is 
intended to 1:1 map all RAM, in arch/x86/setup.c:__start_xen() (the 
code is wrapped in CONFIG_x86_64).
> I tried that patch. The serial output now shows "Platform timer is
> 1.193MHz PIT" but that does not fix the problem. I am still getting
> those fatal errors.
Enable the #if 0''ed code in arch/x86/time.c:local_time_calibration(). 
That should get us more diagnostics out.

  -- Keir


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

Puthiyaparambil, Aravindh

2005-Aug-10 02:35 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

> > It looks like the page fault/interrupt is happening in map_alloc().
I> > see that alloc_heap_pages() and map_alloc() are called before
without> > any issues. Not sure why it is tripping up now. Any ideas?
> 
> Not really. Perhaps some part of the bitmap is not properly mapped? I
> think you''ll have to add a bunch more tracing -- find out what
address
> is actually faulting and work backwards to see why it''s not
mapped. If
> it looks like it should be valid then maybe look at the code that is
> intended to 1:1 map all RAM, in arch/x86/setup.c:__start_xen() (the
> code is wrapped in CONFIG_x86_64).
I found out that the "Unknown Interrupt" issue happens only when debug
is turned on in Xen (verbose & debug=y in Rules.mk). When debug is
turned off the systems dies in the middle of "Scrubbing Free RAM". I
have attached a serial output of the boot messages
(es7000_x86_64_nodebug_6065.txt). This could be Bugzilla #147.
Should I be still trying to find the faulting address in the debug case?
> 
> > I tried that patch. The serial output now shows "Platform timer
is
> > 1.193MHz PIT" but that does not fix the problem. I am still
getting
> > those fatal errors.
> 
> Enable the #if 0''ed code in
arch/x86/time.c:local_time_calibration().
> That should get us more diagnostics out.
Please see the attached dell_x86_64_timer.txt file.

Aravindh



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

Nakajima, Jun

2005-Aug-10 04:39 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Puthiyaparambil, Aravindh wrote:>>> It looks like the page fault/interrupt is happening in map_alloc().
>>> I see that alloc_heap_pages() and map_alloc() are called before
>>> without any issues. Not sure why it is tripping up now. Any ideas?
>> 
>> Not really. Perhaps some part of the bitmap is not properly mapped? I
>> think you''ll have to add a bunch more tracing -- find out what
>> address is actually faulting and work backwards to see why
it''s not
>> mapped. If it looks like it should be valid then maybe look at the
>> code that is intended to 1:1 map all RAM, in
>> arch/x86/setup.c:__start_xen() (the code is wrapped in
>> CONFIG_x86_64). 
> 
> I found out that the "Unknown Interrupt" issue happens only when
debug
> is turned on in Xen (verbose & debug=y in Rules.mk). When debug is
> turned off the systems dies in the middle of "Scrubbing Free
RAM". I
> have attached a serial output of the boot messages
> (es7000_x86_64_nodebug_6065.txt). This could be Bugzilla #147.
> Should I be still trying to find the faulting address in the debug
> case? 
> I have the same problem "Unknown Interrupt" on a DP machine. Looks
like
#PF is happening at => when xen is built with debug=y.

static void map_alloc(unsigned long first_page, unsigned long nr_pages)
{
    ...
    curr_idx  = first_page / PAGES_PER_MAPWORD;
    start_off = first_page & (PAGES_PER_MAPWORD-1);
    end_idx   = (first_page + nr_pages) / PAGES_PER_MAPWORD;
    end_off   = (first_page + nr_pages) & (PAGES_PER_MAPWORD-1);

    if ( curr_idx == end_idx )
    {
        alloc_bitmap[curr_idx] &= -(1UL<<end_off) |
((1UL<<start_off)-1);
    }
    else
    {
        alloc_bitmap[curr_idx] &= (1UL<<start_off)-1;
        while ( ++curr_idx != end_idx ) alloc_bitmap[curr_idx] = 0;
 =>       alloc_bitmap[curr_idx] &= -(1UL<<end_off);
    }
}

If I change 
        while ( ++curr_idx != end_idx - 1 ) alloc_bitmap[curr_idx] = 0;
I can work around it.

Jun
---
Intel Open Source Technology Center

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

Puthiyaparambil, Aravindh

2005-Aug-10 05:39 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

> I have the same problem "Unknown Interrupt" on a DP machine.
Looks
like> #PF is happening at => when xen is built with debug=y.
> 
> static void map_alloc(unsigned long first_page, unsigned long
nr_pages)> {
>     ...
>     curr_idx  = first_page / PAGES_PER_MAPWORD;
>     start_off = first_page & (PAGES_PER_MAPWORD-1);
>     end_idx   = (first_page + nr_pages) / PAGES_PER_MAPWORD;
>     end_off   = (first_page + nr_pages) & (PAGES_PER_MAPWORD-1);
> 
>     if ( curr_idx == end_idx )
>     {
>         alloc_bitmap[curr_idx] &= -(1UL<<end_off) |
> ((1UL<<start_off)-1);
>     }
>     else
>     {
>         alloc_bitmap[curr_idx] &= (1UL<<start_off)-1;
>         while ( ++curr_idx != end_idx ) alloc_bitmap[curr_idx] = 0;
>  =>       alloc_bitmap[curr_idx] &= -(1UL<<end_off);
>     }
> }
> 
> If I change
>         while ( ++curr_idx != end_idx - 1 ) alloc_bitmap[curr_idx] 0;
> I can work around it.
Yes, that fixed the "Unknown Interrupt" problem. I am now seeing the
same issue that I am seeing on the Dell PowerEdge 470 x86_64 system.

BTW, what is a DP machine?

Aravindh

----------------------------

(XEN) Scrubbing Free RAM: ..Assertion ''tsc_elapsed32 != 0''
failed, line
821, file time.c
(XEN) Assertion ''tsc_elapsed32 != 0'' failed, line 821, file
time.c
(XEN) BUG at time.c:821
(XEN) BUG at time.c:821
(XEN) CPU:    2
(XEN) EIP:    e010:[<ffff8300001368c9>]CPU:    3
(XEN) EIP:    e010:[<ffff8300001368c9>]
local_time_calibration+0x479/0x600
(XEN) EFLAGS: 0000000000010282
(XEN) rax: 0000000000000000   rbx: 000000007fffffff   rcx:
0000000000001807   rdx: 0000000000005807
(XEN) rsi: 0000000000000001   rdi: ffff8300000b8fa0   rbp:
0000000000000000   rsp: ffff8300001dfde0
(XEN) r8:  0000000000000001   r9:  0000000000000017   r10:
ffff8300000b8000   r11: 0000000000004001
(XEN) r12: 00000000ffff6ff4   r13: 000000000044c693   r14:
000000003b9aca00   r15: 0000000000000000
(XEN)  local_time_calibration+0x479/0x600
(XEN) EFLAGS: 0000000000010282
(XEN) rax: 0000000000000000   rbx: 000000007fffffff   rcx:
000000000000181f   rdx: 000000000000581f
(XEN) rsi: 0000000000000001   rdi: ffff8300000b8fa0   rbp:
0000000000000000   rsp: ffff8300001d7de0
(XEN) r8:  0000000000000001   r9:  0000000000000017   r10:
ffff8300000b8000   r11: 0000000000004001
(XEN) r12: 00000000ffffefa2   r13: 00000000004559e5   r14:
000000003b9aca00   r15: 0000000000000000
(XEN) Xen stack trace from rsp=ffff8300001dfde0:
(XEN)    0000000000000000 000000003be040cf 0000000000000002
8000000000179100 00000000ef899ea6 0000000028d8c62e 000000020018040
0 ffff830000180500
(XEN)    ffff830000136450 0000000000000000 ffff830000180400
0000000000000100 000000003be1011f ffff830000109345 000000000000010
0 ffff830000180400
(XEN)    0000000000000002 ffff830000189880 ffff83000018a780
ffff830000189780 0000000000000002 0000000000000000 000000000000000
0 ffff830000118c9a
(XEN)    000000ef00000000 0000000000000100 ffffffffffffc000
0000000000000002 ffff8300001a6f10 ffff830000124c0c 000000000000000
2 ffff830000ff0080
(XEN)    ffff8300001dff28 0000000000000000 0000000000000000
ffff830000124ce0 0000000000000000 00000000ffffffff 000000000000000
0 ffff8300001619f8
(XEN)    00000000a5a5a5a5 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 000000000000000
0 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 000000000000000
0 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 000000000000000
0 Xen stack trace from rsp=ffff8300001d7de0:
(XEN)    0000000000000000 000000003be05ffb 0000000000000003
8000000000179100 00000000ef8b97ba 0000000028d90422 000000030018040
0 ffff830000180580
(XEN)    ffff830000136450 0000000000000000 ffff830000180400
0000000000000180 000000003be12081 ffff830000109345 000000000000018
0 ffff830000180400
(XEN)    0000000000000003 ffff830000189900 ffff83000018a780
ffff830000189780 0000000000000003 0000000000000000 000000000000000
0 ffff830000118c9a
(XEN)    000000ef00000000 0000000000000180 ffffffffffffc000
0000000000000003 ffff8300001a6f10 ffff830000124c0c 000000000000000
3 ffff8300001da080
(XEN)    ffff8300001d7f28 0000000000000000 0000000000000000
ffff830000124ce0 0000000000000000 00000000ffffffff 000000000000000
0 ffff8300001619f8
(XEN)    00000000a5a5a5a5 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 000000000000000
0 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 000000000000000
0 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 000000000000000
0 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000003
ffff8300001da080
(XEN) Xen call trace from rsp=ffff8300001d7de0:
(XEN)    [<ffff830000136450>]0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000002
ffff830000ff0080
(XEN)  local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>]Xen call trace from rsp=ffff8300001dfde0:
(XEN)    [<ffff830000136450>] ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118c9a>] local_time_calibration+0x0/0x600
(XEN) [<ffff830000109345>] do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c0c>] ac_timer_softirq_action+0x185/0x300
(XEN) [<ffff830000118c9a>] idle_loop+0xac/0xd0
(XEN) [<ffff830000124ce0>] do_softirq+0xaa/0xc0
(XEN) [<ffff830000124c0c>] startup_cpu_idle_loop+0xb0/0xc0
(XEN) [<ffff8300001619f8>] idle_loop+0xac/0xd0
(XEN) [<ffff830000124ce0>] start_secondary+0xb8/0xc0
(XEN)
(XEN)  startup_cpu_idle_loop+0xb0/0xc0
(XEN) [<ffff8300001619f8>]
****************************************
Panic on CPU3:
CPU3 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
 start_secondary+0xb8/0xc0
(XEN)

****************************************
Panic on CPU2:
CPU2 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

Reboot in five seconds...
(XEN) ......

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

Li, Xin B

2005-Aug-10 05:48 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

>BTW, what is a DP machine?
Dual Processors, :-)
-Xin

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

Nakajima, Jun

2005-Aug-10 05:57 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Puthiyaparambil, Aravindh wrote:>> I have the same problem "Unknown Interrupt" on a DP machine.
Looks
>> like #PF is happening at => when xen is built with debug=y.
>> 
>> static void map_alloc(unsigned long first_page, unsigned long
>>     nr_pages) { ...
>>     curr_idx  = first_page / PAGES_PER_MAPWORD;
>>     start_off = first_page & (PAGES_PER_MAPWORD-1);
>>     end_idx   = (first_page + nr_pages) / PAGES_PER_MAPWORD;
>>     end_off   = (first_page + nr_pages) & (PAGES_PER_MAPWORD-1);
>> 
>>     if ( curr_idx == end_idx )
>>     {
>>         alloc_bitmap[curr_idx] &= -(1UL<<end_off) |
>>     ((1UL<<start_off)-1); }
>>     else
>>     {
>>         alloc_bitmap[curr_idx] &= (1UL<<start_off)-1;
>>         while ( ++curr_idx != end_idx ) alloc_bitmap[curr_idx] = 0;
>>  =>       alloc_bitmap[curr_idx] &= -(1UL<<end_off);     }
>> }
>> 
>> If I change
>>         while ( ++curr_idx != end_idx - 1 ) alloc_bitmap[curr_idx]
>> 0; I can work around it.
> 
> Yes, that fixed the "Unknown Interrupt" problem. I am now seeing
the
> same issue that I am seeing on the Dell PowerEdge 470 x86_64 system.
> 
> BTW, what is a DP machine?
> 
> Aravindh
> Try to use old version of arch/x86/time.c, for example, the one
attached. You also might want to comment out:

asmlinkage int do_page_fault(struct cpu_user_regs *regs)
{
    ...

xen_fault:

    if ( likely((fixup = search_exception_table(regs->eip)) != 0) )
    {
        perfc_incrc(copy_user_faults);
        if ( !shadow_mode_enabled(d) )
            //      DPRINTK("Page fault: %p -> %p\n",
_p(regs->eip),
_p(fixup));
            ;
        regs->eip = fixup;
        return 0;
    }

Jun
---
Intel Open Source Technology Center


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

Keir Fraser

2005-Aug-10 13:49 UTC

head link

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

On 8 Aug 2005, at 19:10, Puthiyaparambil, Aravindh wrote:
> When I tried the same changeset on my Dell PowerEdge 470 box I am 
> seeing
> something totally different and very scary :-)
> Is anybody else seeing this?
I just made a fix to x86/64 time handling, so it''s worth trying out the
latest version on the Dell box.

  -- Keir


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

Puthiyaparambil, Aravindh

2005-Aug-10 18:18 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Xen and Dom0 boots successfully on the Dell PowerEdge x86_64 box with
Keir''s new time fix. I did have to comment out the printk as suggested
by Jun as the serial was getting flooded otherwise.

Jun, are you going to submit a patch for the map_alloc() function?

On the ES7000 x86_64 I no longer see the "Assertion ''tsc_elapsed32
!0''". But the system dies on the error shown at the end of the
email.
This is with changeset 6081 + Jun''s map_alloc fix + Jerone''s
rm_nx
patch. Any suggestions as to how to proceed?

Thanks
Aravindh

------------------------------------------------------------------------
--

(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
(XEN) (file=/root/xen/xen-unstable.hg/xen/include/asm/mm.h, line=204)
Error pfn d9999: rd=ffff8300001da080, od=ffff8300001da080, caf=00000000,
taf=0000000000000000
(XEN) DOM0: (file=mm.c, line=1486) Error while validating pfn dffc7 for
type 0400000020000000. caf=80000004 taf=0400000020000001
(XEN) DOM0: (file=mm.c, line=1712) Error while pinning mfn dffc7
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU:    0
(XEN) EIP:    e033:[<ffffffff8011e04c>] ???
(XEN) EFLAGS: 0000000000000282
(XEN) rax: 00000000ffffffea   rbx: 0000000007000000   rcx:
ffffffff8011e048   rdx: 0000000000000000
(XEN) rsi: 0000000000000001   rdi: ffffffff80567e70   rbp:
0000000020000000   rsp: ffffffff80567e38
(XEN) r8:  0000000000000200   r9:  0000000000000000   r10:
0000000000007ff0   r11: 0000000000000246
(XEN) r12: ffffffff808011b8   r13: 0000000000000037   r14:
ffffffff80800000   r15: 0000000000000000
(XEN) Guest stack trace from rsp=ffffffff80567e38:
(XEN)    ffffffff8011e048 0000000000000246 ffffffff8011e04c
000000010000e030 0000000000010282 ffffffff80567e70 000000000000e02b
0000000000000000
(XEN)    00000000000dffc7 00000000dffff1b0 0000000007000000
0000000020000000 ffffffff80592be9 0000000000000000 0000000000839000
0000000000801000
(XEN)    ffffffff80800000 ffff880020000000 ffff880000000000
ffff880020000000 0000780000000000 0000000080000000 ffffffff80592d81
0000000000800000
(XEN)    0000000000000000 000000000000001b ffffffff805093bb
ffffffff80567fa0 0000ffffffff8010 ffffffff80567fb0 ffffffff8058eada
00000000c064e830
(XEN)    ffffffff80502dbc 0000000000000001 00000000000c0105
0000000000000000 ffffffff80103000 ffffffff0000000f 0000000000010800
ffffffff80452900
(XEN)    ffffffff80100038 00000000ffffffff 0000ffffffff8010
ffffffff80567fb0 ffffffff805884f8 ffffffff805093a0 ffffffff80588190
80108e0000100038
(XEN)    00000000ffffffff 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000
(XEN) Domain 0 shutdown: rebooting machine.
> -----Original Message-----
> Try to use old version of arch/x86/time.c, for example, the one
> attached. You also might want to comment out:
> 
> asmlinkage int do_page_fault(struct cpu_user_regs *regs)
> {
>     ...
> 
> xen_fault:
> 
>     if ( likely((fixup = search_exception_table(regs->eip)) != 0) )
>     {
>         perfc_incrc(copy_user_faults);
>         if ( !shadow_mode_enabled(d) )
>             //      DPRINTK("Page fault: %p -> %p\n",
_p(regs->eip),
> _p(fixup));
>             ;
>         regs->eip = fixup;
>         return 0;
>     }
> 
> Jun
> ---
> Intel Open Source Technology Center
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Nakajima, Jun

2005-Aug-10 18:24 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Puthiyaparambil, Aravindh wrote:> Xen and Dom0 boots successfully on the Dell PowerEdge x86_64 box with
> Keir''s new time fix. I did have to comment out the printk as
suggested
> by Jun as the serial was getting flooded otherwise.
> 
> Jun, are you going to submit a patch for the map_alloc() function?
> 
> On the ES7000 x86_64 I no longer see the "Assertion
''tsc_elapsed32 !> 0''". But the system dies on the
error shown at the end of the email.
> This is with changeset 6081 + Jun''s map_alloc fix +
Jerone''s rm_nx
> patch. Any suggestions as to how to proceed?
Can you try to add mem=3g for the xen boot entry?

Jun
---
Intel Open Source Technology Center
> 
> Thanks
> Aravindh
> 
>
------------------------------------------------------------------------> 
>> -----Original Message-----
>> Try to use old version of arch/x86/time.c, for example, the one
>> attached. You also might want to comment out:
>> 
>> asmlinkage int do_page_fault(struct cpu_user_regs *regs) {
>>     ...
>> 
>> xen_fault:
>> 
>>     if ( likely((fixup = search_exception_table(regs->eip)) != 0) ) 
>>         { perfc_incrc(copy_user_faults);
>>         if ( !shadow_mode_enabled(d) )
>>             //      DPRINTK("Page fault: %p -> %p\n",
_p(regs->eip),
>>             _p(fixup)); ;
>>         regs->eip = fixup;
>>         return 0;
>>     }
>> 
>> Jun
>> ---
>> Intel Open Source Technology Center



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

Puthiyaparambil, Aravindh

2005-Aug-10 18:36 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

With mem=3g dom0_mem=512M this is what happens...

Aravindh

(XEN) Truncating memory map to 3145728kB
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009dc00 (usable)
(XEN)  000000000009dc00 - 00000000000a0000 (reserved)
(XEN)  00000000000ce000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000037ea0000 (usable)
(XEN)  0000000037ea0000 - 0000000037edf000 (ACPI data)
(XEN)  0000000037edf000 - 0000000037f00000 (ACPI NVS)
(XEN)  0000000037f00000 - 00000000c0000000 (usable)
(XEN) System RAM: 3071MB (3144948kB)
(XEN) Xen heap: 14MB (14580kB)

...................................

(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80000000,L
OADER=generic''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000060000000->0000000080000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80100000->ffffffff805cc086
(XEN)  Init. ramdisk: ffffffff805cd000->ffffffff805cd000
(XEN)  Phys-Mach map: ffffffff805cd000->ffffffff8064d000
(XEN)  Page tables:   ffffffff8064d000->ffffffff80654000
(XEN)  Start info:    ffffffff80654000->ffffffff80655000
(XEN)  Boot stack:    ffffffff80655000->ffffffff80656000
(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) (file=/root/xen/xen-unstable.hg/xen/include/asm/mm.h, line=204)
Error pfn 7ffff: rd=ffff8300001c8080, od=0000000000000000, caf=00000000,
taf=0000000000000000
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU:    0
(XEN) EIP:    e033:[<ffffffff8011e4a1>] ???
(XEN) EFLAGS: 0000000000000282
(XEN) rax: 00000000ffffffea   rbx: 00000000000001fe   rcx:
ffffffff8011e49d   rdx: 0000000000000000
(XEN) rsi: 0000000000000001   rdi: ffffffff80567e90   rbp:
0000000000802000   rsp: ffffffff80567e58
(XEN) r8:  0000000000000004   r9:  0000000000000000   r10:
0000000000007ff0   r11: 0000000000000202
(XEN) r12: ffffffff80802000   r13: ffffffff80568000   r14:
ffffffff80105020   r15: ffffffff80105000
(XEN) Guest stack trace from rsp=ffffffff80567e58:
(XEN)    ffffffff8011e49d 0000000000000202 ffffffff8011e4a1
000000010000e030 0000000000010282 ffffffff80567e90 000000000000e02b
0000000060568008
(XEN)    000000007ffff067 0000000000800000 ffffffff80592686
0000000000568000 0000000000000000 000000000000001b 0000000000000000
0000000020000000
(XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff80592cd3
0000000000000000 0000000000000000 000000000000001b ffffffff805093bb
ffffffff80567fa0
(XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff8058eada
000000006064e830 ffffffff80502dbc 0000000000000001 0000000000060105
0000000000000000
(XEN)    ffffffff80103000 ffffffff0000000f 0000000000010800
ffffffff80452900 ffffffff80100038 00000000ffffffff 0000ffffffff8010
ffffffff80567fb0
(XEN)    ffffffff805884f8 ffffffff805093a0 ffffffff80588190
80108e0000100038 00000000ffffffff 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000
(XEN) Domain 0 shutdown: rebooting machine.


> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Nakajima, Jun
> Sent: Wednesday, August 10, 2005 2:25 PM
> To: Puthiyaparambil, Aravindh; Keir Fraser
> Cc: xen-devel@lists.xensource.com; Davis, Jason; Magolan, John F;
> Subrahmanian, Raj; Vessey, Bruce A
> Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000
x86_64> 
> Puthiyaparambil, Aravindh wrote:
> > Xen and Dom0 boots successfully on the Dell PowerEdge x86_64 box
with> > Keir''s new time fix. I did have to comment out the printk as
suggested> > by Jun as the serial was getting flooded otherwise.
> >
> > Jun, are you going to submit a patch for the map_alloc() function?
> >
> > On the ES7000 x86_64 I no longer see the "Assertion
''tsc_elapsed32!> > 0''". But the system dies on the error shown at the end
of the email.> > This is with changeset 6081 + Jun''s map_alloc fix +
Jerone''s rm_nx
> > patch. Any suggestions as to how to proceed?
> 
> Can you try to add mem=3g for the xen boot entry?
> 
> Jun
> ---
> Intel Open Source Technology Center
> 
> >
> > Thanks
> > Aravindh
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Puthiyaparambil, Aravindh

2005-Aug-10 21:14 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Here is the disassembly output from vmlinux-syms-2.6.12.3-xen0. I am
wondering if I have a bad stack. The EIP points to 0xffffffff8011e4a1
<xen_l1_entry_update+113>:   ud2a

What does ud2a do?

Aravindh

Dump of assembler code from 0xffffffff8011e410 to 0xffffffff8011e4b0:
0xffffffff8011e410 <xen_l2_entry_update+112>:   (bad)
0xffffffff8011e411 <xen_l2_entry_update+113>:   ud2a
0xffffffff8011e413 <xen_l2_entry_update+115>:   enterq $0x3f30,$0x80
0xffffffff8011e417 <xen_l2_entry_update+119>:   (bad)
0xffffffff8011e418 <xen_l2_entry_update+120>:   (bad)
0xffffffff8011e419 <xen_l2_entry_update+121>:   (bad)
0xffffffff8011e41a <xen_l2_entry_update+122>:   decl   0x0(%rax)
0xffffffff8011e41d <xen_l2_entry_update+125>:   data16
0xffffffff8011e41e <xen_l2_entry_update+126>:   data16
0xffffffff8011e41f <xen_l2_entry_update+127>:   nop
0xffffffff8011e420 <xen_l2_entry_update+128>:   add    $0x18,%rsp
0xffffffff8011e424 <xen_l2_entry_update+132>:   retq
0xffffffff8011e425 <xen_l2_entry_update+133>:   data16
0xffffffff8011e426 <xen_l2_entry_update+134>:   data16
0xffffffff8011e427 <xen_l2_entry_update+135>:   data16
0xffffffff8011e428 <xen_l2_entry_update+136>:   nop
0xffffffff8011e429 <xen_l2_entry_update+137>:   data16
0xffffffff8011e42a <xen_l2_entry_update+138>:   data16
0xffffffff8011e42b <xen_l2_entry_update+139>:   data16
0xffffffff8011e42c <xen_l2_entry_update+140>:   nop
0xffffffff8011e42d <xen_l2_entry_update+141>:   data16
0xffffffff8011e42e <xen_l2_entry_update+142>:   data16
0xffffffff8011e42f <xen_l2_entry_update+143>:   nop
0xffffffff8011e430 <xen_l1_entry_update+0>:     mov
$0xffffffff7fffffff,%rax
0xffffffff8011e43a <xen_l1_entry_update+10>:    sub    $0x18,%rsp
0xffffffff8011e43e <xen_l1_entry_update+14>:    cmp    %rax,%rdi
0xffffffff8011e441 <xen_l1_entry_update+17>:    jbe
0xffffffff8011e450 <xen_l1_entry_update+32>
0xffffffff8011e443 <xen_l1_entry_update+19>:    mov    $0x80000000,%eax
0xffffffff8011e448 <xen_l1_entry_update+24>:    jmp
0xffffffff8011e45a <xen_l1_entry_update+42>
0xffffffff8011e44a <xen_l1_entry_update+26>:    data16
0xffffffff8011e44b <xen_l1_entry_update+27>:    data16
0xffffffff8011e44c <xen_l1_entry_update+28>:    nop
0xffffffff8011e44d <xen_l1_entry_update+29>:    data16
0xffffffff8011e44e <xen_l1_entry_update+30>:    data16
0xffffffff8011e44f <xen_l1_entry_update+31>:    nop
0xffffffff8011e450 <xen_l1_entry_update+32>:    mov
$0x780000000000,%rax
0xffffffff8011e45a <xen_l1_entry_update+42>:    lea
(%rax,%rdi,1),%rcx
0xffffffff8011e45e <xen_l1_entry_update+46>:    mov
4102811(%rip),%rdx        # 0xffffffff80507f00 <phys_to_machine_mapping>
0xffffffff8011e465 <xen_l1_entry_update+53>:    mov    %rsp,%rdi
0xffffffff8011e468 <xen_l1_entry_update+56>:    mov    %rcx,%rax
0xffffffff8011e46b <xen_l1_entry_update+59>:    and    $0xfff,%ecx
0xffffffff8011e471 <xen_l1_entry_update+65>:    shr    $0xc,%rax
0xffffffff8011e475 <xen_l1_entry_update+69>:    mov    %eax,%eax
0xffffffff8011e477 <xen_l1_entry_update+71>:    mov
(%rdx,%rax,4),%eax
0xffffffff8011e47a <xen_l1_entry_update+74>:    mov    %rsi,0x8(%rsp)
0xffffffff8011e47f <xen_l1_entry_update+79>:    mov    $0x1,%esi
0xffffffff8011e484 <xen_l1_entry_update+84>:    xor    %edx,%edx
0xffffffff8011e486 <xen_l1_entry_update+86>:    shl    $0xc,%rax
0xffffffff8011e48a <xen_l1_entry_update+90>:    or     %rcx,%rax
0xffffffff8011e48d <xen_l1_entry_update+93>:    mov    %rax,(%rsp)
0xffffffff8011e491 <xen_l1_entry_update+97>:    mov    %rsi,%rax
0xffffffff8011e494 <xen_l1_entry_update+100>:   mov    $0x7ff0,%r10
0xffffffff8011e49b <xen_l1_entry_update+107>:   syscall
0xffffffff8011e49d <xen_l1_entry_update+109>:   test   %eax,%eax
0xffffffff8011e49f <xen_l1_entry_update+111>:   jns
0xffffffff8011e4b0 <xen_l1_entry_update+128>
0xffffffff8011e4a1 <xen_l1_entry_update+113>:   ud2a
0xffffffff8011e4a3 <xen_l1_entry_update+115>:   enterq $0x3f30,$0x80
0xffffffff8011e4a7 <xen_l1_entry_update+119>:   (bad)
0xffffffff8011e4a8 <xen_l1_entry_update+120>:   (bad)
0xffffffff8011e4a9 <xen_l1_entry_update+121>:   (bad)
0xffffffff8011e4aa <xen_l1_entry_update+122>:   incl   0x0(%rax)
0xffffffff8011e4ad <xen_l1_entry_update+125>:   data16
0xffffffff8011e4ae <xen_l1_entry_update+126>:   data16
0xffffffff8011e4af <xen_l1_entry_update+127>:   nop

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Puthiyaparambil, Aravindh
> Sent: Wednesday, August 10, 2005 2:36 PM
> To: Nakajima, Jun; Keir Fraser
> Cc: xen-devel@lists.xensource.com; Davis, Jason; Magolan, John F;
> Subrahmanian, Raj; Vessey, Bruce A
> Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000
x86_64> 
> With mem=3g dom0_mem=512M this is what happens...
> 
> Aravindh
> 
> (XEN) Truncating memory map to 3145728kB
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009dc00 (usable)
> (XEN)  000000000009dc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000ce000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 0000000037ea0000 (usable)
> (XEN)  0000000037ea0000 - 0000000037edf000 (ACPI data)
> (XEN)  0000000037edf000 - 0000000037f00000 (ACPI NVS)
> (XEN)  0000000037f00000 - 00000000c0000000 (usable)
> (XEN) System RAM: 3071MB (3144948kB)
> (XEN) Xen heap: 14MB (14580kB)
> 
> ...................................
> 
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
>
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80000000,L> OADER=generic''
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000060000000->0000000080000000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff805cc086
> (XEN)  Init. ramdisk: ffffffff805cd000->ffffffff805cd000
> (XEN)  Phys-Mach map: ffffffff805cd000->ffffffff8064d000
> (XEN)  Page tables:   ffffffff8064d000->ffffffff80654000
> (XEN)  Start info:    ffffffff80654000->ffffffff80655000
> (XEN)  Boot stack:    ffffffff80655000->ffffffff80656000
> (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) (file=/root/xen/xen-unstable.hg/xen/include/asm/mm.h, line=204)
> Error pfn 7ffff: rd=ffff8300001c8080, od=0000000000000000,
caf=00000000,> taf=0000000000000000
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) CPU:    0
> (XEN) EIP:    e033:[<ffffffff8011e4a1>] ???
> (XEN) EFLAGS: 0000000000000282
> (XEN) rax: 00000000ffffffea   rbx: 00000000000001fe   rcx:
> ffffffff8011e49d   rdx: 0000000000000000
> (XEN) rsi: 0000000000000001   rdi: ffffffff80567e90   rbp:
> 0000000000802000   rsp: ffffffff80567e58
> (XEN) r8:  0000000000000004   r9:  0000000000000000   r10:
> 0000000000007ff0   r11: 0000000000000202
> (XEN) r12: ffffffff80802000   r13: ffffffff80568000   r14:
> ffffffff80105020   r15: ffffffff80105000
> (XEN) Guest stack trace from rsp=ffffffff80567e58:
> (XEN)    ffffffff8011e49d 0000000000000202 ffffffff8011e4a1
> 000000010000e030 0000000000010282 ffffffff80567e90 000000000000e02b
> 0000000060568008
> (XEN)    000000007ffff067 0000000000800000 ffffffff80592686
> 0000000000568000 0000000000000000 000000000000001b 0000000000000000
> 0000000020000000
> (XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff80592cd3
> 0000000000000000 0000000000000000 000000000000001b ffffffff805093bb
> ffffffff80567fa0
> (XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff8058eada
> 000000006064e830 ffffffff80502dbc 0000000000000001 0000000000060105
> 0000000000000000
> (XEN)    ffffffff80103000 ffffffff0000000f 0000000000010800
> ffffffff80452900 ffffffff80100038 00000000ffffffff 0000ffffffff8010
> ffffffff80567fb0
> (XEN)    ffffffff805884f8 ffffffff805093a0 ffffffff80588190
> 80108e0000100038 00000000ffffffff 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000
> (XEN) Domain 0 shutdown: rebooting machine.
> 
> 
> 
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> > bounces@lists.xensource.com] On Behalf Of Nakajima, Jun
> > Sent: Wednesday, August 10, 2005 2:25 PM
> > To: Puthiyaparambil, Aravindh; Keir Fraser
> > Cc: xen-devel@lists.xensource.com; Davis, Jason; Magolan, John F;
> > Subrahmanian, Raj; Vessey, Bruce A
> > Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000
> x86_64
> >
> > Puthiyaparambil, Aravindh wrote:
> > > Xen and Dom0 boots successfully on the Dell PowerEdge x86_64 box
> with
> > > Keir''s new time fix. I did have to comment out the
printk as
> suggested
> > > by Jun as the serial was getting flooded otherwise.
> > >
> > > Jun, are you going to submit a patch for the map_alloc()
function?
> > >
> > > On the ES7000 x86_64 I no longer see the "Assertion
''tsc_elapsed32
> !> > > 0''". But the system dies on the error shown
at the end of the
email.> > > This is with changeset 6081 + Jun''s map_alloc fix +
Jerone''s rm_nx
> > > patch. Any suggestions as to how to proceed?
> >
> > Can you try to add mem=3g for the xen boot entry?
> >
> > Jun
> > ---
> > Intel Open Source Technology Center
> >
> > >
> > > Thanks
> > > Aravindh
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Chris Wright

2005-Aug-10 21:17 UTC

head link

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

* Puthiyaparambil, Aravindh (aravindh.puthiyaparambil@unisys.com)
wrote:> Here is the disassembly output from vmlinux-syms-2.6.12.3-xen0. I am
> wondering if I have a bad stack. The EIP points to 0xffffffff8011e4a1
> <xen_l1_entry_update+113>:   ud2a
> 
> What does ud2a do?
That should be BUG()

thanks,
-chris

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

Nakajima, Jun

2005-Aug-10 21:51 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Puthiyaparambil, Aravindh wrote:> With mem=3g dom0_mem=512M this is what happens...
How about non-debug xen? I also see similar problems with debug xen.

Jun
---
Intel Open Source Technology Center
> 
> Aravindh
> 
> (XEN) Truncating memory map to 3145728kB
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009dc00 (usable)
> (XEN)  000000000009dc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000ce000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 0000000037ea0000 (usable)
> (XEN)  0000000037ea0000 - 0000000037edf000 (ACPI data)
> (XEN)  0000000037edf000 - 0000000037f00000 (ACPI NVS)
> (XEN)  0000000037f00000 - 00000000c0000000 (usable)
> (XEN) System RAM: 3071MB (3144948kB)
> (XEN) Xen heap: 14MB (14580kB)
> 
> ...................................
> 
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
>
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80000000,L> OADER=generic''
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000060000000->0000000080000000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff805cc086
> (XEN)  Init. ramdisk: ffffffff805cd000->ffffffff805cd000
> (XEN)  Phys-Mach map: ffffffff805cd000->ffffffff8064d000
> (XEN)  Page tables:   ffffffff8064d000->ffffffff80654000
> (XEN)  Start info:    ffffffff80654000->ffffffff80655000
> (XEN)  Boot stack:    ffffffff80655000->ffffffff80656000
> (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) (file=/root/xen/xen-unstable.hg/xen/include/asm/mm.h, line=204)
> Error pfn 7ffff: rd=ffff8300001c8080, od=0000000000000000,
> caf=00000000, taf=0000000000000000
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) CPU:    0
> (XEN) EIP:    e033:[<ffffffff8011e4a1>] ???
> (XEN) EFLAGS: 0000000000000282
> (XEN) rax: 00000000ffffffea   rbx: 00000000000001fe   rcx:
> ffffffff8011e49d   rdx: 0000000000000000
> (XEN) rsi: 0000000000000001   rdi: ffffffff80567e90   rbp:
> 0000000000802000   rsp: ffffffff80567e58
> (XEN) r8:  0000000000000004   r9:  0000000000000000   r10:
> 0000000000007ff0   r11: 0000000000000202
> (XEN) r12: ffffffff80802000   r13: ffffffff80568000   r14:
> ffffffff80105020   r15: ffffffff80105000
> (XEN) Guest stack trace from rsp=ffffffff80567e58:
> (XEN)    ffffffff8011e49d 0000000000000202 ffffffff8011e4a1
> 000000010000e030 0000000000010282 ffffffff80567e90 000000000000e02b
> 0000000060568008
> (XEN)    000000007ffff067 0000000000800000 ffffffff80592686
> 0000000000568000 0000000000000000 000000000000001b 0000000000000000
> 0000000020000000
> (XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff80592cd3
> 0000000000000000 0000000000000000 000000000000001b ffffffff805093bb
> ffffffff80567fa0
> (XEN)    0000ffffffff8010 ffffffff80567fb0 ffffffff8058eada
> 000000006064e830 ffffffff80502dbc 0000000000000001 0000000000060105
> 0000000000000000
> (XEN)    ffffffff80103000 ffffffff0000000f 0000000000010800
> ffffffff80452900 ffffffff80100038 00000000ffffffff 0000ffffffff8010
> ffffffff80567fb0
> (XEN)    ffffffff805884f8 ffffffff805093a0 ffffffff80588190
> 80108e0000100038 00000000ffffffff 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000
> (XEN) Domain 0 shutdown: rebooting machine.
> 
> 
> 
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>> bounces@lists.xensource.com] On Behalf Of Nakajima, Jun
>> Sent: Wednesday, August 10, 2005 2:25 PM
>> To: Puthiyaparambil, Aravindh; Keir Fraser
>> Cc: xen-devel@lists.xensource.com; Davis, Jason; Magolan, John F;
>> Subrahmanian, Raj; Vessey, Bruce A
>> Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000
>> x86_64 
>> 
>> Puthiyaparambil, Aravindh wrote:
>>> Xen and Dom0 boots successfully on the Dell PowerEdge x86_64 box
>>> with Keir''s new time fix. I did have to comment out the
printk as
>>> suggested by Jun as the serial was getting flooded otherwise.
>>> 
>>> Jun, are you going to submit a patch for the map_alloc() function?
>>> 
>>> On the ES7000 x86_64 I no longer see the "Assertion
''tsc_elapsed32
>>> != 0''". But the system dies on the error shown at the
end of the
>>> email. This is with changeset 6081 + Jun''s map_alloc fix +
Jerone''s
>>> rm_nx patch. Any suggestions as to how to proceed?
>> 
>> Can you try to add mem=3g for the xen boot entry?
>> 
>> Jun
>> ---
>> Intel Open Source Technology Center
>> 
>>> 
>>> Thanks
>>> Aravindh



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

Puthiyaparambil, Aravindh

2005-Aug-11 00:17 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

I am seeing the same crash with non-debug Xen.

Aravindh

(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU:    0
(XEN) EIP:    e033:[<ffffffff8011e04c>] ???
(XEN) EFLAGS: 0000000000000282
(XEN) rax: 00000000ffffffea   rbx: 0000000004e00000   rcx:
ffffffff8011e048   rdx: 0000000000000000
(XEN) rsi: 0000000000000001   rdi: ffffffff80567e70   rbp:
0000000020000000   rsp: ffffffff80567e38
(XEN) r8:  0000000000000200   r9:  0000000000000000   r10:
0000000000007ff0   r11: 0000000000000246
(XEN) r12: ffffffff80801130   r13: 0000000000000026   r14:
ffffffff80800000   r15: 0000000000000000
(XEN) Guest stack trace from rsp=ffffffff80567e38:
(XEN)    ffffffff8011e048 0000000000000246 ffffffff8011e04c
000000010000e030 0000000000010282 ffffffff80567e70 000000000000e02b
0000000000000000
(XEN)    0000000000060828 0000000060801128 0000000004e00000
0000000020000000 ffffffff80592be9 0000000000000000 0000000000828000
0000000000801000
(XEN)    ffffffff80800000 ffff880020000000 ffff880000000000
ffff880020000000 0000780000000000 0000000080000000 ffffffff80592d81
0000000000800000
(XEN)    0000000000000000 000000000000001b ffffffff805093bb
ffffffff80567fa0 0000ffffffff8010 ffffffff80567fb0 ffffffff8058eada
000000006064e830
(XEN)    ffffffff80502dbc 0000000000000001 0000000000060105
0000000000000000 ffffffff80103000 ffffffff0000000f 0000000000010800
ffffffff80452900
(XEN)    ffffffff80100038 00000000ffffffff 0000ffffffff8010
ffffffff80567fb0 ffffffff805884f8 ffffffff805093a0 ffffffff80588190
80108e0000100038
(XEN)    00000000ffffffff 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000
(XEN) Domain 0 shutdown: rebooting machine.

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Nakajima, Jun
> Sent: Wednesday, August 10, 2005 5:52 PM
> To: Puthiyaparambil, Aravindh; Keir Fraser
> Cc: xen-devel@lists.xensource.com; Davis, Jason; Magolan, John F;
> Subrahmanian, Raj; Vessey, Bruce A
> Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000
x86_64> 
> Puthiyaparambil, Aravindh wrote:
> > With mem=3g dom0_mem=512M this is what happens...
> 
> How about non-debug xen? I also see similar problems with debug xen.
> 
> Jun
> ---
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keir Fraser

2005-Aug-11 08:51 UTC

head link

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

On 10 Aug 2005, at 19:18, Puthiyaparambil, Aravindh wrote:
> Jun, are you going to submit a patch for the map_alloc() function?
>
> On the ES7000 x86_64 I no longer see the "Assertion
''tsc_elapsed32 !> 0''". But the system dies on the
error shown at the end of the email.
> This is with changeset 6081 + Jun''s map_alloc fix +
Jerone''s rm_nx
> patch. Any suggestions as to how to proceed?
I fixed the map_alloc() problem already. The symptoms here are quite 
different anyway. It''s almost certainly a different bug.

  -- Keir


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

Nakajima, Jun

2005-Aug-11 14:49 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Keir Fraser wrote:> On 10 Aug 2005, at 19:18, Puthiyaparambil, Aravindh wrote:
> 
>> Jun, are you going to submit a patch for the map_alloc() function?
>> 
>> On the ES7000 x86_64 I no longer see the "Assertion
''tsc_elapsed32 !>> 0''". But the system dies on the
error shown at the end of the email.
>> This is with changeset 6081 + Jun''s map_alloc fix +
Jerone''s rm_nx
>> patch. Any suggestions as to how to proceed?
> 
> I fixed the map_alloc() problem already. The symptoms here are quite
> different anyway. It''s almost certainly a different bug.Agree.

BTW, the machine has discontiguous memory regions (3 of them for >0x100000),
and the 0x100000 one has less than 1GB (892MB). I guess it
would work if mem=512m is set.

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009dc00 (usable)
(XEN)  000000000009dc00 - 00000000000a0000 (reserved)
(XEN)  00000000000ce000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000037ea0000 (usable)
(XEN)  0000000037ea0000 - 0000000037edf000 (ACPI data)
(XEN)  0000000037edf000 - 0000000037f00000 (ACPI NVS)
(XEN)  0000000037f00000 - 00000000e8000000 (usable)
(XEN)  00000000f8000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000110000000 (usable)
(XEN) System RAM: 3967MB (4062452kB)
> 
>   -- Keir

Jun
---
Intel Open Source Technology Center

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

Keir Fraser

2005-Aug-11 16:06 UTC

head link

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

On 11 Aug 2005, at 15:49, Nakajima, Jun wrote:
>
> BTW, the machine has discontiguous memory regions (3 of them for >>
0x100000), and the 0x100000 one has less than 1GB (892MB). I guess it
> would work if mem=512m is set.
We should work correctly for memory holes above about 16MB.

  -- Keir


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

Puthiyaparambil, Aravindh

2005-Aug-11 17:30 UTC

head link

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

I can no longer reproduce (banging head against wall) the issue [Domain
0 (vcpu#0) crashed on cpu#0] with the 6093 changeset!!! This is with
both the debug and non-debug versions. Maybe changeset 6091 fixed the
problem. I am a little uncomfortable that I don''t the know root cause
of
the problem. I hope this does not come back later.
Jun, Keir, thanks for all your help with this. 

Now Xen boots but in Dom0 the system starts to lose interrupts. This is
because the x86_64 SMP patch submitted by Chris Wright (changeset 6090)
always puts the system in flat APIC mode in Dom0. The ES7000 x86_64
needs to be in clustered APIC mode. We need to come up with a way to
accommodate clustered APIC mode in genapic_xen. Someone at Unisys will
look into this and come out with a patch.

Thanks,
Aravindh
> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk]
> Sent: Thursday, August 11, 2005 12:06 PM
> To: Nakajima, Jun
> Cc: xen-devel@lists.xensource.com; Puthiyaparambil, Aravindh; Magolan,
> John F; Vessey, Bruce A; Subrahmanian, Raj; Davis, Jason
> Subject: Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000
x86_64> 
> 
> On 11 Aug 2005, at 15:49, Nakajima, Jun wrote:
> 
> >
> > BTW, the machine has discontiguous memory regions (3 of them for
>> > 0x100000), and the 0x100000 one has less than 1GB (892MB). I guess
it> > would work if mem=512m is set.
> 
> We should work correctly for memory holes above about 16MB.
> 
>   -- Keir

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

Xen devel - Aug 2005 - Unknown interrupt on x86_64 Xen on ES7000 x86_64

[Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64