[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191227225204.GQ27497@sirena.org.uk>
Date: Fri, 27 Dec 2019 22:52:04 +0000
From: Mark Brown <broonie@...nel.org>
To: Peter Seiderer <ps.report@....net>
Cc: linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
Annaliese McDermond <nh6z@...z.net>,
Takashi Iwai <tiwai@...e.com>,
Jaroslav Kysela <perex@...ex.cz>,
Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH v1] ASoC: tlv320aic32x4: handle regmap_read error
gracefully
On Fri, Dec 27, 2019 at 04:20:56PM +0100, Peter Seiderer wrote:
> Fixes:
>
> [ 5.169310] Division by zero in kernel.
> [ 5.200998] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.3.18-20191021-1+ #14
> [ 5.203049] cdc_acm 2-1.6:1.0: ttyACM0: USB ACM device
> [ 5.208198] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> [ 5.220084] Backtrace:
> [ 5.222628] [<8010f60c>] (dump_backtrace) from [<8010f9a8>] (show_stack+0x20/0x24)
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