[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <21b8ccd7-e379-b4aa-3257-c9644ce3664c@samsung.com>
Date: Thu, 07 Feb 2019 15:47:14 +0100
From: Sylwester Nawrocki <s.nawrocki@...sung.com>
To: Mark Brown <broonie@...nel.org>
Cc: lgirdwood@...il.com, krzk@...nel.org, sbkim73@...sung.com,
m.szyprowski@...sung.com, b.zolnierkie@...sung.com,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org
Subject: Re: [PATCH] ASoC: samsung: Prevent clk_get_rate() calls in atomic
context
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.
Powered by blists - more mailing lists