[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190207143214.GC6190@sirena.org.uk>
Date: Thu, 7 Feb 2019 14:32:14 +0000
From: Mark Brown <broonie@...nel.org>
To: Sylwester Nawrocki <s.nawrocki@...sung.com>
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 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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists