From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser 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 Message-ID: References: <9b5c9bb30907052055i58bd373bjdeeb533a7bc3d64@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <9b5c9bb30907052055i58bd373bjdeeb533a7bc3d64@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Teck Choon Giam , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/07/2009 04:55, "Teck Choon Giam" 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