Intel G41 doesn't see any screens connected after suspend/resume

Nikolay Martynov mar.kolya at gmail.com
Mon Mar 17 21:12:00 PDT 2014


Hi.

>>
>>   I would really appreciate if you could point me on some sort of
>> manual that describes how to properly run [2] on Ubuntu? Should I run
>> the whole kernel or just some modules? Is there any way to build only
>> requires modules?
>
> The whole kernel. See https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
> for a starting point; please use the drm-intel-nightly branch in our
> tree instead of Linus' tree.
>

  Thank you so much for that link.
  I've created a bug report about original suspend/resume issue:
https://bugs.freedesktop.org/show_bug.cgi?id=76301.

  I was able to build drm-intel-nightly kernel using instructions from
above link but unfortunately I run into issues:
  - It looks like I get unsigned kernel modules and this prevents
proper debug output, hopefully I would be able to resolve this on my
own but unfortunately I won't be able to provide useful dmesg just
yet.
  - The drm-intel-nightly '6e052fec0cc204f4d2a0f71f45c0363971ad10dc'
kernel hangs during boot on my aforementioned hardware. I've tried
several times and mostly I get black screen. But couple of times I got
some error output that stated something about softlock and lost
interrupts - and it was sort of slowly printing those errors, once
about 30 seconds. Unfortunately I do not have a hardcopy of that. The
interesting thing is that when I add 'nomodeset' to boot parameters
I'm able to successfully boot. I take it this is not expected and
probably is a regression. I would appreciate if you could suggest
course of action to debug this (and probably create another
bugreport).

Thanks!


-- 
Martynov Nikolay.
Email: mar.kolya at gmail.com


More information about the dri-devel mailing list