Bug 60307

Summary: [SNB ILK regression] Call trace appears while doing fbset
Product: DRI Reporter: cancan,feng <cancan.feng>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium CC: cancan.feng, yangweix.shui
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg of calltrace caused by fbset
none
config info of kernel with kernel hijack options none

Description cancan,feng 2013-02-05 07:20:10 UTC 
System Environment:
--------------------------------------------
Kernel: (drm-intel-next-queued)7d37beaaf3dbc6ff16f4d32a4dd6f8c557c6ab50
Some additional commit info:
Author: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Date:   Fri Feb 1 10:14:20 2013 +0900

    GPU/i915: Fix acpi_bus_get_device() check in drivers/gpu/drm/i915/intel_opregion.c


Bug detailed description:
--------------------------------------------
Fbset will cause calltrace. And I found that only happened at kernel with kernel hijack options. If I disable the kernel hijack options, then build kernel and redo fbset, calltrace will not happen. Bisect is on the way, I will paste the first commit info later. 


Reproduce steps:
--------------------------------------------
1. reboot or start 
2. fbset -xres 800 -yres 600
Comment 1 cancan,feng 2013-02-05 07:24:54 UTC 
Created attachment 74219 [details]
dmesg of calltrace caused by fbset
Comment 2 cancan,feng 2013-02-05 08:31:36 UTC 
Created attachment 74221 [details]
config info of kernel with kernel hijack options
Comment 3 Daniel Vetter 2013-02-05 11:59:01 UTC 
Oh, the console_lock mess. Can you please test the fbcon-locking-fixes branch from http://cgit.freedesktop.org/~airlied/linux ?

The bugs have always been there, we've only just added new infrastructure to extend lockdep coverage to the console_lock. So bisecting isn't required.
Comment 4 cancan,feng 2013-02-06 02:20:27 UTC 
(In reply to comment #3)
> Oh, the console_lock mess. Can you please test the fbcon-locking-fixes
> branch from http://cgit.freedesktop.org/~airlied/linux ?

Ok, I have tested the top commit 1b6d764d4bd20fc90284dc59825a6fbf1f7726f7 of branch fbcon-locking-fixes, call trace did not happen any more. 


The bugs have
> always been there, we've only just added new infrastructure to extend
> lockdep coverage to the console_lock. So bisecting isn't required.
Comment 5 Chris Wilson 2013-02-26 21:26:14 UTC 
The fbcon mess is (resolved) upstream.
Comment 6 cancan,feng 2013-02-28 01:56:27 UTC 
(In reply to comment #5)
> The fbcon mess is (resolved) upstream.

Ok, I tested our -nightly branch, the fbcon mess is gone. Here is the kernel info:
---------------------------------------------------
Description :
The Linux Kernel, the operating system core itself
Kernel: (drm-intel-nightly)15caa9b2bad16e0d4bf8c203dcc8325b1894ad09
Some additional commit info:
Merge: 8e14494 de0babd
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Feb 22 13:05:06 2013 +0100
--------------------------------------------------
Comment 7 Elizabeth 2017-10-06 14:46:56 UTC 
Closing old verified.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.