[Bug 78424] New: [HSW Regression]S4 causes Call Trace

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu May 8 00:08:49 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=78424

          Priority: medium
            Bug ID: 78424
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [HSW Regression]S4 causes Call Trace
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: lei.a.liu at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 98664
  --> https://bugs.freedesktop.org/attachment.cgi?id=98664&action=edit
I attach a dmesg.

*System Environment:
--------------------------
Regression: Yes. Good commit:
484b41dd70a9fbea894632d8926bbb93f05021c7(-drm-intel-next-queued). 
commit 484b41dd70a9fbea894632d8926bbb93f05021c7
Author:     Jesse Barnes <jbarnes at virtuousgeek.org>
AuthorDate: Fri Mar 7 08:57:55 2014 -0800
Commit:     Daniel Vetter <daniel.vetter at ffwll.ch>
CommitDate: Sat Mar 8 11:31:58 2014 +0100

    drm/i915: remove early fb allocation dependency on CONFIG_FB v2

    By stuffing the fb allocation into the crtc, we get mode set lifetime
    refcounting for free, but have to handle the initial pin & fence
    slightly differently.  It also means we can move the shared fb handling
    into the core rather than leaving it out in the fbdev code.

    v2: null out crtc->fb on error (Daniel)
        take fbdev fb ref and remove unused error path (Daniel)

Non-working platforms: Haswell
 *kernel: 
--------------------------
-nightly: dd28119c31cf06fc4c3bb548699018a91e45a676 (s4 cause Call Trace)
-queued: 10efa9321e (s4 cause Call Trace)
   commit 10efa9321efe5f62637b189587539e4086726a2b
   Author:     Ville Syrjälä <ville.syrjala at linux.intel.com>
   AuthorDate: Mon Apr 28 15:53:25 2014 +0300
   Commit:     Daniel Vetter <daniel.vetter at ffwll.ch>
   CommitDate: Tue May 6 10:18:04 2014 +0200

    drm/i915: Remove useless checks from primary enable/disable

    We won't be calling intel_enable_primary_plane() or
    intel_disable_primary_plane() with the primary plane in the
    wrong state. So remove the useless DISPLAY_PLANE_ENABLE checks.

    v2: Convert the checks to WARNs instead (Daniel,Paulo)

    Detail of the commit
-fixes: e4c610fe0 (s4 cause Call Trace)
   commit e4c610fe051579ba0a1fadf339905b0231c6ef94
   Author:     Egbert Eich <eich at suse.de>
   AuthorDate: Fri Apr 11 19:07:44 2014 +0200
   Commit:     Jani Nikula <jani.nikula at intel.com>
   CommitDate: Wed May 7 15:01:50 2014 +0300

    drm/i915/SDVO: For sysfs link put directory and target in correct order

    When linking the i2c sysfs file into the connector's directory
    pass directory and link target in the right order.
    This code was introduced with:

      commit 931c1c26983b4f84e33b78579fc8d57e4a14c6b4
      Author: Imre Deak <imre.deak at intel.com>
      Date:   Tue Feb 11 17:12:51 2014 +0200

        drm/i915: sdvo: add i2c sysfs symlink to the connector's directory

        This is the same what we do for DP connectors, so make things more
        consistent.

*Bug detailed description:
-----------------------------
do S4 ,and check dmesg .

