From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, krzk@kernel.org, sbkim73@samsung.com,
m.szyprowski@samsung.com, b.zolnierkie@samsung.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] ASoC: samsung: Prevent clk_get_rate() calls in atomic context
Date: Thu, 07 Feb 2019 15:47:14 +0100 [thread overview]
Message-ID: <21b8ccd7-e379-b4aa-3257-c9644ce3664c@samsung.com> (raw)
In-Reply-To: <20190207143214.GC6190@sirena.org.uk>
On 2/7/19 15:32, Mark Brown wrote:
> On Thu, Feb 07, 2019 at 03:20:41PM +0100, Sylwester Nawrocki wrote:
>
>> [ 82.109780] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:908
>> [ 82.117009] in_atomic(): 1, irqs_disabled(): 128, pid: 1554, name: speaker-test
>> [ 82.124235] 3 locks held by speaker-test/1554:
>> [ 82.128653] #0: cc8c5328 (snd_pcm_link_rwlock){...-}, at: snd_pcm_stream_lock_irq+0x20/0x38
> Please think hard before including complete backtraces in upstream
> reports, they are very large and contain almost no useful information
> relative to their size so often obscure the relevant content in your
> message. If part of the backtrace is usefully illustrative then it's
> usually better to pull out the relevant sections.
OK, let me trim the backtrace some more and resend.
next prev parent reply other threads:[~2019-02-07 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190207142052epcas1p22f1dc03c371674434ff40150cf376b6a@epcas1p2.samsung.com>
2019-02-07 14:20 ` [PATCH] ASoC: samsung: Prevent clk_get_rate() calls in atomic context Sylwester Nawrocki
2019-02-07 14:32 ` Mark Brown
2019-02-07 14:47 ` Sylwester Nawrocki [this message]
2019-02-07 14:54 ` Mark Brown
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=21b8ccd7-e379-b4aa-3257-c9644ce3664c@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sbkim73@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox