* Debugging verbosity with mouse pointer movement
@ 2015-11-28 14:57 Greg Stark
2015-11-28 15:53 ` Ville Syrjälä
0 siblings, 1 reply; 3+ messages in thread
From: Greg Stark @ 2015-11-28 14:57 UTC (permalink / raw)
To: intel-gfx
I set set the debugging flag as suggested by the online docs for
reporting GPU hang bugs and I'm seeing the logs fill up with messages.
I didn't think that was surprising but actually poking around it looks
like they don't get lots of messages generally, all the messages are
generated by the mouse pointer moving. IIs it expected that moving the
mouse pointer would generate lots of debugging output? I'm guessing if
that's the only output it's intended that the debugging logs only
generate messages on less common events?
# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.3.0-trunk-amd64 root=/dev/mapper/pixel-root ro
quiet drm.debug=0x1e log_buf_len=1M
These debug logs get generated for every movement of the mouse pointer:
Nov 28 14:51:12 pixel kernel: [ 234.942620]
[drm:drm_atomic_state_init] Allocated atomic state ffff8800a5fc2400
Nov 28 14:51:12 pixel kernel: [ 234.942626]
[drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff88014892edc0
state to ffff8800a5fc2400
Nov 28 14:51:12 pixel kernel: [ 234.942628]
[drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff8800a6fb9c00 state
to ffff8800a5fc2400
Nov 28 14:51:12 pixel kernel: [ 234.942630]
[drm:drm_atomic_set_crtc_for_plane] Link plane state ffff88014892edc0
to [CRTC:21]
Nov 28 14:51:12 pixel kernel: [ 234.942631]
[drm:drm_atomic_set_fb_for_plane] Set [FB:47] for plane state
ffff88014892edc0
Nov 28 14:51:12 pixel kernel: [ 234.942632]
[drm:drm_atomic_check_only] checking ffff8800a5fc2400
Nov 28 14:51:12 pixel kernel: [ 234.942638]
[drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
47
Nov 28 14:51:12 pixel kernel: [ 234.942639]
[drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 0 -> 1, off
0, on 1, ms 0
Nov 28 14:51:12 pixel kernel: [ 234.942640] [drm:drm_atomic_commit]
commiting ffff8800a5fc2400
Nov 28 14:51:12 pixel kernel: [ 234.942662]
[drm:drm_atomic_state_default_clear] Clearing atomic state
ffff8800a5fc2400
Nov 28 14:51:12 pixel kernel: [ 234.942663]
[drm:drm_atomic_state_free] Freeing atomic state ffff8800a5fc2400
Nov 28 14:51:13 pixel kernel: [ 235.217222]
[drm:drm_atomic_state_init] Allocated atomic state ffff880148b49200
Nov 28 14:51:13 pixel kernel: [ 235.217226]
[drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff88009671a280
state to ffff880148b49200
Nov 28 14:51:13 pixel kernel: [ 235.217228]
[drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff880149d5c400 state
to ffff880148b49200
Nov 28 14:51:13 pixel kernel: [ 235.217229]
[drm:drm_atomic_set_crtc_for_plane] Link plane state ffff88009671a280
to [CRTC:21]
Nov 28 14:51:13 pixel kernel: [ 235.217231]
[drm:drm_atomic_set_fb_for_plane] Set [FB:47] for plane state
ffff88009671a280
Nov 28 14:51:13 pixel kernel: [ 235.217232]
[drm:drm_atomic_check_only] checking ffff880148b49200
Nov 28 14:51:13 pixel kernel: [ 235.217237]
[drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
47
Nov 28 14:51:13 pixel kernel: [ 235.217238]
[drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 1 -> 1, off
0, on 0, ms 0
Nov 28 14:51:13 pixel kernel: [ 235.217240] [drm:drm_atomic_commit]
commiting ffff880148b49200
Nov 28 14:51:13 pixel kernel: [ 235.217253]
[drm:drm_atomic_state_default_clear] Clearing atomic state
ffff880148b49200
Nov 28 14:51:13 pixel kernel: [ 235.217255]
[drm:drm_atomic_state_free] Freeing atomic state ffff880148b49200
Nov 28 14:51:13 pixel kernel: [ 235.250970]
[drm:drm_atomic_state_init] Allocated atomic state ffff880148b55000
Nov 28 14:51:13 pixel kernel: [ 235.250973]
[drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff8800a6ce9dc0
state to ffff880148b55000
Nov 28 14:51:13 pixel kernel: [ 235.250975]
[drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff8800a6fb9c00 state
to ffff880148b55000
Nov 28 14:51:13 pixel kernel: [ 235.250976]
[drm:drm_atomic_set_crtc_for_plane] Link plane state ffff8800a6ce9dc0
to [CRTC:21]
Nov 28 14:51:13 pixel kernel: [ 235.250978]
[drm:drm_atomic_set_fb_for_plane] Set [FB:47] for plane state
ffff8800a6ce9dc0
Nov 28 14:51:13 pixel kernel: [ 235.250979]
[drm:drm_atomic_check_only] checking ffff880148b55000
Nov 28 14:51:13 pixel kernel: [ 235.250982]
[drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
47
Nov 28 14:51:13 pixel kernel: [ 235.250984]
[drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 1 -> 1, off
0, on 0, ms 0
Nov 28 14:51:13 pixel kernel: [ 235.250985] [drm:drm_atomic_commit]
commiting ffff880148b55000
Nov 28 14:51:13 pixel kernel: [ 235.250995]
[drm:drm_atomic_state_default_clear] Clearing atomic state
ffff880148b55000
Nov 28 14:51:13 pixel kernel: [ 235.250997]
[drm:drm_atomic_state_free] Freeing atomic state ffff880148b55000
Nov 28 14:51:14 pixel kernel: [ 236.676789]
[drm:drm_atomic_state_init] Allocated atomic state ffff8801494c0600
Nov 28 14:51:14 pixel kernel: [ 236.676794]
[drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff88009671a280
state to ffff8801494c0600
Nov 28 14:51:14 pixel kernel: [ 236.676797]
[drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff88009de0a400 state
to ffff8801494c0600
Nov 28 14:51:14 pixel kernel: [ 236.676799]
[drm:drm_atomic_set_crtc_for_plane] Link plane state ffff88009671a280
to [NOCRTC]
Nov 28 14:51:14 pixel kernel: [ 236.676800]
[drm:drm_atomic_set_fb_for_plane] Set [NOFB] for plane state
ffff88009671a280
Nov 28 14:51:14 pixel kernel: [ 236.676802]
[drm:drm_atomic_check_only] checking ffff8801494c0600
Nov 28 14:51:14 pixel kernel: [ 236.676807]
[drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
-1
Nov 28 14:51:14 pixel kernel: [ 236.676808]
[drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 1 -> 0, off
1, on 0, ms 0
Nov 28 14:51:14 pixel kernel: [ 236.676810] [drm:drm_atomic_commit]
commiting ffff8801494c0600
Nov 28 14:51:14 pixel kernel: [ 236.676830]
[drm:drm_atomic_state_default_clear] Clearing atomic state
ffff8801494c0600
Nov 28 14:51:14 pixel kernel: [ 236.676831]
[drm:drm_atomic_state_free] Freeing atomic state ffff8801494c0600
--
greg
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Debugging verbosity with mouse pointer movement
2015-11-28 14:57 Debugging verbosity with mouse pointer movement Greg Stark
@ 2015-11-28 15:53 ` Ville Syrjälä
2015-11-28 22:46 ` Greg Stark
0 siblings, 1 reply; 3+ messages in thread
From: Ville Syrjälä @ 2015-11-28 15:53 UTC (permalink / raw)
To: Greg Stark; +Cc: intel-gfx
On Sat, Nov 28, 2015 at 02:57:17PM +0000, Greg Stark wrote:
> I set set the debugging flag as suggested by the online docs for
> reporting GPU hang bugs and I'm seeing the logs fill up with messages.
> I didn't think that was surprising but actually poking around it looks
> like they don't get lots of messages generally, all the messages are
> generated by the mouse pointer moving. IIs it expected that moving the
> mouse pointer would generate lots of debugging output? I'm guessing if
> that's the only output it's intended that the debugging logs only
> generate messages on less common events?
Use drm.debug=0xe unless you really want to debug the atomic code (which
is where all this spew comes from).
>
> # cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-4.3.0-trunk-amd64 root=/dev/mapper/pixel-root ro
> quiet drm.debug=0x1e log_buf_len=1M
>
> These debug logs get generated for every movement of the mouse pointer:
>
> Nov 28 14:51:12 pixel kernel: [ 234.942620]
> [drm:drm_atomic_state_init] Allocated atomic state ffff8800a5fc2400
> Nov 28 14:51:12 pixel kernel: [ 234.942626]
> [drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff88014892edc0
> state to ffff8800a5fc2400
> Nov 28 14:51:12 pixel kernel: [ 234.942628]
> [drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff8800a6fb9c00 state
> to ffff8800a5fc2400
> Nov 28 14:51:12 pixel kernel: [ 234.942630]
> [drm:drm_atomic_set_crtc_for_plane] Link plane state ffff88014892edc0
> to [CRTC:21]
> Nov 28 14:51:12 pixel kernel: [ 234.942631]
> [drm:drm_atomic_set_fb_for_plane] Set [FB:47] for plane state
> ffff88014892edc0
> Nov 28 14:51:12 pixel kernel: [ 234.942632]
> [drm:drm_atomic_check_only] checking ffff8800a5fc2400
> Nov 28 14:51:12 pixel kernel: [ 234.942638]
> [drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
> 47
> Nov 28 14:51:12 pixel kernel: [ 234.942639]
> [drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 0 -> 1, off
> 0, on 1, ms 0
> Nov 28 14:51:12 pixel kernel: [ 234.942640] [drm:drm_atomic_commit]
> commiting ffff8800a5fc2400
> Nov 28 14:51:12 pixel kernel: [ 234.942662]
> [drm:drm_atomic_state_default_clear] Clearing atomic state
> ffff8800a5fc2400
> Nov 28 14:51:12 pixel kernel: [ 234.942663]
> [drm:drm_atomic_state_free] Freeing atomic state ffff8800a5fc2400
>
> Nov 28 14:51:13 pixel kernel: [ 235.217222]
> [drm:drm_atomic_state_init] Allocated atomic state ffff880148b49200
> Nov 28 14:51:13 pixel kernel: [ 235.217226]
> [drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff88009671a280
> state to ffff880148b49200
> Nov 28 14:51:13 pixel kernel: [ 235.217228]
> [drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff880149d5c400 state
> to ffff880148b49200
> Nov 28 14:51:13 pixel kernel: [ 235.217229]
> [drm:drm_atomic_set_crtc_for_plane] Link plane state ffff88009671a280
> to [CRTC:21]
> Nov 28 14:51:13 pixel kernel: [ 235.217231]
> [drm:drm_atomic_set_fb_for_plane] Set [FB:47] for plane state
> ffff88009671a280
> Nov 28 14:51:13 pixel kernel: [ 235.217232]
> [drm:drm_atomic_check_only] checking ffff880148b49200
> Nov 28 14:51:13 pixel kernel: [ 235.217237]
> [drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
> 47
> Nov 28 14:51:13 pixel kernel: [ 235.217238]
> [drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 1 -> 1, off
> 0, on 0, ms 0
> Nov 28 14:51:13 pixel kernel: [ 235.217240] [drm:drm_atomic_commit]
> commiting ffff880148b49200
> Nov 28 14:51:13 pixel kernel: [ 235.217253]
> [drm:drm_atomic_state_default_clear] Clearing atomic state
> ffff880148b49200
> Nov 28 14:51:13 pixel kernel: [ 235.217255]
> [drm:drm_atomic_state_free] Freeing atomic state ffff880148b49200
>
> Nov 28 14:51:13 pixel kernel: [ 235.250970]
> [drm:drm_atomic_state_init] Allocated atomic state ffff880148b55000
> Nov 28 14:51:13 pixel kernel: [ 235.250973]
> [drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff8800a6ce9dc0
> state to ffff880148b55000
> Nov 28 14:51:13 pixel kernel: [ 235.250975]
> [drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff8800a6fb9c00 state
> to ffff880148b55000
> Nov 28 14:51:13 pixel kernel: [ 235.250976]
> [drm:drm_atomic_set_crtc_for_plane] Link plane state ffff8800a6ce9dc0
> to [CRTC:21]
> Nov 28 14:51:13 pixel kernel: [ 235.250978]
> [drm:drm_atomic_set_fb_for_plane] Set [FB:47] for plane state
> ffff8800a6ce9dc0
> Nov 28 14:51:13 pixel kernel: [ 235.250979]
> [drm:drm_atomic_check_only] checking ffff880148b55000
> Nov 28 14:51:13 pixel kernel: [ 235.250982]
> [drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
> 47
> Nov 28 14:51:13 pixel kernel: [ 235.250984]
> [drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 1 -> 1, off
> 0, on 0, ms 0
> Nov 28 14:51:13 pixel kernel: [ 235.250985] [drm:drm_atomic_commit]
> commiting ffff880148b55000
> Nov 28 14:51:13 pixel kernel: [ 235.250995]
> [drm:drm_atomic_state_default_clear] Clearing atomic state
> ffff880148b55000
> Nov 28 14:51:13 pixel kernel: [ 235.250997]
> [drm:drm_atomic_state_free] Freeing atomic state ffff880148b55000
>
> Nov 28 14:51:14 pixel kernel: [ 236.676789]
> [drm:drm_atomic_state_init] Allocated atomic state ffff8801494c0600
> Nov 28 14:51:14 pixel kernel: [ 236.676794]
> [drm:drm_atomic_get_plane_state] Added [PLANE:20] ffff88009671a280
> state to ffff8801494c0600
> Nov 28 14:51:14 pixel kernel: [ 236.676797]
> [drm:drm_atomic_get_crtc_state] Added [CRTC:21] ffff88009de0a400 state
> to ffff8801494c0600
> Nov 28 14:51:14 pixel kernel: [ 236.676799]
> [drm:drm_atomic_set_crtc_for_plane] Link plane state ffff88009671a280
> to [NOCRTC]
> Nov 28 14:51:14 pixel kernel: [ 236.676800]
> [drm:drm_atomic_set_fb_for_plane] Set [NOFB] for plane state
> ffff88009671a280
> Nov 28 14:51:14 pixel kernel: [ 236.676802]
> [drm:drm_atomic_check_only] checking ffff8801494c0600
> Nov 28 14:51:14 pixel kernel: [ 236.676807]
> [drm:intel_plane_atomic_calc_changes] [CRTC:21] has [PLANE:20] with fb
> -1
> Nov 28 14:51:14 pixel kernel: [ 236.676808]
> [drm:intel_plane_atomic_calc_changes] [PLANE:20] visible 1 -> 0, off
> 1, on 0, ms 0
> Nov 28 14:51:14 pixel kernel: [ 236.676810] [drm:drm_atomic_commit]
> commiting ffff8801494c0600
> Nov 28 14:51:14 pixel kernel: [ 236.676830]
> [drm:drm_atomic_state_default_clear] Clearing atomic state
> ffff8801494c0600
> Nov 28 14:51:14 pixel kernel: [ 236.676831]
> [drm:drm_atomic_state_free] Freeing atomic state ffff8801494c0600
>
> --
> greg
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Debugging verbosity with mouse pointer movement
2015-11-28 15:53 ` Ville Syrjälä
@ 2015-11-28 22:46 ` Greg Stark
0 siblings, 0 replies; 3+ messages in thread
From: Greg Stark @ 2015-11-28 22:46 UTC (permalink / raw)
To: Ville Syrjälä; +Cc: intel-gfx
On Sat, Nov 28, 2015 at 3:53 PM, Ville Syrjälä
<ville.syrjala@linux.intel.com> wrote:
> Use drm.debug=0xe unless you really want to debug the atomic code (which
> is where all this spew comes from).
Thanks.
I'm trying to get debug info to report the freezes that still happen
on my Chromebook Pixel even after the fix that apparently fixed the
problem for everyone else. But I just got one and there was nothing in
/sys/class/drm/card0/error and excluding these atomic log entries
nothing interesting in the kernel log. I wonder if there's any other
debug messages I should enable.
I also wonder whether root cause of the problem isn't elsewhere than
the graphics card, though it obviously affects the graphics card. Are
there any generic PCI or kernel interrupt handling debugging I should
enable to report this usefully?
--
greg
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-11-28 22:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-28 14:57 Debugging verbosity with mouse pointer movement Greg Stark
2015-11-28 15:53 ` Ville Syrjälä
2015-11-28 22:46 ` Greg Stark
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.