From: Steve Freitas <sflist@ihonk.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Don Slutz <dslutz@verizon.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Regression, host crash with 4.5rc1
Date: Wed, 26 Nov 2014 21:29:12 -0800 [thread overview]
Message-ID: <5476B6A8.4060706@ihonk.com> (raw)
In-Reply-To: <54746F59020000780004A9E9@mail.emea.novell.com>
On 11/25/2014 03:00 AM, Jan Beulich wrote:
> Okay, so it's not really the mwait-idle driver causing the regression,
> but it is C-state related. Hence we're now down to seeing whether all
> or just the deeper C states are affected, i.e. I now need to ask you
> to play with "max_cstate=". For that you'll have to remember that the
> option's effect differs between the ACPI and the MWAIT idle drivers.
> In the spirit of bisection I'd suggest using "max_cstate=2" first no
> matter which of the two scenarios you pick. If that still hangs,
> "max_cstate=1" obviously is the only other thing to try. Should that
> not hang (and you left out "mwait-idle=0"), trying "max_cstate=3"
> in that same scenario would be the other case to check.
>
> No need for 'd' and 'a' output for the time being, but 'c' output would
> be much appreciated for all cases where you observe hangs.
>
Okay, working through that now. I tried max_cstate=2 and got no hangs,
whether with or without mwait-idle=0. However, I was puzzled by this:
(XEN) 'c' pressed -> printing ACPI Cx structures
(XEN) ==cpu0==
(XEN) active state: C0
(XEN) max_cstate: C2
(XEN) states:
(XEN) C1: type[C1] latency[003] usage[12219860] method[ FFH]
duration[1190961948551]
(XEN) C2: type[C1] latency[010] usage[10205554] method[ FFH]
duration[2015393965907]
(XEN) C3: type[C2] latency[020] usage[50926286] method[ FFH]
duration[30527997858148]
(XEN) *C0: usage[73351700] duration[9974627547595]
(XEN) max=0 pwr=0 urg=0 nxt=0
(XEN) PC2[0] PC3[8589642315848] PC6[0] PC7[0]
(XEN) CC3[28794734145697] CC6[0] CC7[0]
(XEN) ==cpu1==
(XEN) active state: C3
(XEN) max_cstate: C2
(XEN) states:
(XEN) C1: type[C1] latency[003] usage[10699950] method[ FFH]
duration[1141422044112]
(XEN) C2: type[C1] latency[010] usage[06382904] method[ FFH]
duration[1329739264322]
(XEN) *C3: type[C2] latency[020] usage[44630764] method[ FFH]
duration[31676618425954]
(XEN) C0: usage[61713618] duration[9561201640320]
(XEN) max=0 pwr=0 urg=0 nxt=0
(XEN) PC2[0] PC3[8589642315848] PC6[0] PC7[0]
(XEN) CC3[30066495105056] CC6[0] CC7[0]
(XEN) ==cpu2==
(XEN) active state: C3
(XEN) max_cstate: C2
(XEN) states:
(XEN) C1: type[C1] latency[003] usage[10829791] method[ FFH]
duration[1145244102917]
(XEN) C2: type[C1] latency[010] usage[06392468] method[ FFH]
duration[1330830147023]
(XEN) *C3: type[C2] latency[020] usage[44705668] method[ FFH]
duration[31741190985486]
(XEN) C0: usage[61927927] duration[9491716216846]
(XEN) max=0 pwr=0 urg=0 nxt=0
(XEN) PC2[0] PC3[8589642315848] PC6[0] PC7[0]
(XEN) CC3[30117696095715] CC6[0] CC7[0]
(XEN) ==cpu3==
(XEN) active state: C3
(XEN) max_cstate: C2
(XEN) states:
(XEN) C1: type[C1] latency[003] usage[10692336] method[ FFH]
duration[1144876437514]
(XEN) C2: type[C1] latency[010] usage[06394051] method[ FFH]
duration[1333961503379]
(XEN) *C3: type[C2] latency[020] usage[44744178] method[ FFH]
duration[31803488799434]
(XEN) C0: usage[61830565] duration[9426654792908]
(XEN) max=0 pwr=0 urg=0 nxt=0
(XEN) PC2[0] PC3[8589642315848] PC6[0] PC7[0]
(XEN) CC3[30191557548300] CC6[0] CC7[0]
(XEN) ==cpu4==
(XEN) active state: C3
(XEN) max_cstate: C2
(XEN) states:
(XEN) C1: type[C1] latency[003] usage[10746634] method[ FFH]
duration[1144044534459]
(XEN) C2: type[C1] latency[010] usage[06444054] method[ FFH]
duration[1340637424913]
(XEN) *C3: type[C2] latency[020] usage[44690901] method[ FFH]
duration[31663207165902]
(XEN) C0: usage[61881589] duration[9561092487876]
(XEN) max=0 pwr=0 urg=0 nxt=0
(XEN) PC2[0] PC3[8589642315848] PC6[0] PC7[0]
(XEN) CC3[30049235012919] CC6[0] CC7[0]
(XEN) ==cpu5==
(XEN) active state: C3
(XEN) max_cstate: C2
(XEN) states:
(XEN) C1: type[C1] latency[003] usage[10694684] method[ FFH]
duration[1140625901110]
(XEN) C2: type[C1] latency[010] usage[06461563] method[ FFH]
duration[1342115502967]
(XEN) *C3: type[C2] latency[020] usage[44834522] method[ FFH]
duration[31719560664023]
(XEN) C0: usage[61990769] duration[9506679619986]
(XEN) max=0 pwr=0 urg=0 nxt=0
(XEN) PC2[0] PC3[8589642315848] PC6[0] PC7[0]
Why would some of the cores be in C3 even though they list max_cstate as C2?
Steve
next prev parent reply other threads:[~2014-11-27 5:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 21:46 Regression, host crash with 4.5rc1 Steve Freitas
2014-11-03 21:52 ` Steve Freitas
2014-11-04 14:01 ` Don Slutz
2014-11-04 8:20 ` Pasi Kärkkäinen
2014-11-04 10:15 ` Jan Beulich
2014-11-10 8:03 ` Steve Freitas
2014-11-10 8:51 ` Jan Beulich
2014-11-10 20:05 ` Steve Freitas
2014-11-11 8:05 ` Jan Beulich
2014-11-17 19:21 ` Steve Freitas
2014-11-18 7:54 ` Jan Beulich
2014-11-20 1:23 ` Steve Freitas
2014-11-20 7:59 ` Jan Beulich
2014-11-20 20:07 ` Steve Freitas
2014-11-21 8:42 ` Jan Beulich
2014-11-23 1:28 ` Steve Freitas
2014-11-24 8:45 ` Jan Beulich
2014-11-24 9:08 ` Steve Freitas
2014-11-24 9:15 ` Jan Beulich
2014-11-24 11:41 ` Jan Beulich
2014-11-24 22:17 ` Steve Freitas
2014-11-25 8:16 ` Jan Beulich
2014-11-25 9:38 ` Steve Freitas
2014-11-25 11:00 ` Jan Beulich
2014-11-27 5:29 ` Steve Freitas [this message]
2014-11-27 9:27 ` Jan Beulich
2014-11-28 8:24 ` Steve Freitas
2014-11-28 8:50 ` Jan Beulich
2014-11-28 9:44 ` Steve Freitas
2014-12-03 17:14 ` Dugger, Donald D
2015-02-27 17:25 ` Dugger, Donald D
2015-02-27 17:50 ` Brown, Len
2015-03-02 15:24 ` Jan Beulich
2015-03-09 0:45 ` Steve Freitas
2015-03-26 20:49 ` Brown, Len
2014-11-21 9:31 ` Jan Beulich
2014-11-04 18:35 ` Steve Freitas
2014-11-04 14:39 ` Don Slutz
2014-11-06 23:20 ` Steve Freitas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5476B6A8.4060706@ihonk.com \
--to=sflist@ihonk.com \
--cc=JBeulich@suse.com \
--cc=dslutz@verizon.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.