search for: 6ff8c76

...s <bskeggs at redhat.com> >> Date: Wed Aug 21 11:30:36 2013 +1000 >> >> drm/nv04/disp: fix framebuffer pin refcounting >> >> I've booted that commit and one commit older few times. Every time I >> booted 78ae0ad I got corruption. Every time I booted 6ff8c76 (it's the >> earlier commit), it was OK. > > But I bet if you restart X, you get a backtrace, right? That's right. 78ae0ad: Corruptions 6ff8c76: WARNING: at drivers/gpu/drm/nouveau/nouveau_bo.c:151 nouveau_bo_del_ttm+0x80/0x90 [nouveau]() (after quiting X by "init 3&quot...

...d403daf11cf63da86923d2b5dbeda3af8f Author: Ben Skeggs <bskeggs at redhat.com> Date: Wed Aug 21 11:30:36 2013 +1000 drm/nv04/disp: fix framebuffer pin refcounting I've booted that commit and one commit older few times. Every time I booted 78ae0ad I got corruption. Every time I booted 6ff8c76 (it's the earlier commit), it was OK. Ben: any idea why this commit caused regression for my hardware? From the commit message I assume it was supposed to affect some ancient nv04 hardware only. Did it accidentally touch my nv4e path code maybe? -- Rafa?

...f > Author: Ben Skeggs <bskeggs at redhat.com> > Date: Wed Aug 21 11:30:36 2013 +1000 > > drm/nv04/disp: fix framebuffer pin refcounting > > I've booted that commit and one commit older few times. Every time I > booted 78ae0ad I got corruption. Every time I booted 6ff8c76 (it's the > earlier commit), it was OK. But I bet if you restart X, you get a backtrace, right? > > Ben: any idea why this commit caused regression for my hardware? From > the commit message I assume it was supposed to affect some ancient > nv04 hardware only. Did it accidental...

2014-02-10 20:06 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: > On Mon, Feb 10, 2014 at 10:12 AM, Rafa? Mi?ecki <zajec5 at gmail.com> wrote: >> 2014-02-09 23:12 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: >>> On Sun, Feb 9, 2014 at 5:08 PM, Rafa? Mi?ecki <zajec5 at gmail.com> wrote: >>>> Last week I've switched from my old &