On Sat, 30 Mar 2019 16:15:14 +0100 (CET) Stefan Wahren <stefan.wahren@xxxxxxxx> wrote: > Hi Michal, > > > Michal Suchánek <msuchanek@xxxxxxx> hat am 28. März 2019 um 21:43 geschrieben: > > > > > > On Fri, 22 Mar 2019 18:10:11 +0100 (CET) > > Stefan Wahren <stefan.wahren@xxxxxxxx> wrote: > > > > > Hi Michal, > > > > > > > Michal Suchánek <msuchanek@xxxxxxx> hat am 22. März 2019 um 17:06 geschrieben: > > > > > > > > > > > > On Fri, 22 Mar 2019 15:45:13 +0100 > > > > Stefan Wahren <stefan.wahren@xxxxxxxx> wrote: > > > > > > > > > Hi Michal, > > > > > > > > > > Am 21.03.19 um 21:03 schrieb Michal Suchánek: > > > > > > > > > > could you please retry with mainline kernel 5.0? > > > > > > > > I can try that. What I have is pretty much 5.0 anyway so I don't expect > > > > much difference: > > > > > > > > > > as long as the issue lies in the sdhost driver code. There also has been a lot of fixes by Lukas Wunner to the DMA engine driver. I prefer a well defined source base. > > > > > > > > > > > I suspect that one of the locking fixes that went into mainline > > > > recently prevents recovering from the error but I did not try > > > > reverting them yet. > > > > > could you please try this patch: > > http://lists.infradead.org/pipermail/linux-rpi-kernel/2019-March/008627.html > > Stefan So I updated the dma driver to be able to apply this patch, applied it, and the system locked up. It even stopped logging over the network - only the serial console shows the message: Linux version 4.4.176-1.g755499f-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) .... ( 7/526) Installing: info2html-2.0-223.1.noarch .........................[done] ( 8/526) Installing: libX11-data-1.6.3-10.3.1.noarch ...............<89%>===[|][ 664.670582] sdhost-bcm2835 3f202000.sdhost: ti. [ 674.750501] sdhost-bcm2835 3f202000.sdhost: timeout waiting for hardware interrupt. So at least on 4.4 kernel this does not help. Thanks Michal
