Bug 714971

Changing component to kernel, because it has nothing to do with hibernate-commons-annotations.

(In reply to comment #1)
> Changing component to kernel, because it has nothing to do with
> hibernate-commons-annotations.

Maybe. I am here first time, sorry. What about my error?

(In reply to comment #3)
> Created attachment 505828 [details]
> /var/log/dmseg
> 
> Hello. I have next problem. When my notebook go to hibernate, i see black
> display and  rows on it: 
> [drm:init_ring_common] *ERROR* render ring head not reset to zero ctl 00000000
> head 02001000 tail 00000000 start 02001000
> 
> If I more  go to in hibernate my netbook, then i see more rows with error. So,
> I go to in hibernate, i see this error on black screen and my notebook
> sleeping. When I run notebook after sleep then i see black screen with this
> error. I wait about 40 sec and notebook working. All works ok, but this
> error... what wiht it to make?  Help me. please.

if it's not causing a problem don't worry about it.

(In reply to comment #3)
> (In reply to comment #3)
> > Created attachment 505828 [details]
> > /var/log/dmseg
> > 
> > Hello. I have next problem. When my notebook go to hibernate, i see black
> > display and  rows on it: 
> > [drm:init_ring_common] *ERROR* render ring head not reset to zero ctl 00000000
> > head 02001000 tail 00000000 start 02001000
> > 
> > If I more  go to in hibernate my netbook, then i see more rows with error. So,
> > I go to in hibernate, i see this error on black screen and my notebook
> > sleeping. When I run notebook after sleep then i see black screen with this
> > error. I wait about 40 sec and notebook working. All works ok, but this
> > error... what wiht it to make?  Help me. please.
> 
> if it's not causing a problem don't worry about it.

Sometimes  I cant to enter in system after hibernate, then I  to hold button off for reboot it. Maybe it is because of this error. What do you think about?

Created attachment 511210 [details]
/var/log/dmesg

Created attachment 511214 [details]
/etc/X11/xorg.conf.d/00-system-setup-keyboard.conf

Created attachment 511215 [details]
/var/log/messages

Created attachment 511216 [details]
/var/log/Xorg.0.log

I added to kernel parameter drm.debug=0x04 and I replayed error. This is files with report (/var/log/dmesg, /etc/X11/xorg.conf.d/00-system-setup-keyboard.conf, /var/log/messages, /var/log/Xorg.0.log). What do you think about?

(In reply to comment #3)
> if it's not causing a problem don't worry about it.

Also note that this error message and its companion error message were made into something more sane (ie, a debug message and a conditional error message) in commit  6fd0d56e3bc1abfb237b8824261b613e21e77bc8 ("drm/i915/ringbuffer: Only print an error on the second attempt to reset head"), shipped in v2.6.37 and later.

Only if v2.6.37 or later still prints a "render ring head" error there might be a reason to have another look at this. For now CLOSED/UPSTREAM or whatever?

(In reply to comment #4) 
> Sometimes  I cant to enter in system after hibernate, then I  to hold button
> off for reboot it. Maybe it is because of this error. What do you think about?

What I think is (or was) happening is this: the pre v2.6.37 kernel always printed two errors at every boot and at every thaw (ie, after hibernation). My guess is the errors printed at boot where hidden by the graphical boot magic (plymouth). When this laptop hibernates and thaws there's some switching between graphical and text mode going on. In text mode those scary boot errors suddenly become visible, and at thaw were moreover followed by two identical errors. That suggests there's something wrong. But in fact these errors were most likely just false alarms.

Does this look plausible to reporter? Whatever actually happens, hibernation problems are, at least in my experience, hard to pinpoint. In this case there's currently no strong reason to suspect the i915 drm code more than any other part of the kernel.

(In reply to comment #9)
> I added to kernel parameter drm.debug=0x04 and I replayed error. This is files
> with report (/var/log/dmesg,
> /etc/X11/xorg.conf.d/00-system-setup-keyboard.conf, /var/log/messages,
> /var/log/Xorg.0.log).

Side note: the files attached in comment 5, comment 6, comment 7 and comment 8 should be all plain text files, shouldn't they? But for some reason bugzilla treats them as binary blobs, not to be viewed from within a browser. They need to be downloaded to be viewed. I was also unable (or not allowed?) to flip some switch to get these handled as text files.

Are files like these handled as blobs by design or by webmaster choice or for another reason?

Are files like these handled as blobs by design or by webmaster choice or for
another reason?

I don't understand question. This is text files.

(In reply to comment #13)
> This is text files.
That is what I think too. And maybe you are allowed to change the MIME type of these attachments on their details page from application/octet-stream to text/plain. Are you?

Sorry. I don't  understand what I has to do. What is MIME?

(In reply to comment #15)
> What is MIME?
0) Not very interesting, see http://en.wikipedia.org/wiki/MIME .

1) Go to
    https://bugzilla.redhat.com/attachment.cgi?id=511210&action=edit

(and the similar pages for the other attachments) and see if you can change
    application/octet-stream

to
    text/plain

Going with the suggestion in comment #10