xen-devel
RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64
To: |
"Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> |
Subject: |
RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64 |
From: |
"Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx> |
Date: |
Wed, 10 Aug 2005 01:39:10 -0400 |
Cc: |
xen-devel@xxxxxxxxxxxxxxxxxxx, "Davis, Jason" <jason.davis@xxxxxxxxxx>, "Magolan, John F" <John.Magolan@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx> |
Delivery-date: |
Wed, 10 Aug 2005 05:38:39 +0000 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
AcWdAZeo7cFZVA22QViz6u3TsjtZZwAR8SiAAAapuMAAAlRYsA== |
Thread-topic: |
[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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Puthiyaparambil, Aravindh
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Puthiyaparambil, Aravindh
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Puthiyaparambil, Aravindh
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Nakajima, Jun
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64,
Puthiyaparambil, Aravindh <=
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Li, Xin B
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Nakajima, Jun
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Puthiyaparambil, Aravindh
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Nakajima, Jun
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Puthiyaparambil, Aravindh
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Puthiyaparambil, Aravindh
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Nakajima, Jun
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, Puthiyaparambil, Aravindh
|
|
|