| 
         
xen-devel
RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64
 
| 
To:  | 
"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>,	"Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx> | 
 
| 
Subject:  | 
RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64 | 
 
| 
From:  | 
"Nakajima, Jun" <jun.nakajima@xxxxxxxxx> | 
 
| 
Date:  | 
Thu, 11 Aug 2005 07:49:29 -0700 | 
 
| 
Cc:  | 
"Davis, Jason" <jason.davis@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx,	"Magolan, John F" <John.Magolan@xxxxxxxxxx>, "Vessey,	Bruce A" <Bruce.Vessey@xxxxxxxxxx>, "Subrahmanian,	Raj" <raj.subrahmanian@xxxxxxxxxx> | 
 
| 
Delivery-date:  | 
Thu, 11 Aug 2005 14:48:15 +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:  | 
AcWeUUuZX+QxvAq/S+GCEhfMpG8QNgAL7/wQ | 
 
| 
Thread-topic:  | 
[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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread>
 |  
- RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64, (continued)
- 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
 
- 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
 
 
 
 
 |  
  
 | 
    |