On 2026 Sep 24 (Thu) at 17:26:39 +0200 (+0200), Stefan Sperling wrote: :On Wed, Sep 23, 2026 at 06:38:21PM +0200, Peter Hessler wrote: :> On 2026 Sep 23 (Wed) at 10:25:52 +0200 (+0200), Stefan Sperling wrote: :> :On Tue, Sep 22, 2026 at 04:17:55PM +0200, BESSOT Jean-Michel wrote: :> :> Hello :> :> :> :> I do not have network this time but it pass most of the time with those :> :> errors in dmesg. :> :> :> :> Sorry for the bug, i send the dmesg. :> :> :> :> Bye :> :> :> : :> :Can you please try this patch and let me know whether it helps? :> : :> :See https://lore.kernel.org/lkml/[email protected]/ :> : :> :> OK : :Looking at this again, I believe the diff below might be better. : :There are many more places where we read or write SRNG descriptors in :memory shared with the device. All these places are surrounded with :the access_begin() and access_end() helpers. Adding DMA syncs there :should ensure that host and device will always get a coherent view :of memory, not just in the particular case fixed in the Linux patch. : :Also handle the potential empty packet case a bit better. The Linux :patch is correct in that erroring out early here is bad. It leaves the :ring data structures in an incosistent state. The sw_index counter won't :be updated which means we will be looking at the wrong rx_data pointer :when receiving the next packet. : :Does this help with the issues on arm64? ok? :
tested on x13s, OK
