From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Subject: Re: Intel G41 doesn't see any screens connected after suspend/resume Date: Tue, 18 Mar 2014 10:29:10 +0200 Message-ID: <87k3brzz8p.fsf@intel.com> References: <87mwgp8e39.fsf@intel.com> <87zjkozxk6.fsf@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id 2BD8F2BB24 for ; Tue, 18 Mar 2014 01:28:57 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Nikolay Martynov Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Tue, 18 Mar 2014, Nikolay Martynov wrote: > 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). Perhaps you failed to install the modules that go with the kernel? BR, Jani. > > Thanks! > > > -- > Martynov Nikolay. > Email: mar.kolya@gmail.com -- Jani Nikula, Intel Open Source Technology Center