<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'> <hr id="zwchr"><blockquote id="DWT995" style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">De: "Ilia Mirkin" <imirkin@alum.mit.edu> À: "pierre morrow" <pierre.morrow@free.fr> Cc: nouveau@lists.freedesktop.org Envoyé: Vendredi 31 Janvier 2014 21:16:40 Objet: Re: [Nouveau] Help needed for bug 58556 Unfortunately this is a *massive* bug... and confused by the "other" very similar but apparently not identical bug in the system. What happens if you only enable acceleration on the NVAC card? (e.g. by hacking up nouveau to ignore the other one entirely). Wasn't there some thing where the NV96 card was effectively disabled but still appearing in PCI space? Or I might be thinking of a different mac situation... </blockquote>Well, if I disable acceleration for the NV96 card, it doesn't hang after initialising it, but I get spammed (I think it's PAGE_NOT_PRESENT errors, like [1], but my screen goes garbage at that point, so I can't read anything) later on, and I don't get to login. BTW, what could I do to get boot logs even if the system did not make it trough (apart from recording with my phone...)? <blockquote id="DWT996" style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"> As you probably saw, this is a MASSIVE commit. What exactly was the problem with 20abd1634a? </blockquote>The vblank structure was a little bit modified, and psw->vblank would be initialised only when acceleration is on (it was always initialised before), though it would be used inside functions called even when acceleration is off. You can see it in comments 18 [2] and 20 [3]. <blockquote id="DWT997" style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"> Can you go into some detail on what these tests were that yielded a successful outcome? IIRC nouveau_channel_new is called to create a new... channel, which is used by drm clients. If you don't have acceleration, that whole api is disabled, so it shouldn't come up. I guess accel_init also initializes drm->channel which is the kernel channel for doing stuff. [Although TBH I'm not entirely sure how things work without acceleration enabled... but I think there's a non-fifo way to show images on the screen.] </blockquote>My tests were pretty bruteforcing ones: * comment all nouveau_accel_init content, and uncomment block by block until it works; * then comment all nouveau_channel_new content, and uncomment function by function until it works; * and finally, I did the same inside nouveau_channel_init (for this function, only the vram creation, gart creation and dma variables initialisation were enough to get a clean screen). To sum up what pieces of nouveau_accel_init were needed to get a clean screen: * return if card is an NV96 one; * init fence; * run nouveau_channel_new: * nouveau_channel_ind * nouveau_channel_init, precisely these parts: * vram creation; * gart creation; * dma variables initialisation.<blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"> -ilia </blockquote> Pierre Moreau [1]: nouveau E[PFB][0000:03:00:0] trapped write at 0x0000546000 on channel 0x0000fee0 [unknown] BAR/PFIFO_WRITE/FB reason: PAGE_NOT_PRESENT [2]: https://bugs.freedesktop.org/show_bug.cgi?id=58556#c18 [3]: https://bugs.freedesktop.org/show_bug.cgi?id=58556#c20</div></body></html>