On Thu, May 20, 2021 at 09:53:02AM +0200, Peter N. M. Hansteen wrote: > On Thu, May 20, 2021 at 08:53:14AM +1000, Jonathan Gray wrote: > > On Wed, May 19, 2021 at 06:32:01PM +0200, Peter N. M. Hansteen wrote: > > > On Wed, May 19, 2021 at 04:43:44PM +0200, Peter N. M. Hansteen wrote: > > > > > outdated...) > > > > > > > > I tried the first, that only seemed to have the effect of having > > > > the freeze come faster. So I commented out that part of the xorg.conf > > > > and I'm trying the steps in the README now, but for some reasons I > > > > don't get any dumps in /var/crash as expected. Then again I could well > > > > be missing some crucial step. > > > > > > Still no luck getting coredumps but when I sshed in after the last freeze > > > the last two lines of dmesg were > > > > > > [drm] *ERROR* ring sdma0 timeout, signaled seq=110053, emitted seq=110053 > > > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > > > > > the [drm] part has me suspect this is related (but I don't know what sdma > > > signifies in this context) > > > > sdma is the asynchronous System DMA engine > > > > Ring timeouts like this are a known problem with amdgpu which persist > > across multiple major drm versions. > > Looking at what appears in the log (/var/log/messages) the time when X > freezes corresponds very well with when those messages are recorded. > > The question is, how do I usefully debug this? I've gone over the README's > procedure a few times now and it unfortunately does not produce any coredumps > or traces.
The point at which ring timeouts are encountered I believe acceleration is disabled. Likely it hits some not well tested error path after that. > > One option is of course to trade up or sideways to something like > https://www.power.no/data-og-tilbehoer/pc-og-mac/baerbar-pc/asus-zenbook-s-ux393ea-pure2-13-laptop/p-1115705/ > (Intel Core i7-1165G7 with Iris Xe graphics), but would that have a better > chance of success (or for that matter be helpful to the project)? While there is some support for tiger lake in the linux 5.7 based drm in -current I know of at least one machine that needs the newer 5.10 based drm tree I am working on. Trying to deal with some regressions on older Intel hardware with that at the moment. > > All the best, > Peter > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. > >
