Re: [Xen-ia64-devel] MCA patches causing Xen to hang on sn2

[Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>]

Hi Jes,

For Xen boot option, you have to specify "nomca" in the left side of append 
line.
For Dom0 boot option, you have to specify "nomca" in the right side of append 
line.

Example:
 append="nomca com2=115200,8n1 console=com2 -- nomca console=tty0 
console=ttyS1,115200,8n1 rhgb root=/dev/sda2"
               <---- Xen boot options ----+    +---- Dom0 boot options ---->

If you cannot start up Xen/Dom0, please stop the salinfod in Dom0.
Nevertheless if you cannot start up Xen/Dom0, could you send the serial log to 
me?

Best regards,
 Kan

>SUZUKI Kazuhiro wrote:
>> Hi Jes,
>> 
>>> I tried this and attached the output below. I was wondering why we
>>> seem to allocate pages to MCA handlers on 64 processors even if we
>>> only boot 8, but thats a detail.
>> 
>>   It's OK. The mca_data is allocated up to NR_CPUS(=64) in MCA
>> initialization routine. 
>> 
>>>>    And I think that your system will boot up if "nomca" is specified
>>>> in boot parameters.
>>> This didn't make any difference :(
>> 
>>   Please confirm whether to have specified "nomca" for not only the 
>> Domain0 boot parameter but also Xen. And please send me a boot log
>> with "nomca" too.
>> 
>> Thanks,
>> KAZ
>
>Hi Kaz,
>
>I just did 'nomca' on the boot line. Can you explain to me how I do
>it for dom0 too?
>
>Thanks,
>Jes
>
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel


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