[Intel-gfx] still experiencing oops connecting Laptop to docking Station

Wed May 20 10:06:35 PDT 2015

> Two things:
> - Can you please boot with drm.debug=0xff and enable full debug output
> to the console with dmesg -n debug and try to recapture? I'd like to
> know what exactly happened right before. There should be lots of debug
> output right before the oops.

There ya go. dmesg with drm.debug=0xff right to the point where I plugin to my dock and the driver dies: http://pastebin.com/0mWxZ1Nr

> - Can you please decode a few symbols:
> gdb drivers/gpu/drm/drm_atomic_helper.c
> (gdb) break *drm_atomic_helper_check_modeset+0x2c5

I've never tried to debug a kernel module. You know a good howto? ;)

Cheers
Nic

Gesendet: Mittwoch, 20. Mai 2015 um 18:39 Uhr
Von: "Daniel Vetter" <daniel at ffwll.ch>
An: "Nicolas Kalkhof" <nkalkhof at web.de>
Cc: intel-gfx <Intel-gfx at lists.freedesktop.org>
Betreff: Re: Re: [Intel-gfx] still experiencing oops connecting Laptop to docking Station
On Wed, May 20, 2015 at 6:00 PM, Nicolas Kalkhof <nkalkhof at web.de> wrote:
> Hi Daniel,
>
> ok here is the first oops showing up on the screen. Image is not too good though. http://imgur.com/O0kutIE
>
> Btw. did you take a look at the stacktrace I've posted below complaining about complaining about pipe state doesn't match?

Two things:
- Can you please boot with drm.debug=0xff and enable full debug output
to the console with dmesg -n debug and try to recapture? I'd like to
know what exactly happened right before. There should be lots of debug
output right before the oops.
- Can you please decode a few symbols:

gdb drivers/gpu/drm/drm_atomic_helper.c
(gdb) break *drm_atomic_helper_check_modeset+0x2c5

Please also paste around that line and indicate which one it is (since
that always moves around).

Thanks, Daniel

> Gesendet: Mittwoch, 20. Mai 2015 um 17:38 Uhr
> Von: "Daniel Vetter" <daniel at ffwll.ch>
> An: "Nicolas Kalkhof" <nkalkhof at web.de>
> Cc: intel-gfx <Intel-gfx at lists.freedesktop.org>
> Betreff: Re: [Intel-gfx] still experiencing oops connecting Laptop to docking Station
> On Wed, May 20, 2015 at 5:05 PM, Nicolas Kalkhof <nkalkhof at web.de> wrote:
>> Hallo,
>>
>> I'm still getting oops with drm-intel-nightly when I try to connect my Laptop to its docking station or when I boot up and the Laptop is already connected.
>>
>> kdump doesn't seem to work with current drm-intel-nightly so I've attached an Image (sorry for the bad quality). http://imgur.com/463ZQny[http://imgur.com/463ZQny]
>
> Looks like the culprit has already scrolled off the screen and the
> oops you've captured is just follow-up fallout. Can you try booting
> with pause_on_oops=60 and try to capture the very first oops?
>
> Thanks, Daniel
>
>>
>>
>> My system boots up without Kernel Panic when NOT connected to dock. However dmesg still reveals a problem:
>>
>> [ 20.137622] [drm:intel_connector_check_state] [CONNECTOR:33:eDP-1]
>> [ 20.137625] [drm:check_encoder_state] [ENCODER:31:DAC-31]
>> [ 20.137626] [drm:check_encoder_state] [ENCODER:32:TMDS-32]
>> [ 20.137627] [drm:check_encoder_state] [ENCODER:40:TMDS-40]
>> [ 20.137628] [drm:check_encoder_state] [ENCODER:42:DP MST-42]
>> [ 20.137629] [drm:check_encoder_state] [ENCODER:43:DP MST-43]
>> [ 20.137629] [drm:check_encoder_state] [ENCODER:44:DP MST-44]
>> [ 20.137630] [drm:check_encoder_state] [ENCODER:47:TMDS-47]
>> [ 20.137630] [drm:check_encoder_state] [ENCODER:49:DP MST-49]
>> [ 20.137631] [drm:check_encoder_state] [ENCODER:50:DP MST-50]
>> [ 20.137631] [drm:check_encoder_state] [ENCODER:51:DP MST-51]
>> [ 20.137632] [drm:check_crtc_state] [CRTC:20]
>> [ 20.137640] [drm:check_crtc_state] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0x90280202, found 0x00000000)
>> [ 20.137641] ------------[ cut here ]------------
>> [ 20.137643] WARNING: CPU: 0 PID: 1086 at drivers/gpu/drm/i915/intel_display.c:12114 check_crtc_state+0x8a5/0xfc0()
>> [ 20.137643] pipe state doesn't match!
>> [ 20.137644] Modules linked in: snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic iwlmvm iwlwifi snd_hda_intel snd_hda_codec snd_hda_core snd_pcm snd_timer
>> [ 20.137651] CPU: 0 PID: 1086 Comm: X Tainted: G W 4.1.0-rc4+ #5
>> [ 20.137652] Hardware name: LENOVO qqqqENX407/qqqqENX407, BIOS GLET77WW (2.31 ) 01/27/2015
>> [ 20.137652] 0000000000000000 ffffffff817c5f10 ffffffff81645beb ffff880406cb7878
>> [ 20.137654] ffffffff81047047 ffff880409d87000 ffff88040be64000 ffff88040bf70000
>> [ 20.137655] 0000000000000001 ffff88040be64340 ffffffff810470c5 ffffffff817f43d3
>> [ 20.137657] Call Trace:
>> [ 20.137660] [<ffffffff81645beb>] ? dump_stack+0x40/0x50
>> [ 20.137663] [<ffffffff81047047>] ? warn_slowpath_common+0x77/0xb0
>> [ 20.137665] [<ffffffff810470c5>] ? warn_slowpath_fmt+0x45/0x50
>> [ 20.137666] [<ffffffff8137d555>] ? check_crtc_state+0x8a5/0xfc0
>> [ 20.137668] [<ffffffff8108d504>] ? ktime_get+0x34/0xb0
>> [ 20.137671] [<ffffffff8138ff29>] ? intel_modeset_check_state+0x229/0xb50
>> [ 20.137673] [<ffffffff81390e38>] ? intel_crtc_set_config+0x578/0x650
>> [ 20.137675] [<ffffffff8131136f>] ? drm_mode_set_config_internal+0x5f/0x100
>> [ 20.137677] [<ffffffff81315cda>] ? drm_mode_setcrtc+0x22a/0x5f0
>> [ 20.137679] [<ffffffff8130766a>] ? drm_ioctl+0x15a/0x580
>> [ 20.137682] [<ffffffff81108ce8>] ? do_vfs_ioctl+0x2e8/0x4f0
>> [ 20.137684] [<ffffffff8103c19b>] ? __do_page_fault+0x17b/0x3e0
>> [ 20.137685] [<ffffffff81108f26>] ? SyS_ioctl+0x36/0x80
>> [ 20.137688] [<ffffffff8164dd9b>] ? system_call_fastpath+0x16/0x6e
>> [ 20.137688] ---[ end trace a67764a031b81585 ]---
>>
>> Full dmesg goes here: http://pastebin.com/fzjnsfyQ[http://pastebin.com/fzjnsfyQ][http://pastebin.com/fzjnsfyQ[http://pastebin.com/fzjnsfyQ]]
>>
>> Any Clues?
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx[http://lists.freedesktop.org/mailman/listinfo/intel-gfx][http://lists.freedesktop.org/mailman/listinfo/intel-gfx[http://lists.freedesktop.org/mailman/listinfo/intel-gfx]]
>
>
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch[http://blog.ffwll.ch][http://blog.ffwll.ch[http://blog.ffwll.ch]]

--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch[http://blog.ffwll.ch]