From: John Doe <securef33d@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Call trace on SKL with 4.3.0-rc3+ kernel
Date: Tue, 27 Oct 2015 16:59:11 +0100 [thread overview]
Message-ID: <562F9F4F.70407@gmail.com> (raw)
In-Reply-To: <87611svedh.fsf@intel.com>
On 27/10/2015 10:40, Jani Nikula wrote:
> On Tue, 27 Oct 2015, Kai Huang <kai.huang@linux.intel.com> wrote:
>> I got below Call Trace when booting my 4.3.0-rc3+ kernel on my SKL DT
>> machine. Although my machine boots up despite this call trace, I think
>> it's better to report it (and hopefully this is the right mailing list
>> to report).
>
> Please try v4.3-rc7. If that doesn't help, please file a bug at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
>
> BR,
> Jani.
>
Hi,
I'm testing 4.3-rc7 and got a similar crash (i7-6700k on z170), the
machine fails to boot.
[ 5.063912] ------------[ cut here ]------------
[ 5.063941] WARNING: CPU: 1 PID: 6 at
/home/user/n/qubes-builder/qubes-src/linux-kernel/kernel-4.3.0/linux-4.3.0/drivers/gpu/drm/i915/intel_pm.c:3668
skl_update_other_pipe_wm+0x1f3/0x200)
[ 5.063942] WARN_ON(!wm_changed)
[ 5.063950] Modules linked in: crct10dif_pclmul crc32_pclmul
crc32c_intel nouveau(+) mxm_wmi radeon(+) i915 intel_gtt i2c_algo_bit
drm_kms_helper ttm drm agpgart wmi video xen_pciback xek
[ 5.063951] CPU: 1 PID: 6 Comm: kworker/u4:0 Not tainted
4.3.0-1.pvops.qubes.x86_64 #1
[ 5.063952] Hardware name: To Be Filled By O.E.M. To Be Filled By
O.E.M./Z170 Extreme4, BIOS P2.10 10/14/2015
[ 5.063958] Workqueue: events_unbound async_run_entry_fn
[ 5.063960] 0000000000000000 00000000624b15e0 ffff88086bb67400
ffffffff81394b54
[ 5.063964] ffff88086bb67448 ffff88086bb67438 ffffffff8109ced2
ffff8808677f8000
[ 5.063965] ffff88086bb67594 ffff88086bb674e0 ffff8808677fb000
0000000000000000
[ 5.063965] Call Trace:
[ 5.063972] [<ffffffff81394b54>] dump_stack+0x44/0x60
[ 5.063975] [<ffffffff8109ced2>] warn_slowpath_common+0x82/0xc0
[ 5.063976] [<ffffffff8109cf6c>] warn_slowpath_fmt+0x5c/0x80
[ 5.063997] [<ffffffffa015f9f3>]
skl_update_other_pipe_wm+0x1f3/0x200 [i915]
[ 5.064013] [<ffffffffa015fbbb>] skl_update_wm+0x1bb/0x700 [i915]
[ 5.064028] [<ffffffff8172dae9>] ? error_exit+0x9/0x20
[ 5.064044] [<ffffffffa01610be>] intel_update_watermarks+0x1e/0x30
[i915]
[ 5.064073] [<ffffffffa01c0f46>] haswell_crtc_enable+0x476/0xbd0 [i915]
[ 5.064098] [<ffffffffa01bdeef>] intel_atomic_commit+0x36f/0x630 [i915]
[ 5.064114] [<ffffffffa0068e24>] ? drm_atomic_check_only+0x1d4/0x570
[drm]
[ 5.064128] [<ffffffffa00691f7>] drm_atomic_commit+0x37/0x60 [drm]
[ 5.064135] [<ffffffffa00f09d4>]
drm_atomic_helper_set_config+0x1c4/0x430 [drm_kms_helper]
[ 5.064144] [<ffffffffa0059052>]
drm_mode_set_config_internal+0x62/0x100 [drm]
[ 5.064151] [<ffffffffa00f37eb>] restore_fbdev_mode+0xab/0x110
[drm_kms_helper]
[ 5.064157] [<ffffffffa00f5685>]
drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
[ 5.064159] [<ffffffffa00f56fd>] drm_fb_helper_set_par+0x2d/0x50
[drm_kms_helper]
[ 5.064188] [<ffffffffa01d20ea>] intel_fbdev_set_par+0x1a/0x60 [i915]
[ 5.064190] [<ffffffff81401cd3>] fbcon_init+0x533/0x5a0
[ 5.064195] [<ffffffff814837ca>] visual_init+0xca/0x130
[ 5.064196] [<ffffffff81485ec8>] do_bind_con_driver+0x168/0x390
[ 5.064197] [<ffffffff8148639c>] do_take_over_console+0xac/0x1a0
[ 5.064198] [<ffffffff813fcef7>] do_fbcon_takeover+0x57/0xb0
[ 5.064199] [<ffffffff81402746>] fbcon_event_notify+0x646/0x740
[ 5.064204] [<ffffffff810bbbca>] notifier_call_chain+0x4a/0x70
[ 5.064205] [<ffffffff810bbf07>]
__blocking_notifier_call_chain+0x47/0x60
[ 5.064206] [<ffffffff810bbf36>] blocking_notifier_call_chain+0x16/0x20
[ 5.064211] [<ffffffff814082cb>] fb_notifier_call_chain+0x1b/0x20
[ 5.064211] [<ffffffff8140a449>] register_framebuffer+0x209/0x340
[ 5.064214] [<ffffffffa00f5959>]
drm_fb_helper_initial_config+0x239/0x3c0 [drm_kms_helper]
[ 5.064241] [<ffffffffa01d31fb>]
intel_fbdev_initial_config+0x1b/0x20 [i915]
[ 5.064242] [<ffffffff810bd5da>] async_run_entry_fn+0x4a/0x140
[ 5.064243] [<ffffffff810b4d30>] process_one_work+0x150/0x3f0
[ 5.064244] [<ffffffff810b595e>] worker_thread+0x4e/0x460
[ 5.064248] [<ffffffff810b5910>] ? rescuer_thread+0x300/0x300
[ 5.064249] [<ffffffff810bab78>] kthread+0xd8/0xf0
[ 5.064250] [<ffffffff810baaa0>] ? kthread_park+0x60/0x60
[ 5.064251] [<ffffffff8172ba1f>] ret_from_fork+0x3f/0x70
[ 5.064256] [<ffffffff810baaa0>] ? kthread_park+0x60/0x60
[ 5.064256] ---[ end trace 18eaeb20a49fdf89 ]---
John.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-27 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 7:34 Call trace on SKL with 4.3.0-rc3+ kernel Kai Huang
2015-10-27 9:40 ` Jani Nikula
2015-10-27 15:59 ` John Doe [this message]
2015-10-28 1:11 ` Matt Roper
2015-10-28 12:42 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=562F9F4F.70407@gmail.com \
--to=securef33d@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.