still experiencing oops connecting Laptop to docking Station

still experiencing oops connecting Laptop to docking Station

[Nicolas Kalkhof]

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


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

Any Clues?
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Daniel Vetter]

On Wed, May 20, 2015 at 5:05 PM, Nicolas Kalkhof <nkalkhof@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

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
>
> Any Clues?
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Nicolas Kalkhof]

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?

Regards
Nic

Gesendet: Mittwoch, 20. Mai 2015 um 17:38 Uhr
Von: "Daniel Vetter" <daniel@ffwll.ch>
An: "Nicolas Kalkhof" <nkalkhof@web.de>
Cc: intel-gfx <Intel-gfx@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@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

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]
>
> Any Clues?
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> 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]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Daniel Vetter]

On Wed, May 20, 2015 at 6:00 PM, Nicolas Kalkhof <nkalkhof@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@ffwll.ch>
> An: "Nicolas Kalkhof" <nkalkhof@web.de>
> Cc: intel-gfx <Intel-gfx@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@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
>
> 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]
>>
>> Any Clues?
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> 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]



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Chris Wilson]

On Wed, May 20, 2015 at 06:39:26PM +0200, Daniel Vetter wrote:
> On Wed, May 20, 2015 at 6:00 PM, Nicolas Kalkhof <nkalkhof@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

Use "list *drm_atomic_helper_check_modeset+0x2c5"
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Nicolas Kalkhof]

> 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@ffwll.ch>
An: "Nicolas Kalkhof" <nkalkhof@web.de>
Cc: intel-gfx <Intel-gfx@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@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@ffwll.ch>
> An: "Nicolas Kalkhof" <nkalkhof@web.de>
> Cc: intel-gfx <Intel-gfx@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@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@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]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Daniel Vetter]

On Wed, May 20, 2015 at 07:06:35PM +0200, Nicolas Kalkhof wrote:
> > 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  

This only contains the pile of WARNINGs and not the Oops itself. I guess
we still need a picture (and you need to change the system console logging
to make sure the debug stuff shows up to). At least at the bottom of your
past there's from drm or i915, indicating that the crucial debug info
didn't make it out before the machine died.

> > - 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? ;)

I just want the decoded address (which I read from the oops, if you
recompile the kernel it might have changed so please double check). I.e.
the above two lines is all the howto you need. But please use "list"
instead of "break" as Chris suggested.

Thanks, Daniel

>  

> Cheers
> Nic
> 
> 
> Gesendet: Mittwoch, 20. Mai 2015 um 18:39 Uhr
> Von: "Daniel Vetter" <daniel@ffwll.ch>
> An: "Nicolas Kalkhof" <nkalkhof@web.de>
> Cc: intel-gfx <Intel-gfx@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@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@ffwll.ch>
> > An: "Nicolas Kalkhof" <nkalkhof@web.de>
> > Cc: intel-gfx <Intel-gfx@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@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@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]

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Nicolas Kalkhof]

> This only contains the pile of WARNINGs and not the Oops itself. I guess
> we still need a picture (and you need to change the system console logging
> to make sure the debug stuff shows up to). At least at the bottom of your
> past there's from drm or i915, indicating that the crucial debug info
> didn't make it out before the machine died.

Ok, I've set CONFIG_MESSAGE_LOGLEVEL_DEFAULT=7 to squeeze some more debug info out of the kernel. For the OOPS I still have to take a picture since kdump seems to be broken for me.

http://pastebin.com/9mxRgNa2

> I just want the decoded address (which I read from the oops, if you
> recompile the kernel it might have changed so please double check). I.e.
> the above two lines is all the howto you need. But please use "list"
> instead of "break" as Chris suggested.

Gotcha!

