Re: [Xen-devel] cpuidle and un-eoid interrupts at the local apic

["Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>]

Probably you can use a non-Xen kernel to boot up the system, and then you can 
get the micro-code in cpuinfo.  Thanks!
Xiantao

-----Original Message-----
From: Thimo E. [mailto:abc@xxxxxxxxxx] 
Sent: Wednesday, September 18, 2013 5:05 AM
To: Zhang, Yang Z
Cc: Keir Fraser; Jan Beulich; Andrew Cooper; Dong, Eddie; Xen-develList; 
Nakajima, Jun; Zhang, Xiantao
Subject: Re: [Xen-devel] cpuidle and un-eoid interrupts at the local apic

Hello,

unfortunately the Xenserver kernel seems to not support reading the microcode, 
at least it is not populated in /proc/cpuinfo.
Andrew, are there any special tricks to get the version out of the Xenserver 
kernel ?

Best regards
   Thimo


Am 17.09.2013 09:43, schrieb Zhang, Yang Z:
> Thimo E. wrote on 2013-09-17:
>> Hello Yang,
>>
>> The problem that we are discussing here seems to come from the 
>> interaction of my raid controller (Areca, ARC-1212) and the hardware.
>> When I enable MSI on that controller the server crashes with the 
>> known error messages between 1 day and 7 days.  When I disable MSI I 
>> don't see these crashes anymore.
>>
>> Andrew doesn't have this controller but he could also observe these 
>> type of crashes with another MSI enabled card, I think the networc 
>> card. But less often, I think 2 times in the last 4 months.
>>
>> My cpuinfo nor dmesg show any microcode information, perhaps Xen 
>> hides that info ?!
> 'cat /proc/cpuinfo' will show the microcode version.
> Best regards,
> Yang
>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel