linux-kernel - Re: Player Thread is not woken after period elapsed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4E70716B.3010201@gmail.com>
Date:	Wed, 14 Sep 2011 17:18:35 +0800
From:	Shan Hai <haishan.bai@...il.com>
To:	"Nallasellan, Singaravelan" <singaravelan.nallasellan@...el.com>
CC:	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Player Thread is not woken after period elapsed

On 09/06/2011 01:38 AM, Nallasellan, Singaravelan wrote:
> Hi,
>
> When I tried to root cause a glitch in the audio playback, I found a weird behavior.
>
> User thread which invokes the writei function which in turn  invokes a kernel function which waits for the free buffer to write the audio data.  This kernel function adds this thread to a wake(sleep) queue  and calls a schedule_timeout (msecs_to_jiffies(10000)).
>
> When the audio playback of a period is completed, the hardware generates an interrupt. The handler in the path wake_up the thread added to the sleep queue.  Most of the time, the playback thread is woken up.
>
> During this error case, the thread is not getting woken up. However the sleep queue is not empty.  This continues until the playback enter into underrun due to all the periods in the buffer are played back. Audio playback continues after recovery from xrun.
>

Its possible that your user thread was woken up by the IRQ handler but
it found out the 'free buffer' is not available and go back to sleep.

- check the /proc/<pid of user thread>/schedstat for whether the thread 
was scheduled
- your shared buffer design might has problems in it, it seemed there is 
a race between
     your IRQ handler and 'free buffer' checking logic.
- ftrace might be helpful

Cheers
Shan Hai

> Will you provide some hint on how to go about identifying the root cause?
>
> Thanks
> -Sing
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/