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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 10 Mar 2014 15:38:50 +0100
From:	Daniel Vetter <>
To:	Jiri Kosina <>
Cc:	Jani Nikula <>,
	Linux Kernel Mailing List <>,
	intel-gfx <>
Subject: Re: i915 resume-from-hibernation problems on resume with current
 Linus' tree

On Mon, Mar 10, 2014 at 3:25 PM, Jiri Kosina <> wrote:
> On Mon, 3 Mar 2014, Jiri Kosina wrote:
>> > first things first: this is hard to bisect, because it doesn't happen
>> > reliably and I don't really know what is the first good version, as I had
>> > a delay in following Linus' tree.
>> >
>> > What happens is that after resumption from S4 (disk), Xorg session is in
>> > complete havoc -- the windows don't redraw properly, sometimes the mouse
>> > pointer is "jailed" on a small rectangle in the middle of the screen, etc.
>> >
>> > I have captured 'drm.debug=14' output of the failing resume ... I guess
>> > this is realted to the
>> >
>> > *ERROR* render ring initialization failed ctl 0001f001 head 00003004 tail 00000000 start 00003000
>> >
>> > as it doesn't seem to be there in case of resumption that works properly.
>> >
>> > Please see the dmesg from the broken case below.
>> I encountered this again with -rc5.
>> If there is anything I can do to help debug this, please let me know.
> I hate to be doing this, but ... ping? :)

gm45 and rendering ring init failures. We've seen this occasionally
crop up due to rather unrelated changes. Some even hit stable
backports and had to be backed out again. We essentially have no clue
what's amiss, but it seems to /mostly/ work. Thus far I've only hear
reports of this for gm45 and not yet really for upstream. Until
someone digs up more evidence I think we need to classify this as a
rare heisenbug and not really a regression :(

One thing we could try is to simply repeat the ring init setup, maybe
after a gpu reset or something like that.
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists