[Bug 93711] BUG in i915_gem.c freezed the console
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Thu Mar 26 00:00:13 PDT 2015
https://bugzilla.kernel.org/show_bug.cgi?id=93711
--- Comment #23 from Martin Ziegler <ziegler at uni-freiburg.de> ---
Ich applied Damien's patch to 4.0-rc5.
Before the patch I had two warnings druring boot:
WARNING: CPU: 3 PID: 1 at include/linux/kref.h:47
drm_framebuffer_reference+0x56/0x5f()
WARNING: CPU: 2 PID: 6 at drivers/gpu/drm/drm_atomic.c:482
drm_atomic_check_only+0x3a9/0x3cf()
After the patch only the following warning:
Mar 25 21:46:01 zertz kernel: [drm] GMBUS [i915 gmbus dpb] timed out,
falling back to bit banging on pin 5
...
fbcon: inteldrmfb (fb0) is primary device
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/drm_atomic.c:482
drm_atomic_check_only+0x3a9/0x3cf()
Modules linked in:
CPU: 0 PID: 6 Comm: kworker/u8:0 Tainted: G U
4.0.0-rc5-00003-gad5de1d #77
Hardware name: LENOVO 4349WK7/4349WK7, BIOS 6MET81WW (1.41) 10/26/2010
Workqueue: events_unbound async_run_entry_fn
0000000000000000 0000000000000009 ffffffff813d2040 0000000000000000
ffffffff81036594 ffff8801334c2710 ffffffff81241786 0000000000000088
ffff8800b6c66180 ffff8800b6c93000 0000000000000002 ffff8800b6c5a180
Call Trace:
[<ffffffff813d2040>] ? dump_stack+0x40/0x50
[<ffffffff81036594>] ? warn_slowpath_common+0x93/0xab
[<ffffffff81241786>] ? drm_atomic_check_only+0x3a9/0x3cf
[<ffffffff81241786>] ? drm_atomic_check_only+0x3a9/0x3cf
[<ffffffff812417ba>] ? drm_atomic_commit+0xe/0x4d
[<ffffffff812264da>] ?
drm_atomic_helper_plane_set_property+0x68/0xa3
[<ffffffff81240c43>] ? modeset_lock+0x8f/0xf2
[<ffffffff812345ee>] ? drm_mode_plane_set_obj_prop+0x28/0x49
[<ffffffff81227a8c>] ? restore_fbdev_mode+0x5f/0xc7
[<ffffffff8122934c>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x1e/0x54
[<ffffffff812293b0>] ? drm_fb_helper_set_par+0x2e/0x32
[<ffffffff8129fc1b>] ? intel_fbdev_set_par+0x11/0x55
[<ffffffff811bc715>] ? fbcon_init+0x327/0x442
[<ffffffff81209ec1>] ? visual_init+0xaf/0x102
[<ffffffff8120b422>] ? do_bind_con_driver+0x18e/0x295
[<ffffffff8120b9db>] ? do_take_over_console+0x150/0x179
[<ffffffff811b90df>] ? do_fbcon_takeover+0x58/0x94
[<ffffffff8104a8de>] ? notifier_call_chain+0x35/0x59
[<ffffffff8104aaff>] ?
__blocking_notifier_call_chain+0x42/0x5d
[<ffffffff811c0017>] ? register_framebuffer+0x281/0x2b4
[<ffffffff81229632>] ? drm_fb_helper_initial_config+0x27e/0x330
[<ffffffff81001684>] ? __switch_to+0x1ff/0x45d
[<ffffffff8104bb5a>] ? async_run_entry_fn+0x2d/0xbf
[<ffffffff810467a5>] ? process_one_work+0x142/0x214
[<ffffffff81046ce3>] ? worker_thread+0x1c3/0x26d
[<ffffffff81046b20>] ? rescuer_thread+0x284/0x284
[<ffffffff8104a0c8>] ? kthread+0xab/0xb3
[<ffffffff81040000>] ? get_signal+0x2e0/0x4ce
[<ffffffff8104a01d>] ? __kthread_parkme+0x5d/0x5d
[<ffffffff813d60c8>] ? ret_from_fork+0x58/0x90
[<ffffffff8104a01d>] ? __kthread_parkme+0x5d/0x5d
---[ end trace 8d8be2074054d8dc ]---
Martin
--
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