This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue May 7 07:15:53 2024 Delivery-date: Fri, 09 Sep 2011 08:07:51 +0200 Received: from mail-ww0-f44.google.com ([74.125.82.44]:62291 "EHLO mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758383Ab1IIGHk convert rfc822-to-8bit (ORCPT ); Fri, 9 Sep 2011 02:07:40 -0 Received: by wwf5 with SMTP id 5so748298wwf.1 for ; Thu, 08 Sep 2011 23:07:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh Received: by 10.227.57.77 with SMTP id b13mr1634145wbh.96.1315548457707; Thu, 08 Sep 2011 23:07:37 -0700 (PDT) Received: from localhost ([61.148.56.138]) by mx.google.com with ESMTPS id et17sm6410158wbb.0.2011.09.08.23.07.34 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Sep 2011 23:07:36 -0700 (PDT) Date: Fri, 9 Sep 2011 14:07:25 +0800 From: Yong Zhang To: "Nallasellan, Singaravelan" Cc: Arjan van de Ven , "alsa-devel@alsa-project.org" , "linux-kernel@vger.kernel.org" Subject: Re: Player Thread is not woken after period elapsed Message-Id: <20110909060725.GA21124@zhy> Reply-To: Yong Zhang References: <3CA6C6D9F70D314CA34352990B57DA1507C420F147@bgsmsx502.gar.corp.intel.com> <20110905105253.2787b91f@infradead.org> <3CA6C6D9F70D314CA34352990B57DA1507C420F15C@bgsmsx502.gar.corp.intel.com> <20110905112225.72b46ac9@infradead.org> <3CA6C6D9F70D314CA34352990 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: QUOTED-PRINTABLE In-Reply-To: <3CA6C6D9F70D314CA34352990B57DA1507C42C3CA5@bgsmsx502.gar.corp.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 08, 2011 at 03:15:38PM +0530, Nallasellan, Singaravelan wro= te: > > > > Further investigation of this issue shows that the thread is in= running state Hmm, how do you detect it? > > and it is not scheduled. I am not sure how I will go about debuggin= g this issue. > > Any pointer would help. Could 'cat /proc/sched_debug' give some useful info? And BTW, have you tried CONFIG_DETECT_SOFTLOCKUP =3D y? Thanks, Yong > > > > > > Could you confirm if [commit f26f9af Sched: fix skip_clock_update > > > optimization] residents in your kernel? > I applied this patch manually. I still see the issue. > >=20 > > And commit da7a735e51f9622eb3e1672594d4a41da01d7e4f > > http://marc.info/?l=3Dlinux-kernel&m=3D129527509622696&w=3D2 > This is already applied. > =13=EF=BF=BD=EF=BF=BD=EC=B9=BB=1C=EF=BF=BD&=EF=BF=BD~=EF=BF=BD&=EF=BF= =BD=18=EF=BF=BD=EF=BF=BD+-=EF=BF=BD=EF=BF=BD=DD=B6=17=EF=BF=BD=EF=BF=BD= w=EF=BF=BD=EF=BF=BD=CB=9B=EF=BF=BD=EF=BF=BD=EF=BF=BDm=EF=BF=BDb=EF=BF=BD= =EF=BF=BDdz=EF=BF=BD=DE=96)=EF=BF=BD=EF=BF=BD=EF=BF=BDw*=1Fjg=EF=BF=BD=EF= =BF=BD=EF=BF=BD=1E=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=DD=A2j/= =EF=BF=BD=EF=BF=BD=EF=BF=BDz=EF=BF=BD=DE=96=EF=BF=BD=EF=BF=BD2=EF=BF=BD= =DE=99=EF=BF=BD=EF=BF=BD=EF=BF=BD&=EF=BF=BD)=DF=A1=EF=BF=BDa=EF=BF=BD=EF= =BF=BD=7F=EF=BF=BD=EF=BF=BD=1E=EF=BF=BDG=EF=BF=BD=EF=BF=BD=EF=BF=BDh=EF= =BF=BD=0F=EF=BF=BDj:+v=EF=BF=BD=EF=BF=BD=EF=BF=BDw=EF=BF=BD=D9=A5>W=EF=BF= =BD=EF=BF=BD=EF=BF=BD=EF=BF=BDi=EF=BF=BDaxP=10j=EF=BF=BDm=EF=BF=BD=EF=BF= =BD=EF=BF=BD=EF=BF=BD=0C-=EF=BF=BD=1A+=EF=BF=BD=EF=BF=BDd=EF=BF=BD_ --=20 Only stand for myself -- To unsubscribe from this list: send the line "unsubscribe linux-kernel"= in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/