gdb) list *drm_atomic_helper_check_modeset+0x2c5
0x955 is in drm_atomic_helper_check_modeset (drivers/gpu/drm/drm_atomic_helper.c:235).
230             }
231
232             connector_state->best_encoder = new_encoder;
233             idx = drm_crtc_index(connector_state->crtc);
234
235             crtc_state = state->crtc_states[idx];
236             crtc_state->mode_changed = true;
237
238             DRM_DEBUG_ATOMIC("[CONNECTOR:%d:%s] using [ENCODER:%d:%s] on [CRTC:%d]\n",
239                              connector->base.id,
(gdb)

Address drm_atomic_helper_check_modeset+0x2c5/0x990 is the first line in the call trace.
One more thing: When I fire up X BEFORE I connect to the docking there are no OOPSES and I can switch between DP/eDP. As soon as I kill X however my machine dies.

HTH.

Regards
Nic
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Daniel Vetter]

On Thu, May 21, 2015 at 12:32:18PM +0200, Nicolas Kalkhof wrote:
> > This only contains the pile of WARNINGs and not the Oops itself. I guess
> > we still need a picture (and you need to change the system console logging
> > to make sure the debug stuff shows up to). At least at the bottom of your
> > past there's from drm or i915, indicating that the crucial debug info
> > didn't make it out before the machine died.
> 
> Ok, I've set CONFIG_MESSAGE_LOGLEVEL_DEFAULT=7 to squeeze some more debug info out of the kernel. For the OOPS I still have to take a picture since kdump seems to be broken for me.
> 
> http://pastebin.com/9mxRgNa2
> 
> > I just want the decoded address (which I read from the oops, if you
> > recompile the kernel it might have changed so please double check). I.e.
> > the above two lines is all the howto you need. But please use "list"
> > instead of "break" as Chris suggested.
> 
> Gotcha!
> 
> gdb) list *drm_atomic_helper_check_modeset+0x2c5
> 0x955 is in drm_atomic_helper_check_modeset (drivers/gpu/drm/drm_atomic_helper.c:235).
> 230             }
> 231
> 232             connector_state->best_encoder = new_encoder;
> 233             idx = drm_crtc_index(connector_state->crtc);
> 234
> 235             crtc_state = state->crtc_states[idx];
> 236             crtc_state->mode_changed = true;
> 237
> 238             DRM_DEBUG_ATOMIC("[CONNECTOR:%d:%s] using [ENCODER:%d:%s] on [CRTC:%d]\n",
> 239                              connector->base.id,
> (gdb)
> 
> Address drm_atomic_helper_check_modeset+0x2c5/0x990 is the first line in the call trace.
> One more thing: When I fire up X BEFORE I connect to the docking there are no OOPSES and I can switch between DP/eDP. As soon as I kill X however my machine dies.

Ah, Chris hunch against my claim that this is impossible was spot-on. Can
you please try the below hack please and grab dmesg? Hopefully the kernel
won't die any more at least.
-Daniel
---
diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c
index b82ef6262469..15ba72fb98dd 100644
--- a/drivers/gpu/drm/drm_atomic_helper.c
+++ b/drivers/gpu/drm/drm_atomic_helper.c
@@ -157,6 +157,7 @@ update_connector_routing(struct drm_atomic_state *state, int conn_idx)
 	struct drm_connector *connector;
 	struct drm_connector_state *connector_state;
 	struct drm_crtc_state *crtc_state;
+	struct drm_crtc *saved_crtc;
 	int idx, ret;
 
 	connector = state->connectors[conn_idx];
@@ -195,6 +196,8 @@ update_connector_routing(struct drm_atomic_state *state, int conn_idx)
 		return 0;
 	}
 
+	saved_crtc = connector_state->crtc;
+
 	funcs = connector->helper_private;
 	new_encoder = funcs->best_encoder(connector);
 
@@ -230,7 +233,8 @@ update_connector_routing(struct drm_atomic_state *state, int conn_idx)
 	}
 
 	connector_state->best_encoder = new_encoder;
