[Intel-gfx] [REGRESSION] Occasional Flickering with Linux 4.6.0-rc* on Scree connected to eDP
Hi, with 4.6.0-rc4 and -rc6 kernel I experience occasional (every 1-2 Minutes) on my laptop (thinkpad t440s) screen. This flickering has not been there in 4.5. Unfortunately the laptop does not boot with 4.6-rc1. The laptop screen is connected via eDP. I have two other monitors connected to the dock, conected via DP. They do not show the flickering. There is nothing in the log when the flickering occurs (drm.debug=14). Compared to 4.5.0 I see the following message with 4.6.0 after bootup: [ 5921.720651] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. I tried to increase graphics memory in bios, however, this did not seem to have any effect. Any idea how to track this down? I'm happy to provide more info. Best Regards Arnd ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [REGRESSION] Occasional Flickering with Linux 4.6.0-rc* on Scree connected to eDP
Hi, probably a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=95124 Sorry for the noise. Best regards Arnd Am 04.05.2016 um 11:45 schrieb Arnd Hannemann: > Hi, > > with 4.6.0-rc4 and -rc6 kernel I experience occasional (every 1-2 Minutes) > on my laptop (thinkpad t440s) screen. > This flickering has not been there in 4.5. > Unfortunately the laptop does not boot with 4.6-rc1. > > The laptop screen is connected via eDP. I have two other monitors connected > to the dock, > conected via DP. They do not show the flickering. > There is nothing in the log when the flickering occurs (drm.debug=14). > > Compared to 4.5.0 I see the following message with 4.6.0 after bootup: > > [ 5921.720651] [drm] Reducing the compressed framebuffer size. This may lead > to less power savings than a non-reduced-size. Try to increase stolen memory > size if available in BIOS. > > I tried to increase graphics memory in bios, however, this did not seem to > have any effect. > > Any idea how to track this down? I'm happy to provide more info. > > Best Regards > Arnd > ___ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] 3.11.0-rc5: WARNING: at drivers/gpu/drm/i915/intel_display.c:8286 check_crtc_state
Hi, when changing the refresh rate of my laptop display with xrandr on 3.11.0-rc5, like: xrandr --output LVDS1 --rate 59.9 --mode 1920x1080 The following WARNING is generated: [ 50.018055] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags (expected 1, found 0) [ 50.018060] [ cut here ] [ 50.018105] WARNING: CPU: 0 PID: 1819 at /home/arnd/Projekte/kernel/linux-2.6/drivers/gpu/drm/i915/intel_display.c:8286 check_crtc_state+0x59f/0xa30 [i915]() [ 50.018106] pipe state doesn't match! [ 50.018107] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables joydev deflate ctr twofish_generic twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_x86_64 bridge stp llc serpent_sse2_x86_64 serpent_generic ablk_helper cryptd xts lrw gf128mul glue_helper blowfish_generic blowfish_x86_64 blowfish_common cast5_generic cast_common des_generic cmac xcbc rmd160 sha512_generic dm_crypt crypto_null af_key xfrm_algo arc4 iwldvm mac80211 snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep snd_pcm dm_multipath snd_page_alloc snd_seq_midi snd_seq_midi_event uvcvideo videobuf2_vmalloc thinkpad_acpi videobuf2_memops snd_rawmidi videobuf2_core nvram videodev media snd_seq snd_seq_device snd_timer psmouse se rio_raw q cserial usb_wwan usbserial intel_ips tpm_tis snd btusb bnep iwlwifi lpc_ich rfcomm bluetooth cfg80211 soundcore binfmt_misc btrfs xor zlib_deflate raid6_pq libcrc32c mmc_block mxm_wmi firewire_ohci firewire_core crc_itu_t wmi i915 video i2c_algo_bit drm_kms_helper drm e1000e sdhci_pci ptp sdhci ahci pps_core libahci [ 50.018156] CPU: 0 PID: 1819 Comm: Xorg Not tainted 3.11.0-rc5aha+ #3 [ 50.018157] Hardware name: LENOVO 4384GEG/4384GEG, BIOS 6MET86WW (1.46 ) 05/24/2011 [ 50.018159] 0009 880223b39870 81633b7d 880223b398b8 [ 50.018160] 880223b398a8 8104a69c 8802322fc6d0 0001 [ 50.018162] 88022d99d000 8802322fc000 88022d99d478 880223b39908 [ 50.018164] Call Trace: [ 50.018172] [] dump_stack+0x45/0x56 [ 50.018177] [] warn_slowpath_common+0x8c/0xc0 [ 50.018178] [] warn_slowpath_fmt+0x4c/0x50 [ 50.018191] [] check_crtc_state+0x59f/0xa30 [i915] [ 50.018204] [] intel_modeset_check_state+0x2cd/0x750 [i915] [ 50.018215] [] intel_set_mode+0x25/0x30 [i915] [ 50.018225] [] intel_crtc_set_config+0x7b2/0x990 [i915] [ 50.018241] [] drm_mode_set_config_internal+0x5d/0xe0 [drm] [ 50.018250] [] drm_mode_setcrtc+0xfb/0x620 [drm] [ 50.018260] [] ? intel_crtc_load_lut+0xd2/0x190 [i915] [ 50.018267] [] drm_ioctl+0x539/0x670 [drm] [ 50.018276] [] ? drm_mode_setplane+0x3b0/0x3b0 [drm] [ 50.018282] [] do_vfs_ioctl+0x8c/0x4f0 [ 50.018284] [] ? __sb_end_write+0x31/0x60 [ 50.018286] [] ? vfs_write+0x17e/0x1e0 [ 50.018288] [] SyS_ioctl+0x91/0xb0 [ 50.018291] [] system_call_fastpath+0x16/0x1b [ 50.018293] ---[ end trace d0d4c4e12439b0ce ]--- This is pretty reproducable on a newly booted system, and already present since -rc1 or such. The update of the refresh rate seems to work nevertheless, though. Best regards Arnd ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] 3.18.0-rc3: i915: eDP connected Display stays blank
Hi, I have a Thinkpad T440s (Haswell) connected to two additional Monitors via a Docking Station (MST). During Bootup all three displays work, even when X is started. However, if the laptop display is turned off once (either because of power saving, or via xrandr), it fails to "come back". That is if I try to re-enable it the Display stays blank. I believe this used to work in 3.17. Here is the xrandr Ouput of the edp, when its enabled (but staying blank): Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767 eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 175mm 1920x1080 60.0*+ 59.9 here is the debug output, while trying to enable it: [ 416.314290] [drm:drm_mode_setcrtc] [CONNECTOR:19:eDP-1] [ 416.314294] [drm:intel_crtc_set_config] [CRTC:12] [FB:149] #connectors=1 (x y) (0 0) [ 416.314299] [drm:intel_set_config_compute_mode_changes] inactive crtc, full mode set [ 416.314303] [drm:intel_set_config_compute_mode_changes] computed changes for [CRTC:12], mode_changed=1, fb_changed=1 [ 416.314305] [drm:intel_modeset_stage_output_state] encoder changed, full mode switch [ 416.314309] [drm:intel_modeset_stage_output_state] [CONNECTOR:19:eDP-1] to [CRTC:12] [ 416.314312] [drm:intel_modeset_stage_output_state] [CONNECTOR:39:DP-3] to [CRTC:8] [ 416.314315] [drm:intel_modeset_stage_output_state] [CONNECTOR:43:DP-4] to [CRTC:16] [ 416.314317] [drm:intel_modeset_stage_output_state] crtc changed, full mode switch [ 416.314321] [drm:intel_modeset_stage_output_state] crtc enabled, full mode switch [ 416.314325] [drm:intel_modeset_affected_pipes] set mode pipe masks: modeset: 2, prepare: 2, disable: 0 [ 416.314329] [drm:connected_sink_compute_bpp] [CONNECTOR:19:eDP-1] checking for sink bpp constrains [ 416.314332] [drm:connected_sink_compute_bpp] clamping display bpp (was 24) to EDID reported max of 18 [ 416.314337] [drm:intel_dp_compute_config] DP link computation with max lane count 2 max bw 0a pixel clock 140100KHz [ 416.314341] [drm:intel_dp_compute_config] DP link bw 0a lane count 2 clock 27 bpp 18 [ 416.314343] [drm:intel_dp_compute_config] DP link bw required 252180 available 432000 [ 416.314347] [drm:intel_modeset_pipe_config] plane bpp: 24, pipe bpp: 18, dithering: 1 [ 416.314351] [drm:intel_dump_pipe_config] [CRTC:12][modeset] config for pipe B [ 416.314353] [drm:intel_dump_pipe_config] cpu_transcoder: D [ 416.314355] [drm:intel_dump_pipe_config] pipe bpp: 18, dithering: 1 [ 416.314359] [drm:intel_dump_pipe_config] fdi/pch: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0 [ 416.314363] [drm:intel_dump_pipe_config] dp: 1, gmch_m: 4896849, gmch_n: 8388608, link_m: 272047, link_n: 524288, tu: 64 [ 416.314392] [drm:intel_dump_pipe_config] dp: 1, gmch_m2: 0, gmch_n2: 0, link_m2: 0, link_n2: 0, tu2: 0 [ 416.314406] [drm:intel_dump_pipe_config] requested mode: [ 416.314422] [drm:drm_mode_debug_printmodeline] Modeline 0:"" 0 140100 1920 1980 2016 2092 1080 1083 1088 1116 0x0 0x9 [ 416.314435] [drm:intel_dump_pipe_config] adjusted mode: [ 416.314453] [drm:drm_mode_debug_printmodeline] Modeline 0:"1920x1080" 60 140100 1920 1980 2016 2092 1080 1083 1088 1116 0x48 0x9 [ 416.314468] [drm:intel_dump_crtc_timings] crtc timings: 140100 1920 1980 2016 2092 1080 1083 1088 1116, type: 0x48 flags: 0x9 [ 416.314482] [drm:intel_dump_pipe_config] port clock: 27 [ 416.314496] [drm:intel_dump_pipe_config] pipe src size: 1920x1080 [ 416.314510] [drm:intel_dump_pipe_config] gmch pfit: control: 0x, ratios: 0x, lvds border: 0x [ 416.314521] [drm:intel_dump_pipe_config] pch pfit: pos: 0x, size: 0x, disabled [ 416.314524] [drm:intel_dump_pipe_config] ips: 0 [ 416.314527] [drm:intel_dump_pipe_config] double wide: 0 [ 416.314568] [drm:intel_edp_panel_on] Turn eDP power on [ 416.314575] [drm:wait_panel_power_cycle] Wait for panel power cycle [ 416.314585] [drm:wait_panel_status] mask b80f value status control abcd0008 [ 416.314591] [drm:wait_panel_status] Wait complete [ 416.314599] [drm:wait_panel_on] Wait for panel power on [ 416.314606] [drm:wait_panel_status] mask b00f value 8008 status 000a control abcd000b [ 416.522545] [drm:wait_panel_status] Wait complete [ 416.523689] [drm:intel_dp_set_signal_levels] Using signal levels [ 416.524311] [drm:intel_dp_start_link_train] clock recovery OK [ 416.525224] [drm:intel_dp_complete_link_train] Channel EQ done. DP Training successful [ 416.525528] [drm:intel_edp_backlight_on] [ 416.525533] [drm:intel_panel_enable_backlight] pipe B [ 416.525541] [drm:intel_panel_actually_set_backlight] set backlight PWM = 10 [ 416.530518] [drm:intel_edp_psr_match_conditions] PSR disable by flag [ 416.538553] [drm:ironlake_update_primary_plane] Writing base 030B 0 0 15360 [ 416.538575] [drm:intel_connector_check_state] [CONNECTOR:19:eDP-1] [ 416.538584] [drm:intel
Re: [Intel-gfx] 3.18.0-rc3: i915: eDP connected Display stays blank
Hi, thanks for your quick response. Am 06.11.2014 um 10:39 schrieb Jani Nikula: > On Thu, 06 Nov 2014, Arnd Hannemann wrote: >> Hi, >> >> I have a Thinkpad T440s (Haswell) connected to two additional Monitors >> via a Docking Station (MST). >> >> During Bootup all three displays work, even when X is started. >> However, if the laptop display is turned off once (either because of >> power saving, or via xrandr), it fails to "come back". >> That is if I try to re-enable it the Display stays blank. >> I believe this used to work in 3.17. >> >> Here is the xrandr Ouput of the edp, when its enabled (but staying blank): >> Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767 >> eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) >> 309mm x 175mm >>1920x1080 60.0*+ 59.9 >> >> here is the debug output, while trying to enable it: >> > > ... > >> [ 416.538848] [drm:intel_edp_backlight_power] panel power control backlight >> disable >> >> >> I'm happy to provide further input. > > What does cat /sys/class/backlight/intel_backlight/bl_power say? What if root@kallisto:~# cat /sys/class/backlight/intel_backlight/bl_power 1 > you echo 0 there? :-) Works my display comes back, when I echo 0 there. Is user-space doing something wrong here? Best regards Arnd ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] 3.18.0-rc3: i915: eDP connected Display stays blank
Hi, Am 06.11.2014 um 13:53 schrieb Jani Nikula: >> root@kallisto:~# cat /sys/class/backlight/intel_backlight/bl_power >> 1 >> >>> you echo 0 there? >> >> :-) Works my display comes back, when I echo 0 there. >> >> Is user-space doing something wrong here? > > If the userspace wishes to switch off backlight, then it's doing nothing > wrong at all! ;) > > Here's the story as I know it. > > Once upon a time someone added the bl_power attribute to the sysfs class > backlight interface. Even though the name implies a boolean backlight > power, the values are in fact FB_BLANK_* from fb.h, and power on is > FB_BLANK_UNBLANK, or 0. All the other values are various levels of > blanking which make little sense to backlight, and thus any non-zero > values mean power off. [1] > > Until recently, intel_backlight of drm/i915 did not support bl_power at > all. We ignored the attribute altogether. However changing bl_power from > its default 0 did cause a backlight update hook to be called. In some > edge cases doing this fixed some backlight issues by reprogramming the > backlight intensity, and probably lead to the false assumption that > bl_power needed to be set to 1 to enable power. > > Now that we've enabled support for bl_power attribute (on eDP at least), > the previously harmless, or sometimes even helpful, bl_power=1 actually > does what it means. That is, switch off the backlight. > Thanks for your elaborated answer. > Please try this patch (untested) to find out the culprit. Thanks, its the intel xorg driver: [ 255.98] bl_power 1 by Xorg I seems it was already corrected upstream, by Chris Wilson two days ago: http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=7ecc778691c452285f754743a93a46fa1d3da52f Best regards Arnd ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
