<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - NV11 black screen & kernel hang on loading nouveaufb" href="https://bugs.freedesktop.org/show_bug.cgi?id=56461#c42">Comment # 42</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - NV11 black screen & kernel hang on loading nouveaufb" href="https://bugs.freedesktop.org/show_bug.cgi?id=56461">bug 56461</a> from <a class="email" href="mailto:chris@edesix.com" title="Chris Paulson-Ellis <chris@edesix.com>"> Chris Paulson-Ellis</a> <pre>I found the bug in commit cb75d97e that results in the incorrect GART aperture and fixed it with this patch: --- a/drivers/gpu/drm/nouveau/nouveau_compat.c +++ b/drivers/gpu/drm/nouveau/nouveau_compat.c @@ -17,7 +17,7 @@ nvdrm_gart_init(struct drm_device *dev, u64 *base, u64 *size) struct nouveau_drm *drm = nouveau_newpriv(dev); if (drm->agp.stat == ENABLED) { *base = drm->agp.base; - *size = drm->agp.base; + *size = drm->agp.size; return 0; } return -ENODEV; However, the display still fades to black. I now get an error that I didn't get with the parent commit: PFIFO_DMA_PUSHER - Ch 0 Get 0x04000000 Put 0x00001088 State 0xc0000000 (err: MEM_FAULT) Push 0x00000000 This message appears at the end of enabling the LDVS output, so it's probably related (I'll attach the console log). I'm not sure how to debug further. I'm wondering in particular how to trace the effect of various changes in commit cb75d97e, such as those made to run_digital_op_script()? Perhaps I need to trace all register read/writes during the devinit phase and compare to the parent commit? How would I do this?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>