On 26 May 2014 19:19, Daniel Vetter <daniel@xxxxxxxx> wrote: > On Mon, May 26, 2014 at 8:07 PM, Pedro Ribeiro <pedrib@xxxxxxxxx> wrote: >> On 26 May 2014 10:22, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote: >>> On Sat, 24 May 2014, Pedro Ribeiro <pedrib@xxxxxxxxx> wrote: >>>> Hi, >>>> >>>> I'm getting this error consistently with the Debian 3.14.4 after >>>> resuming from hibernation: >>> >>> Does this ever happen on a fresh boot or when resuming from suspend to >>> ram? >>> >>> BR, >>> Jani. >>> >> >> Hi Jani, >> >> it seems to happen only on resume from disk (after waking up from >> hibernation, not suspend to ram), and only from the 2nd resume >> forward. It doesn't happen on fresh boot. > > Can you please boot with drm.debug=0xe added to your kernel cmdline, > reproduce the issue (i.e. do 2 suspend-to-disk cycles) and then attach > the complete dmesg. You probably need to grab it from logfiles on the > disk to avoid the beginning getting cut off. Hi Daniel, sorry for my ignorance, but do you know where in a Debian system would I have the full log output since boot time? The /var/log/dmesg does not seem to contain all the output in the "dmesg" command. Here is a cropped version that shows part of the debug and the error. Regards, Pedro > Thanks, Daniel > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Attachment:
dmesg.tar.gz
Description: GNU Zip compressed data
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
