<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NVA8] nouveau screen corruption and X lockup when reclocking" href="https://bugs.freedesktop.org/show_bug.cgi?id=89273#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NVA8] nouveau screen corruption and X lockup when reclocking" href="https://bugs.freedesktop.org/show_bug.cgi?id=89273">bug 89273</a> from <a class="email" href="mailto:rspliet@eclipso.eu" title="Roy <rspliet@eclipso.eu>"> Roy</a> <pre>(In reply to Max Sydorenko from <a href="show_bug.cgi?id=89273#c0">comment #0</a>) > Created <a href="attachment.cgi?id=113734" name="attach_113734" title="Thinkpad T410, Quadro NVS 3100M (256M GDDR3) vbios dump">attachment 113734</a> <a href="attachment.cgi?id=113734&action=edit" title="Thinkpad T410, Quadro NVS 3100M (256M GDDR3) vbios dump">[details]</a> > Thinkpad T410, Quadro NVS 3100M (256M GDDR3) vbios dump > > Kernel: 3.19.1 > Hardware: Thinkpad T410, Quadro NVS 3100M (256M GDDR3) [similar hw but > different VRAM compared to <a class="bz_bug_link bz_status_NEW " title="NEW - [NVA8] nouveau GPU lockup when reclocking" href="show_bug.cgi?id=88415">bug 88415</a>] > Problem: reclocking between pstates 3 and 7 is flawless, but reclocking to > pstate f causes problems. [...] > I also mmiotraced functioning reclocking with the nvidia blob. Trace is > quite large (120MB). Should I truncate it somehow to upload, or just provide > as is? Thanks for reporting. I've had very little GDDR3 cards to test with (in fact... just one), so these logs will be extremely useful. If you can, please provide the trace in full. Feel free to compress it using xz or similar.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>