[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc53dca0-74d1-42d2-936a-adc383bd571a@sirena.org.uk>
Date: Tue, 27 May 2025 12:28:54 +0100
From: Mark Brown <broonie@...nel.org>
To: Gabor Juhos <j4g8y7@...il.com>
Cc: Md Sadre Alam <quic_mdalam@...cinc.com>,
Varadarajan Narayanan <quic_varada@...cinc.com>,
Sricharan Ramabadhran <quic_srichara@...cinc.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>, linux-spi@...r.kernel.org,
linux-mtd@...ts.infradead.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] spi: spi-qpic-snand: reallocate BAM transactions
On Sun, May 25, 2025 at 07:05:35PM +0200, Gabor Juhos wrote:
> # reboot
> [ 877.178844] Unable to handle kernel read from unreadable memory at virtual address 0000000000000078
> [ 877.178913] Mem abort info:
> [ 877.186767] ESR = 0x0000000096000005
> [ 877.189508] EC = 0x25: DABT (current EL), IL = 32 bits
> [ 877.193312] SET = 0, FnV = 0
> [ 877.198780] EA = 0, S1PTW = 0
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 (it often is
for search engines if nothing else) 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