[  101.206995] ------------[ cut here ]------------
[  101.207009] WARNING: CPU: 4 PID: 1123 at
drivers/gpu/drm/i915/intel_ddi.c:960 intel_ddi_pll_enable+0x191/0x1ef [i915]()
[  101.207009] SPLL already enabled
[  101.207016] Modules linked in: dm_mod snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support serio_raw
pcspkr i2c_i801 lpc_ich mfd_core snd_hda_intel snd_hda_controller snd_hda_codec
snd_hwdep snd_pcm snd_timer snd soundcore battery wmi tpm_infineon tpm_tis tpm
acpi_cpufreq i915 video button drm_kms_helper drm
[  101.207018] CPU: 4 PID: 1123 Comm: kworker/u16:6 Not tainted
3.15.0-rc3_drm-intel-next-queued_1cf0ba_20140508+ #2418
[  101.207018] Hardware name: ASUS All Series/Z87-EXPERT, BIOS 1008 05/17/2013
[  101.207021] Workqueue: events_unbound async_run_entry_fn
[  101.207023]  0000000000000000 0000000000000009 ffffffff817233c0
ffff8802514b1ad8
[  101.207023]  ffffffff8103517a ffff8802514b1ad0 ffffffffa00b04f1
0000000000000001
[  101.207024]  ffff8802512e0000 0000000094000000 ffffffffa00e65d0
0000000000000000
[  101.207025] Call Trace:
[  101.207028]  [<ffffffff817233c0>] ? dump_stack+0x41/0x51
[  101.207030]  [<ffffffff8103517a>] ? warn_slowpath_common+0x73/0x8b
[  101.207035]  [<ffffffffa00b04f1>] ? intel_ddi_pll_enable+0x191/0x1ef [i915]
[  101.207037]  [<ffffffff8103522a>] ? warn_slowpath_fmt+0x45/0x4a
[  101.207043]  [<ffffffffa008e2fb>] ? gen6_read32+0x71/0x7c [i915]
[  101.207048]  [<ffffffffa00b04f1>] ? intel_ddi_pll_enable+0x191/0x1ef [i915]
[  101.207052]  [<ffffffffa0005546>] ? drm_vblank_get+0x1e0/0x1f2 [drm]
[  101.207058]  [<ffffffffa009a1be>] ? haswell_crtc_mode_set+0x44/0x433 [i915]
[  101.207064]  [<ffffffffa009f363>] ? __intel_set_mode+0xfd7/0x11b9 [i915]
[  101.207071]  [<ffffffffa00a2b93>] ? intel_modeset_setup_hw_state+0x8ff/0x9d8
[i915]
[  101.207077]  [<ffffffffa008e98d>] ? hsw_write64+0x9b/0x9b [i915]
[  101.207084]  [<ffffffffa008e98d>] ? hsw_write64+0x9b/0x9b [i915]
[  101.207088]  [<ffffffffa0060411>] ? __i915_drm_thaw+0xe8/0x1d9 [i915]
[  101.207090]  [<ffffffff812fe516>] ? pci_pm_default_resume+0x29/0x29
[  101.207095]  [<ffffffffa0060a4c>] ? i915_resume+0x1f/0x39 [i915]
[  101.207099]  [<ffffffffa0060a6d>] ? i915_pm_resume+0x7/0x11 [i915]
[  101.207102]  [<ffffffff813896c1>] ? dpm_run_callback.isra.8+0x24/0x52
[  101.207104]  [<ffffffff81389cb0>] ? device_resume+0x10c/0x14e
[  101.207105]  [<ffffffff81389d06>] ? async_resume+0x14/0x38
[  101.207106]  [<ffffffff8104f683>] ? async_run_entry_fn+0x55/0x10b
[  101.207108]  [<ffffffff81046844>] ? process_one_work+0x1bc/0x2ed
[  101.207110]  [<ffffffff81046db2>] ? worker_thread+0x1c7/0x2bc
[  101.207111]  [<ffffffff81046beb>] ? rescuer_thread+0x251/0x251
[  101.207112]  [<ffffffff8104b722>] ? kthread+0xc5/0xcd
[  101.207113]  [<ffffffff8104b65d>] ? kthread_freezable_should_stop+0x40/0x40
[  101.207114]  [<ffffffff8172dafc>] ? ret_from_fork+0x7c/0xb0
[  101.207115]  [<ffffffff8104b65d>] ? kthread_freezable_should_stop+0x40/0x40
[  101.207116] ---[ end trace db4d3e1dc7c3c334 ]---


*Reproduce steps:
---------------------------- 
1. echo 0 > /sys/class/rtc/rtc0/wakealarm ; 
   echo +10 > /sys/class/rtc/rtc0/wakealarm; 
   echo disk > /sys/power/state
   (do S4)
2. dmesg

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140508/dec1cc92/attachment.html>


More information about the intel-gfx-bugs mailing list