Re: [Xen-devel] Regression, host crash with 4.5rc1

[Steve Freitas <sflist@xxxxxxxxx>]

On Nov 24, 2014, at 00:45, Jan Beulich <JBeulich@xxxxxxxx> wrote:

>>>> On 23.11.14 at 02:28, <sflist@xxxxxxxxx> wrote:
>> With mwait-idle=0:
>> 
>> (XEN) 'c' pressed -> printing ACPI Cx structures
>> (XEN) ==cpu0==
>> (XEN) active state:             C0
>> (XEN) max_cstate:               C7
>> (XEN) states:
>> (XEN)     C1:   type[C1] latency[001] usage[00000000] method[  FFH] 
>> duration[0]
>> (XEN)     C2:   type[C0] latency[000] usage[00000000] method[ NONE] 
>> duration[0]
>> (XEN)     C3:   type[C3] latency[064] usage[00000000] method[  FFH] 
>> duration[0]
>> (XEN)     C4:   type[C3] latency[096] usage[00000000] method[  FFH] 
>> duration[0]
>> (XEN)    *C0:   usage[00000000] duration[46930624784]
>> (XEN) PC2[0] PC3[0] PC6[0] PC7[0]
>> (XEN) CC3[0] CC6[0] CC7[0]
>> [...]
> 
> Very interesting - the hypervisor has C-state information, but never
> entered any of them. That certainly explains the difference between
> using/not using the ,wait-idle driver, but puts us back to there being
> a more general issue with C-state use on this CPU model. Possibly
> related to C2 having entry method "NONE", but then again I can't
> see how such a state could get entered into the table the first place:
> set_cx() bails upon check_cx() returning an error, and hence its
> switch()'s default statement should never be reached. Plus even if an
> array entry was set to "NONE", it should simply be ignored when
> looking for a state to enter. I'll probably need to put together a
> debugging patch to figure out what's going on here.
> 

Okay, happy to give it a go whenever you have the time to put something 
together.

> 
>> 
>> As promised, below is the apic-verbosity=debug log, with 'i'. Thanks!
> 
> I'm sorry, I misspelled the option, it's really "apic_verbosity=debug".
> The 'i' output at least already confirms that there are no ExtINT
> entries among the IO-APIC RTEs.
> 
> 

No sweat. Do you need me to run it again with the corrected option?

Thanks!

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