2014-02-11 11:41 GMT+01:00 Ilia Mirkin <imirkin@xxxxxxxxxxxx>:
> On Mon, Feb 10, 2014 at 3:05 PM, Rafał Miłecki <zajec5@xxxxxxxxx> wrote:
>> 2014-02-10 20:06 GMT+01:00 Ilia Mirkin <imirkin@xxxxxxxxxxxx>:
>>> There was also an issue with libdrm_nouveau for pre-nv50 chips, when
>>> compiled with gcc-4.8 some time back... fixed in... 2.4.48 or so?
>>
>> I use openSUSE 12.2 (x86_64) which provides gcc 4.7.1 and
>> libdrm_nouveau1-2.4.33-2.3.2.x86_64. I assume libdrm_nouveau was
>> compiled using that 4.7.1.
>
> Hmmm... the nouveau drm rewrite went into 2.4.34... I guess you're
> using pretty old userspace in general, since everything depends on the
> post-rewrite libdrm_nouveau. Of course it definitely sounds like a
> kernel issue, but I can't help but wonder if this is a non-issue with
> later userspace.
>
> So there are basically 2 things left to do, in order of time-consuming-ness:
>
> (a) try a live{cd,usb} (e.g. arch, or something else that has recent
> software), and see if the issue is still present there.
I've tried Fedora 20 booted from USB. It suffers from the same issue.
It's based on kernel 3.11.10, but I'm sure it has more up to date
userspace.
> (b) bisect. you can (almost) definitely restrict the bisect to
> drivers/gpu/drm/nouveau. if you have additional computational power, i
> would recommend looking into distcc for speeding up the compiles. it
> may be interesting to also try 3.6.x since 3.7 received a pretty big
> rewrite. but a git bisect is a lot more direct in figuring these
> things out :)
Bisecting nouveau between 3.10 and 3.11 is a real pain.
Ben introduced booting regression with commit:
commit dceef5d87cc01358cc1434416f3272e2ddc3d97a
Author: Ben Skeggs <bskeggs@xxxxxxxxxx>
Date: Mon Mar 4 13:01:21 2013 +1000
drm/nouveau/fb: initialise vram controller as pfb sub-object
I had to first bisect fix for that regression which appeared to be:
commit 6284bf41b97fb36ed96b664a3c23b6dc3661f5f9
Author: Ilia Mirkin <imirkin@xxxxxxxxxxxx>
Date: Fri Aug 9 17:25:54 2013 -0400
drm/nouveau/fb: fix null derefs in nv49 and nv4e init
Unfortunately meanwhile another init regression was introduced with:
commit 0108bc808107b97e101b15af9705729626be6447
Author: Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxx>
Date: Sun Jul 7 10:40:19 2013 +0200
drm/nouveau: do not allow negative sizes for now
And I had to find fix for that which was:
commit 35095f7529bb6abdfc956e7a41ca6957520b70a7
Author: Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxx>
Date: Sat Jul 27 10:17:12 2013 +0200
drm/nouveau: fix size check for cards without vm
Then I finally was able to test every commit between 3.10 and 3.11
without skipping 90% of them.
--
Rafał
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
