From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Skillen Subject: Re: i915 kernel driver errors Date: Mon, 21 Jul 2014 17:16:38 -0400 Message-ID: <53CD8336.2060201@ccsl.carleton.ca> References: <53CA7A3D.8090305@ccsl.carleton.ca> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------040201070704010807000101" Return-path: Received: from shakespeare.ccsl.carleton.ca (shakespeare.ccsl.carleton.ca [134.117.225.58]) by gabe.freedesktop.org (Postfix) with ESMTP id BFBA76E11A for ; Mon, 21 Jul 2014 14:17:07 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Daniel Vetter Cc: intel-gfx List-Id: intel-gfx@lists.freedesktop.org This is a multi-part message in MIME format. --------------040201070704010807000101 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi Daniel, I captured the error log when booting with "drm.debug=14" on the 3.16-rc5 branch, after reproducing the error. Please see attached. I also attached the dmesg output to the bug report filed at: https://bugs.freedesktop.org/show_bug.cgi?id=81537 Sorry for duplicating this bug report, but after mailing the intel-gfx list, it occurred to me that this probably belongs under intel-gfx-bugs. I will build drm-intel-nightly shortly and attach the error log to the bug report at the URL above. I can CC the output to intel-gfx if you'd like. Thanks for your time, Adam Skillen On 14-07-21 04:15 PM, Daniel Vetter wrote: > On Sat, Jul 19, 2014 at 4:01 PM, Adam Skillen wrote: >> After upgrading my kernel from 3.11 to 3.13, I have been experiencing >> issues with graphical freezes. Specific dmesg errors started showing up >> after the upgrade (see below). >> >> When waking the screen from power saving/screensaver, the primary >> display wakes but X stops responding to input (the mouse cursor can >> still move, but clicking has no effect). Secondary display does not wake. >> >> This issue persists up to the latest 3.16-rc5. A commit bisect shows >> that fdbc3b1f639bb2cbfb32c612b2699e0ba373317d is the first bad commit. >> Reverting that commit on the 3.16-rc5 branch seemed to fix the problem. >> >> >> The original bug report also contains relevant logs and configuration >> information (e.g., Xorg.0.log, lspci, etc.): >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1343543 >> >> Please let me know if you require any further logs or information. > > Can you please boot with drm.debug=0xe added to your kernel cmdline, > reproduce the issue and then attach the complete dmesg? You might need > to increase the log buffer size with log_buf_len=4M or so. > > We have a bunch of changes queued up for 3.17 in the panel power > sequencing which might affect your machine. Please also test the > latest drm-intel-nightly git branch from > > http://cgit.freedesktop.org/drm-intel > > Thanks, Daniel > >> >> >> Sincerely, >> >> Adam Skillen >> >> >> >> >> Hardware: >> Dell System XPS L502X/0NJT03, BIOS A12 09/07/2012 >> Intel Corporation 2nd Generation Core Processor Family Integrated >> Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) >> >> >> >> >> Bisect result: >> fdbc3b1f639bb2cbfb32c612b2699e0ba373317d is the first bad commit >> >> $ git show >> commit fdbc3b1f639bb2cbfb32c612b2699e0ba373317d >> Author: Jani Nikula