From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Teck Choon Giam <giamteckchoon@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: tg3 network stall in xen-3.4.x but not in xen-3.3.x
Date: Mon, 06 Jul 2009 08:19:01 +0100 [thread overview]
Message-ID: <C67763F5.EF1F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <9b5c9bb30907052055i58bd373bjdeeb533a7bc3d64@mail.gmail.com>
On 06/07/2009 04:55, "Teck Choon Giam" <giamteckchoon@gmail.com> wrote:
>> Hmm, that's rather disturbing. Its presumably the cpuidle parameter which is
>> having the effect. Quite why deeper sleep states can result in one particular
>> device interrupt getting stuck (as opposed to all of them) is a mystery. It
>> might be interesting to see the boot messages, and also to find out which of
>> the C states is causing the problem (presumably C2 or C3).
>
> If I do not add cpuidle and cpufreq in xen boot para. I got the below:
>
> # xenpm get-cpuidle-states
> Max C-state: C1
>
> cpu id : 0
> total C-states : 2
That's interesting, since it appears the troublesome system does not even
support deep sleep states (e.g., C3). Just C0 and C1: which would normally
mean C0=running, C1=normal-HLT. I've cc'ed a couple of Intel guys to confirm
we couldn't be misreading the xenpm output.
If we're reading this correctly I think it really means that the special
acpi-cx idle handler has a bug in it somewhere. Actually one bug has been
found already, and I will forward the patch to you. It could be worth
applying it and rebuilding Xen and see if we're lucky enough for that to
solve your problem.
-- Keir
next prev parent reply other threads:[~2009-07-06 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-04 6:32 tg3 network stall in xen-3.4.x but not in xen-3.3.x Teck Choon Giam
2009-07-04 6:41 ` Keir Fraser
2009-07-04 6:59 ` Teck Choon Giam
2009-07-04 7:09 ` Keir Fraser
2009-07-04 7:30 ` Teck Choon Giam
2009-07-05 2:56 ` Teck Choon Giam
2009-07-05 21:36 ` Ian Pratt
2009-07-06 3:55 ` Teck Choon Giam
2009-07-06 7:19 ` Keir Fraser [this message]
2009-07-07 1:29 ` Teck Choon Giam
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=C67763F5.EF1F%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=giamteckchoon@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.