-	idx = drm_crtc_index(connector_state->crtc);
+	WARN_ON(!connector_state->crtc);
+	idx = drm_crtc_index(saved_crtc);
 
 	crtc_state = state->crtc_states[idx];
 	crtc_state->mode_changed = true;
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Nicolas Kalkhof]

Hi Daniel,
 
> Ah, Chris hunch against my claim that this is impossible was spot-on. Can
> you please try the below hack please and grab dmesg? Hopefully the kernel
> won't die any more at least.

Unfortunately the patch doesn't keep my machine from crashing.

image of stack trace: http://imgur.com/CV5ho1B
dmesg: http://pastebin.com/T69SPT3g

it seems that the problem now occurs in drm_atomic_get_connector_state.

(gdb) list *drm_atomic_get_connector_state+0x40
0xff0 is in drm_atomic_get_connector_state (drivers/gpu/drm/drm_atomic.c:652).
647              *
648              * Note that we only grab the indexes once we have the right lock to
649              * prevent hotplug/unplugging of connectors. So removal is no problem,
650              * at most the array is a bit too large.
651              */
652             if (index >= state->num_connector) {
653                     DRM_DEBUG_ATOMIC("Hot-added connector would overflow state array, restarting\n");
654                     return ERR_PTR(-EAGAIN);
655             }
656
(gdb)   

HTH
Nic
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Daniel Vetter]

On Thu, May 21, 2015 at 04:30:34PM +0200, Nicolas Kalkhof wrote:
> Hi Daniel,
>  
> > Ah, Chris hunch against my claim that this is impossible was spot-on. Can
> > you please try the below hack please and grab dmesg? Hopefully the kernel
> > won't die any more at least.
> 
> Unfortunately the patch doesn't keep my machine from crashing.
> 
> image of stack trace: http://imgur.com/CV5ho1B
> dmesg: http://pastebin.com/T69SPT3g
> 
> it seems that the problem now occurs in drm_atomic_get_connector_state.

Hm something seems to be deeply wrong here. And the oops you've captured
still doesn't include the debug messages before things go boom. Can you
please replace the WARN_ON in my previous patch with a BUG_ON? That should
stop the machine at least and hopefully prevents it all from going boom.

And please play around with dmesg -n to get these debug messages to the
console. I really need them to figure out what's going wrong here.
-Daniel

> 
> (gdb) list *drm_atomic_get_connector_state+0x40
> 0xff0 is in drm_atomic_get_connector_state (drivers/gpu/drm/drm_atomic.c:652).
> 647              *
> 648              * Note that we only grab the indexes once we have the right lock to
> 649              * prevent hotplug/unplugging of connectors. So removal is no problem,
> 650              * at most the array is a bit too large.
> 651              */
> 652             if (index >= state->num_connector) {
> 653                     DRM_DEBUG_ATOMIC("Hot-added connector would overflow state array, restarting\n");
> 654                     return ERR_PTR(-EAGAIN);
> 655             }
> 656
> (gdb)   
> 
> HTH
> Nic

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: still experiencing oops connecting Laptop to docking Station

[Nicolas Kalkhof]

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]


> Hm something seems to be deeply wrong here. And the oops you've captured
> still doesn't include the debug messages before things go boom. Can you
> please replace the WARN_ON in my previous patch with a BUG_ON? That should
> stop the machine at least and hopefully prevents it all from going boom.

I've switched WARN_ON to BUG_ON and in deed it appears right before the oops:

http://imgur.com/eKFSTYB

> And please play around with dmesg -n to get these debug messages to the
> console. I really need them to figure out what's going wrong here.

Please see attached .bz file. This is the max debug output taken from /proc/kmsg right up to the oops. This is everything I got out of it. Maybe I've missed something to get more debug messages to the console other than setting kernel parameters to drm.debug=0xff log_buf_len=10M LOGLEVEL=8 debug and dmesg config dmesg -n 7 and dmesg -n 8. Any hints?

-
Nic

[-- Attachment #2: 4.1-rc4_4.log.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 31744 bytes --]

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx