<div dir="ltr"><div><div>Hi Russel, </div>The requested file follows in attachment. </div>Luis </div><div class="gmail_extra"> <div class="gmail_quote">On Thu, Nov 2, 2017 at 3:20 PM, Russell King - ARM Linux <<a href="mailto:linux@armlinux.org.uk" target="_blank">linux@armlinux.org.uk</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, Nov 02, 2017 at 03:05:38PM +0000, Luís Mendes wrote: > Hi, > > Wladimir, Fabio: Thanks for pointing out this patch. I have applied the > patch and compiled mesa, but it produced no relevant change regarding the > MMU fault that I am getting. For me it makes sense that it isn't related to > this issue because I am running no 3D applications, just logging in into > the Ubuntu MATE Desktop. Since I am using xf86-video-armada It is expected > that GC320 is the only unit busy, working, during this stage of the desktop > initialization. > > Russel, Lucas: The etna-gpu-tools compiled cleanly... I got this log and > some .bin files with the dumps. I have no clue about the GC320 registers as > I have no knowledge about the unit, however I if could get the stack of the > calling process, would be great... > [ 56.173613] etnaviv-gpu 134000.gpu: MMU fault status > 0x00000002 > [ 56.179955] etnaviv-gpu 134000.gpu: MMU 0 fault addr > 0x0803ffc0 > [ 56.185905] etnaviv-gpu 134000.gpu: MMU 1 fault addr > 0x00000000 > [ 56.191843] etnaviv-gpu 134000.gpu: MMU 2 fault addr > 0x00000000 > [ 56.197778] etnaviv-gpu 134000.gpu: MMU 3 fault addr > 0x00000000 > [ 59.258367] etnaviv-gpu 134000.gpu: hangcheck detected gpu > lockup! > [ 59.265910] etnaviv-gpu 134000.gpu: completed fence: > 378 > [ 59.271737] etnaviv-gpu 134000.gpu: active fence: > 383 > [ 59.277930] etnaviv-gpu 134000.gpu: hangcheck > recover! > [ 59.393270] etnaviv-gpu 134000.gpu: MMU fault status > 0x00000002 > [ 59.399256] etnaviv-gpu 134000.gpu: MMU 0 fault addr > 0x00343fc0 > [ 59.405207] etnaviv-gpu 134000.gpu: MMU 1 fault addr > 0x00000000 > [ 59.411143] etnaviv-gpu 134000.gpu: MMU 2 fault addr > 0x00000000 > [ 59.417082] etnaviv-gpu 134000.gpu: MMU 3 fault addr > 0x00000000 > [ 61.272368] etnaviv-gpu 134000.gpu: hangcheck detected gpu > lockup! > [ 61.278633] etnaviv-gpu 134000.gpu: completed fence: > 384 > [ 61.284515] etnaviv-gpu 134000.gpu: active fence: > 387 > [ 61.290110] etnaviv-gpu 134000.gpu: hangcheck > recover! > [ 62.278720] etnaviv-gpu 134000.gpu: MMU fault status > 0x00000002 > [ 62.284699] etnaviv-gpu 134000.gpu: MMU 0 fault addr > 0x0803ffc0 > [ 62.290681] etnaviv-gpu 134000.gpu: MMU 1 fault addr > 0x00000000 > [ 62.296644] etnaviv-gpu 134000.gpu: MMU 2 fault addr > 0x00000000 > [ 62.302603] etnaviv-gpu 134000.gpu: MMU 3 fault addr > 0x00000000 > [ 64.306760] etnaviv-gpu 134000.gpu: hangcheck detected gpu > lockup! > [ 64.313031] etnaviv-gpu 134000.gpu: completed fence: > 387 > [ 64.318907] etnaviv-gpu 134000.gpu: active fence: > 403 > [ 64.325477] etnaviv-gpu 134000.gpu: hangcheck recover! > > === Register dump > 0000000c = 000000df > 00000000 = 00040900 > 00000004 = 7ffffff8 Idle: FE- DE- PE- SH+ PA+ SE+ RA+ TX+ VG+ IM+ FP+ TS+ > 00000008 = 00002200 > 00000014 = ffffffff > 00000018 = 14010000 > 0000001c = e02c7eca > 00000020 = 00000320 > 00000024 = 00005303 > 00000028 = 20140510 > 0000002c = 20353900 > 00000034 = e9399eff > 00000038 = e9399eff > 00000070 = 00000000 > 00000100 = 00140021 > 00000104 = 00000000 > 00000108 = 000000fa > 0000010c = 00000000 > 00000400 = 00000000 > 00000404 = 00000000 > 00000408 = 00000000 > 0000040c = 00000000 > 00000410 = 00000000 > 00000414 = 3c000000 > 00000418 = 00000000 > 0000041c = 00000000 > 00000420 = 00000000 > 00000424 = 00000000 > 00000428 = 00000000 > 0000042c = 00030000 > 00000480 = 000000a8 > 0000065c = 00000001 > 00000660 = 00000803 Cmd: [load0 DMA: idle Fetch: valid] Req idle Cal idle > 00000664 = 00001230 Command DMA address > 00000668 = 00000040 FE fetched word 0 > 0000066c = 00000000 FE fetched word 1 > 00000670 = 00000000 </div></div>Okay, so we stopped at 0x1230. > === > Buffers > > Num Name IOVA Size > 0 reg 00000000 00000128 296 > 1 mmu 00000000 00401000 4198400 > 2 ring 00000000 00001000 4096 > * 3 cmd 00001000 00000320 800 > 4 cmd 00002000 00000190 400 > 5 cmd 00003000 00000320 800 > 6 cmd 00004000 00000190 400 > 7 cmd 00005000 00000188 392 > 8 bomap 00000000 000018f0 6384 > 9 bo 00040000 00300000 3145728 > 10 bo 00340000 00001000 4096 > 11 bo 00341000 00002000 8192 > 12 bo 02e60000 00001000 4096 > 13 bo 030c3000 00001000 4096 > 14 bo 030c4000 00001000 4096 > 15 bo 030c5000 00018000 98304 > Checking MMU entries... ok So, buffer 3 is the command buffer we were processing, it's only 800 bytes long. You should find that along side the log file, called "cmd-00001000.bin". Please send me this file. Thanks. <div class="HOEnZb"><div class="h5"> -- RMK's Patch system: <a href="http://www.armlinux.org.uk/developer/patches/" rel="noreferrer" target="_blank">http://www.armlinux.org.uk/developer/patches/</a> FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up According to <a href="http://speedtest.net" rel="noreferrer" target="_blank">speedtest.net</a>: 8.21Mbps down 510kbps up </div></div></blockquote></div> </div>