From: Ben Dooks <ben.dooks@codethink.co.uk>
To: alsa-devel@alsa-project.org
Subject: pulseaudio and rcar-h2 sound
Date: Tue, 01 Apr 2014 15:28:45 +0100 [thread overview]
Message-ID: <533ACD1D.9080209@codethink.co.uk> (raw)
I am currently investigating an issue with the rcar-h2 audio driver
and a hang when running pulse-audio. From what I can see the issue
seems to be an interaction with the driver and the regmap code.
The current issue is that whatever is happening causes CPU0 to
stall, thus nothing seems to be able to continue. The following
errors are detected by the rcu code:
INFO: rcu_sched self-detected stall on CPU
0: (1 GPs behind) idle=415/2/0 softirq=3076/3077
(t=10500 jiffies g=520 c=519 q=51)
I have been through the regmap code and the locking looks ok. I also
enabled as much of the locking checks as I could and it does not
produce any useful output as to why it would be deadlocking.
I can run the system fine if I replace the rsnd_read, rsnd_write
and rsnd_bset code with versions which do not directly use regmap.
Does anyone have any experience with this, or any further ideas on
how to continue debugging?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
reply other threads:[~2014-04-01 14:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=533ACD1D.9080209@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alsa-devel@alsa-project.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.