[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7166d32d-1172-4f43-8539-199791a1f82b@amd.com>
Date: Thu, 24 Apr 2025 17:57:38 +0530
From: "Rangoju, Raju" <raju.rangoju@....com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
miquel.raynal@...tlin.com, Krishnamoorthi M <krishnamoorthi.m@....com>,
Akshata MukundShetty <akshata.mukundshetty@....com>
Subject: Re: [PATCH] spi: spi-mem: Add fix to avoid divide error
On 4/24/2025 5:45 PM, Mark Brown wrote:
> On Thu, Apr 24, 2025 at 05:43:33PM +0530, Raju Rangoju wrote:
>
>>
>> Following divide error is fixed by this change:
>>
>> Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI
>> CPU: 15 UID: 0 PID: 1872 Comm: modprobe Not tainted 6.14.0-rc7-zero-day-+ #7
>> Hardware name: AMD FOX/Lilac-RMB, BIOS RFE1007A_SPI2_11112024. 10/17/2024
>> RIP: 0010:spi_mem_calc_op_duration+0x56/0xb0
>> Code: 47 08 0f b6 7f 09 c1 e0 03 99 f7 ff 0f b6 51 0a 83 e2 01 8d 7a 01 99 f7 ff 0f b6 79 19 48 98 48 01 c6 0f b6 41 18 c1 e0 03 99 <f7> ff 0f b6 51 1a 83 e2 01 8d 7a 01 99 f7 ff 0f b6 79 20 31 d2 48
>> RSP: 0018:ffffb6638416b3d0 EFLAGS: 00010256
>
> 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.
Sure Mark. I'll respin V2 keeping just the relevant part of call trace
and discarding rest of it.
Powered by blists - more mailing lists