[Bug 54661] New: Backlight doesn't turn on after suspend on Acer 1830T with Ironlake chip
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Sat Mar 2 03:55:12 PST 2013
https://bugzilla.kernel.org/show_bug.cgi?id=54661
Summary: Backlight doesn't turn on after suspend on Acer 1830T
with Ironlake chip
Product: Drivers
Version: 2.5
Kernel Version: 3.8.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - Intel)
AssignedTo: intel-gfx-bugs at lists.freedesktop.org
ReportedBy: itumaykin at gmail.com
CC: intel-gfx-bugs at lists.freedesktop.org
Regression: Yes
Created an attachment (id=94281)
--> (https://bugzilla.kernel.org/attachment.cgi?id=94281)
lspci -vvv
After upgrading my kernel to 3.8.1 I've noticed that backlight doesn't
automatically turn on when I wake my notebook from suspend. The only way to get
backlight back is to press brightness control buttons. The following stack
trace is in my dmesg every time I do suspend/resume:
[22762.594676] ------------[ cut here ]------------
[22762.594700] WARNING: at drivers/gpu/drm/i915/i915_gem.c:1021
__wait_seqno+0x4fd/0x530 [i915]()
[22762.594701] Hardware name: Aspire 1830T
[22762.594728] Modules linked in: ipv6 nf_conntrack_ipv4 nf_defrag_ipv4
xt_conntrack nf_conntrack iptable_filter ip_tables bnep bluetooth dm_mod
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev ums_realtek
hid_logitech_dj i915 intel_agp iTCO_wdt acer_wmi iTCO_vendor_support ath9k
ath9k_common ath9k_hw ath atl1c mac80211 cfg80211 sparse_keymap drm_kms_helper
intel_gtt video wmi
[22762.594731] Pid: 13103, comm: kworker/u:0 Tainted: G W
3.8.1-ACER-1830T #1
[22762.594732] Call Trace:
[22762.594743] [<ffffffff8103907b>] ? warn_slowpath_common+0x7b/0xc0
[22762.594753] [<ffffffffa01dc5dd>] ? __wait_seqno+0x4fd/0x530 [i915]
[22762.594766] [<ffffffffa0211501>] ? __i915_update_gfx_val+0x31/0xf0 [i915]
[22762.594778] [<ffffffffa02141a4>] ? i915_update_gfx_val+0x24/0x40 [i915]
[22762.594788] [<ffffffffa01dcd5f>] ? i915_add_request+0x2bf/0x2e0 [i915]
[22762.594800] [<ffffffffa0214a2f>] ? intel_enable_gt_powersave+0x49f/0x870
[i915]
[22762.594813] [<ffffffffa01fc2aa>] ? intel_modeset_init_hw+0x3a/0x50 [i915]
[22762.594820] [<ffffffffa01c91c9>] ? __i915_drm_thaw+0xd9/0xf0 [i915]
[22762.594828] [<ffffffffa01c96f4>] ? i915_resume+0x74/0xd0 [i915]
[22762.594834] [<ffffffff812d18a0>] ? pci_pm_thaw+0x80/0x80
[22762.594842] [<ffffffff8137d3b6>] ? dpm_run_callback.isra.5+0x36/0x80
[22762.594845] [<ffffffff8137d6d6>] ? device_resume+0xa6/0x140
[22762.594849] [<ffffffff8137d784>] ? async_resume+0x14/0x40
[22762.594853] [<ffffffff810630f7>] ? async_run_entry_fn+0xa7/0x1c0
[22762.594858] [<ffffffff81055d07>] ? process_one_work+0x117/0x530
[22762.594861] [<ffffffff81053119>] ? need_to_create_worker+0x9/0x20
[22762.594865] [<ffffffff81055a8f>] ? manage_workers+0x1df/0x2a0
[22762.594867] [<ffffffff81063050>] ? async_schedule+0x10/0x10
[22762.594871] [<ffffffff81056562>] ? worker_thread+0x182/0x490
[22762.594874] [<ffffffff810645bf>] ? __wake_up_common+0x4f/0x80
[22762.594878] [<ffffffff810563e0>] ? rescuer_thread+0x280/0x280
[22762.594881] [<ffffffff8105b9e3>] ? kthread+0xb3/0xc0
[22762.594884] [<ffffffff81060000>] ? hrtimers_resume+0x10/0x50
[22762.594887] [<ffffffff8105b930>] ? kthread_freezable_should_stop+0x60/0x60
[22762.594891] [<ffffffff81564b2c>] ? ret_from_fork+0x7c/0xb0
[22762.594922] [<ffffffff8105b930>] ? kthread_freezable_should_stop+0x60/0x60
[22762.594924] ---[ end trace 5bb601912bd1588a ]---
[22762.594927] [drm:ironlake_enable_rc6] *ERROR* failed to enable ironlake
power power savings
There was no such problem with 3.8.0. My notebook is Acer 1830T with Ironlake
chip running Gentoo amd64. I've attached lscpi output and if you need some more
info I am ready to provide it.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the intel-gfx-bugs
mailing list