On Mon, Mar 24, 2014 at 7:27 AM, Andreas Mohr <andi@xxxxxxxx> wrote: > On Sun, Mar 23, 2014 at 09:39:16AM -0700, Linus Torvalds wrote: >> On Sun, Mar 23, 2014 at 5:15 AM, Andreas Mohr <andi@xxxxxxxx> wrote: >> > >> > which did end up flawless on 3.12.0-rc2+, too >> > (but failed to improve the issue on 3.14.0-rc7+). >> > >> > So, for all intents and purposes, drm infrastructure seems unavoidably >> > (neither dri disable nor libdrm upgrade helps) affected. >> > Does anyone know which change caused that issue? >> > (I'm asking because bisect here would be relatively painful). >> >> So 3.12-rc2 works. Does 3.13 work? Is this a regression in the current >> 3.14 rc only, or did it happen already in the previous release? > > Hmm, given that Mikulas in > https://lkml.org/lkml/2014/2/26/537 > offered a diff of linux-3.13.5 files, it truly seems (shock! ack! noo!) > that that indeed may have been a regression at <= 3.13 proper even > (which may pose interesting questions about the level of testing coverage > we still enjoy [not!?] in this hardware area). > > Oh well, seems I'll have to prepare/build 3.13 now... It's > 15 year old hardware, so yes I believe we have close to 0 testing coverage on it outside of distros, I'm not even sure I have one anymore, I might be able to test an MGA in one box. Dave. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
