lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 24 Mar 2014 14:39:42 +0100 (CET) From: Jiri Kosina <jkosina@...e.cz> To: Daniel Vetter <daniel.vetter@...ll.ch> cc: Jani Nikula <jani.nikula@...ux.intel.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, intel-gfx <intel-gfx@...ts.freedesktop.org> Subject: Re: i915 resume-from-hibernation problems on resume with current Linus' tree On Fri, 21 Mar 2014, Daniel Vetter wrote: > > So I am still seeing this with current Linus' tree rather regularly (but > > it's not deterministic enough for a reliable bisect). > > > > Unfortunately I haven't received any patches to test; what do you propose? > > Would reporting this on bugs.freedesktop.org instead of ranting here > > change anything? > > Yeah, filing a bug on fdo to keep track of this should help. Please > add a [gm45 regression] tag to the summary so that it shows up in our > queries at the right spot ;-) > > One thing to test would be to give -nightly (or drm-intel-testing as > of today) a shot. We've merged a few patches recently to slightly > improve the ring init sequence in the generic code, they might > actually help here. Sorry for not correlating them with your patch > when I've merged them, only just realized this now. I just tested current Linus' tree + drm-intel-testing (HEAD == 14347c2 ("drm-intel-nightly: 2014y-03m-21d-16h-13m-30s integration manifest")), and on 3rd suspend-resume cycle I got the ring initialization failure again, with Xorg going crazy afterwards. So unfortunately it's still unfixed. Now submitted as https://bugs.freedesktop.org/show_bug.cgi?id=76554 as well. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists