Bug #1308674 “[Lenovo ThinkPad X220] kernel 3.13 i915 brightness...” : Bugs : linux package : Ubuntu

Revision history for this message

In Red Hat Bugzilla #1067071, Kamil (kamil-redhat-bugs) wrote on 2014-02-19:

#26

Created attachment 865143
journal snippet

Description of problem:
If this happens:
1. You power on the notebook inside the docking station.
2. You log in.
3. You dock out the notebook.

Then your brightness is set to minimum (the screen is nearly unreadable) and the brightness control is broken - you can't adjust the brightness.

When you dock the notebook back in, the brightness is restored to the normal level and you can control it.

If you start your notebook outside of the docking station, this bug is not experienced at all (even if you dock in and dock out, everything works).

This is a regression with kernel-3.13.2-200.fc20.x86_64 , if I boot
kernel-3.12.9-301.fc20.x86_64 then everything works OK.

I have this confirmed on Thinkpad X220:
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

and also on Thinkpad T520. I guess both use Intel HD 3000?

I don't see anything useful in the logs. I attach journal snippet when I undock the notebook. You can see brightness-related systemd printouts, that's when I try to change the brightness (or some of that happens automatically during docking out).

Version-Release number of selected component (if applicable):
kernel-3.13.2-200.fc20.x86_64

How reproducible:
100%

Steps to Reproduce:
1. power on the notebook inside the docking station
2. log in
3. dock out the notebook

Actual results:
your brightness is set to minimum (the screen is nearly unreadable) and the brightness control is broken - you can't adjust the brightness

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-02-19:

#27

Do you have an external monitor attached to the dock? If so, how do you have the screens configured when docked?

Which brightness controls are you using? The hardware keys or the software slider?

If you use the hardware keys, does the OSD show any changes after you undock but those changes are not reflected in actual brightness adjustment?

If you adjust the brightness in any manner, do the values of brightness/actual_brightness in /sys/class/backlight/acpi_video0 and/or /sys/class/backlight/intel_backlight change? If so, which is changed on 3.12 and which is changed on 3.13?

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-02-19:

#28

Could you also try the 3.14.0-0.rc3.git0.1.fc21.x86_64 build and see if that fixes the controls for you? I have similar hardware and can recreate your issue, and I think 3.14-rc3 seems to work again but I'd like you to confirm.

Revision history for this message

In Red Hat Bugzilla #1067071, Kamil (kamil-redhat-bugs) wrote on 2014-02-20:

#29

(In reply to Josh Boyer from comment #1)
> Do you have an external monitor attached to the dock?

Yes.

> If so, how do you
> have the screens configured when docked?

$ xrandr
Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 8192 x 8192
LVDS1 connected 1366x768+0+128 (normal left inverted right x axis y axis) 277mm x 156mm
   1366x768 60.1*+
   1024x768 60.0
   800x600 60.3 56.2
   640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 connected primary 1920x1080+1366+0 (normal left inverted right x axis y axis) 510mm x 290mm
   1920x1080 60.0*+
   1680x1050 59.9
   1280x1024 60.0
   1280x960 60.0
   1152x864 60.0
   1024x768 60.0
   800x600 60.3
   640x480 60.0
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)

>
> Which brightness controls are you using? The hardware keys or the software
> slider?

Neither of them work.

>
> If you use the hardware keys, does the OSD show any changes after you undock
> but those changes are not reflected in actual brightness adjustment?

Exactly. OSD indicates changes, but the actual brightness is not changed.

>
> If you adjust the brightness in any manner, do the values of
> brightness/actual_brightness in /sys/class/backlight/acpi_video0 and/or
> /sys/class/backlight/intel_backlight change? If so, which is changed on
> 3.12 and which is changed on 3.13?

On 3.12, the {acpi_video0,intel_backlight}/{actual_,}brightness attribute changes value according to my changes. On 3.13 acpi_video0/{actual_,}brightness value changes as well, but intel_backlight}/{actual_,}brightness value is stuck to 44 (out of 3000 max) and doesn't change at all.

(In reply to Josh Boyer from comment #2)
> Could you also try the 3.14.0-0.rc3.git0.1.fc21.x86_64 build and see if that
> fixes the controls for you? I have similar hardware and can recreate your
> issue, and I think 3.14-rc3 seems to work again but I'd like you to confirm.

I tested kernel-3.14.0-0.rc3.git2.1.fc21.x86_64 and it seems to be fixed there. It's a bit different build, let me know if I should retest exactly the one you suggested.

(In reply to Josh Boyer from comment #1)
> Do you have an external monitor attached to the dock?

Yes.

>  If so, how do you
> have the screens configured when docked?

$ xrandr
Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 8192 x 8192
LVDS1 connected 1366x768+0+128 (normal left inverted right x axis y axis) 277mm x 156mm
   1366x768       60.1*+
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        59.9  
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 connected primary 1920x1080+1366+0 (normal left inverted right x axis y axis) 510mm x 290mm
   1920x1080      60.0*+
   1680x1050      59.9  
   1280x1024      60.0  
   1280x960       60.0  
   1152x864       60.0  
   1024x768       60.0  
   800x600        60.3  
   640x480        60.0  
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)

> 
> Which brightness controls are you using?  The hardware keys or the software
> slider?

Neither of them work.

> 
> If you use the hardware keys, does the OSD show any changes after you undock
> but those changes are not reflected in actual brightness adjustment?

Exactly. OSD indicates changes, but the actual brightness is not changed.

> 
> If you adjust the brightness in any manner, do the values of
> brightness/actual_brightness in /sys/class/backlight/acpi_video0 and/or
> /sys/class/backlight/intel_backlight change?  If so, which is changed on
> 3.12 and which is changed on 3.13?

On 3.12, the {acpi_video0,intel_backlight}/{actual_,}brightness attribute changes value according to my changes. On 3.13 acpi_video0/{actual_,}brightness value changes as well, but intel_backlight}/{actual_,}brightness value is stuck to 44 (out of 3000 max) and doesn't change at all.

(In reply to Josh Boyer from comment #2)
> Could you also try the 3.14.0-0.rc3.git0.1.fc21.x86_64 build and see if that
> fixes the controls for you?  I have similar hardware and can recreate your
> issue, and I think 3.14-rc3 seems to work again but I'd like you to confirm.

I tested kernel-3.14.0-0.rc3.git2.1.fc21.x86_64 and it seems to be fixed there. It's a bit different build, let me know if I should retest exactly the one you suggested.

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-02-20:

#30

No, the kernel you tested is fine. I have no idea what fixed it in the newer kernels yet, but it happened after the DRM merge. A reverse bisect I've been working on has proven utterly unhelpful.

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-02-21:

#31

Can you please test this scratch kernel when it finishes building: http://koji.fedoraproject.org/koji/taskinfo?taskID=6557799 It works locally, but I'd like confirmation before I follow up with upstream.

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-02-24:

#32

Hello?

Revision history for this message

In Red Hat Bugzilla #1067071, Kamil (kamil-redhat-bugs) wrote on 2014-02-25:

#33

Vacation. Problem is fixed in comment 5, thanks.

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-03-04:

#34

Upstream reviewed the patch to fix this and said it wasn't technically correct. Doing the correct fix is a bit more invasive of a backport than is really suitable it seems. We're likely going to have to wait for a 3.14 rebase to fix this bug.

Revision history for this message

In Red Hat Bugzilla #1067071, Kamil (kamil-redhat-bugs) wrote on 2014-03-05:

#35

Just to clarify, I've found out that this problem is also triggered by disconnecting an external display. Therefore undocking is probably not the root cause (there is an external display connected to my dock), disconnecting from an external display is.

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-03-05:

#36

Thanks. That actually makes sense with the upstream diagnosis still.

Revision history for this message

In Red Hat Bugzilla #1067071, Matthias (matthias-redhat-bugs) wrote on 2014-03-06:

#37

I see the following stacktrace after suspending/resuming and undocking:

[74755.531008] Hardware name: LENOVO 4243BQ9/4243BQ9, BIOS 8AET56WW (1.36 ) 12/06/2011
[74755.531010] 0000000000000009 ffff8800ca74dbd0 ffffffff81686fdc ffff8800ca74dc18
[74755.531015] ffff8800ca74dc08 ffffffff8106d47d ffff880036ce8000 0000000000070008
[74755.531018] 00000001046fce31 0000000000000000 ffff88021029a320 ffff8800ca74dc68
[74755.531022] Call Trace:
[74755.531033] [<ffffffff81686fdc>] dump_stack+0x45/0x56
[74755.531040] [<ffffffff8106d47d>] warn_slowpath_common+0x7d/0xa0
[74755.531045] [<ffffffff8106d4ec>] warn_slowpath_fmt+0x4c/0x50
[74755.531071] [<ffffffffa00cc2cb>] intel_wait_for_pipe_off+0x1db/0x1f0 [i915]
[74755.531093] [<ffffffffa00cc380>] intel_disable_pipe+0xa0/0xb0 [i915]
[74755.531114] [<ffffffffa00cd454>] ironlake_crtc_disable+0xe4/0x940 [i915]
[74755.531135] [<ffffffffa00d3abf>] intel_crtc_update_dpms+0x6f/0xa0 [i915]
[74755.531157] [<ffffffffa00d7429>] intel_connector_dpms+0x59/0x70 [i915]
[74755.531180] [<ffffffffa003b3f8>] drm_mode_obj_set_property_ioctl+0x328/0x340 [drm]
[74755.531199] [<ffffffffa003b440>] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
[74755.531214] [<ffffffffa002ab52>] drm_ioctl+0x502/0x630 [drm]
[74755.531226] [<ffffffff8119d2bf>] ? kfree+0xff/0x130
[74755.531231] [<ffffffff81321b50>] ? lockref_put_or_lock+0x50/0x80
[74755.531236] [<ffffffff811cb6d8>] do_vfs_ioctl+0x2d8/0x4a0
[74755.531241] [<ffffffff811ba77e>] ? ____fput+0xe/0x10
[74755.531244] [<ffffffff811cb921>] SyS_ioctl+0x81/0xa0
[74755.531250] [<ffffffff81695fa9>] system_call_fastpath+0x16/0x1b
[74755.531253] ---[ end trace cd788d6e38c5424a ]---
[74755.582844] [drm:ironlake_disable_pch_transcoder] *ERROR* failed to disable transcoder A

This clearly worked with 3.12

Revision history for this message

In Red Hat Bugzilla #1067071, Kamil (kamil-redhat-bugs) wrote on 2014-03-17:

#38

When working with external displays, it seems that:
a) every odd display disconnect leaves you with broken (minimal, nonadjustable) brightness
b) every even display disconnect seems to work properly (brightness can be adjusted)

I haven't tested this with docking station, but it's likely that it could work the same way. This might be at least some workaround, until this is fixed. Simply disconnect the display twice.

Revision history for this message

Ursula Junque (ursinha) wrote on 2014-04-16:

#1

AlsaInfo.txt Edit (62.2 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (102.7 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (123.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (583 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (11.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (764 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (316 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.1 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (29.0 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (182 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (153.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (326.7 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (1.2 MiB, text/plain; charset="utf-8")

Ursula Junque (ursinha) on 2014-04-16

description:

updated

Revision history for this message

Brad Figg (brad-figg) wrote on 2014-04-16: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-04-16: Re: On a X220, kernel 3.13 i915 brightness settings broken when going from docked -> undocked

#3

Hi Ursula,

Can you test the 3.14 -final upstream kernel, to confirm it fixes this bug? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
tags:	added: kernel-da-key
Changed in linux (Ubuntu):
status:	Confirmed → Triaged

penalvch (penalvch) on 2014-04-19

tags:	added: bios-outdated-1.39
Changed in linux:
importance:	Unknown → Undecided
status:	Unknown → New
Changed in linux (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

In Red Hat Bugzilla #1067071, Josh (josh-redhat-bugs) wrote on 2014-04-24:

#39

3.14.1 is in updates-testing now.

penalvch (penalvch) on 2014-04-28

summary:

- On a X220, kernel 3.13 i915 brightness settings broken when going from
- docked -> undocked
+ [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when
+ going from docked -> undocked

Revision history for this message

In Red Hat Bugzilla #1067071, Fedora (fedora-redhat-bugs) wrote on 2014-04-28:

#40

kernel-3.14.2-200.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/kernel-3.14.2-200.fc20

Revision history for this message

In Red Hat Bugzilla #1067071, Fedora (fedora-redhat-bugs) wrote on 2014-04-30:

#41

Package kernel-3.14.2-200.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.14.2-200.fc20'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-5808/kernel-3.14.2-200.fc20
then log in and leave karma (feedback).

Revision history for this message

In Red Hat Bugzilla #1067071, Fedora (fedora-redhat-bugs) wrote on 2014-05-01:

#42

kernel-3.14.2-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message

In Red Hat Bugzilla #1067071, Christopher (christopher-redhat-bugs) wrote on 2014-05-02:

#43

Unfortunately, this "Fix" (kernel-3.14.2-200.fc20) actually breaks the brightness control outright for me on an Intel GM965 (Core 2 Duo) on a Dell Inspiron 1420. Since this update, the brightness is stuck at the lowest possible setting. Neither the graphical slider nor the hardware Fn+Up/Down keys have any effect.

Revision history for this message

In Red Hat Bugzilla #1067071, Karolis (karolis-redhat-bugs) wrote on 2014-05-05:

#44

I never had an issue described in the original report (or just didn't notice), but just like in Christopher Tubbs' case (Comment 17), after upgrading to kernel-3.14.2-200.fc20 my brightess is messed up - always at the lowest possible setting and there's no way to increase it via xrandr or xbacklightset.

Do we need to report a separate bug? What information can I provide to help fixing this issue?

I'm using Dell XPS m1330 with Intel® 965GM graphics.

Revision history for this message

In Red Hat Bugzilla #1067071, Soeren (soeren-redhat-bugs) wrote on 2014-05-09:

#45

I have encountered the same issue as Karolis Pocius. Since the update to 3.14.2-200.fc20 display brightness isn't working, while I had never experienced the original problem.

I use the same laptop as Karolis Pocius (Dell XPS m1330 with Intel® 965GM graphics)

Anything we can do to help fixing this?

Regards
Sören

Revision history for this message

In Red Hat Bugzilla #1067071, Dave (dave-redhat-bugs) wrote on 2014-05-10:

#46

I also have this problem. Would love to know how to manually get brightness to a proper level without a reboot.

For me the issue happens when I'm docked, with an external monitor, and I undock while not suspended.

Dave.

Revision history for this message

In Red Hat Bugzilla #1067071, Karolis (karolis-redhat-bugs) wrote on 2014-05-10:

#47

3.14.3-200.fc20 still has the same issue

Revision history for this message

In Red Hat Bugzilla #1067071, Karolis (karolis-redhat-bugs) wrote on 2014-05-14:

#48

As this issue remains closed, I believe the closes one that deals with brightness on XPS is Bug 1093991.

Revision history for this message

Siddharth Agarwal (sid-w) wrote on 2014-05-29:

#4

I have an X220 running Ubuntu 14.04 amd64, and I can confirm that:

- linux-image-3.13.0-27-generic has this bug
- http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/linux-image-3.14.0-031400-generic_3.14.0-031400.201403310035_amd64.deb does not have this bug.

Siddharth Agarwal (sid-w) on 2014-05-30

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2014-05-30:

#5

Siddharth Agarwal, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

In Red Hat Bugzilla #1067071, Billy (billy-redhat-bugs) wrote on 2014-06-01:

#49

Same issue on a Dell Latitude D630 with Intel® 965GM graphics.

Revision history for this message

tserries (t-serries) wrote on 2014-06-05:

#6

Is this bug related to these threads I found:

* http://linux-kernel.2935.n7.nabble.com/3-13-i915-brightness-settings-broken-when-going-from-docked-gt-undocked-td808925.html
* https://bugs.freedesktop.org/show_bug.cgi?id=75001

Revision history for this message

Daniel Hahler (blueyed) wrote on 2014-08-15:

#7

I have experienced the same problem on a Lenovo X220t, but could not reproduce it now after the latest kernel update (3.13.0-34.60).

Changed in linux (Ubuntu):
status:	Incomplete → Triaged

Revision history for this message

penalvch (penalvch) wrote on 2014-08-23:

#8

Daniel Hahler, thanks for the update on your issue. As per the Ubuntu Kernel Team, for linux (Ubuntu) bug reports, one would would mark this bug Triaged when the original reporter has tested this to the mainline kernel. As well, the OR would want to provide as much information, for example check for a WORKAROUND, if BIOS has a hand update it, regression bisect, etc.

Given that your issue is resolved, let us wait for input from the OR.

Changed in linux (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Roger Kind Kristiansen (rogerkk) wrote on 2014-08-29:

#9

I just tried this with kernel 3.13.0-34.60 and I'm still experiencing the problem. Brightness set to minimum and not adjustable after undocking.

I originally encountered another (duplicate?) bug post which suggested to upgrade the x220's BIOS, so I'm also running the latest BIOS version (8DET69WW / 1.39). The possible duplicate is at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348550?comments=all

Revision history for this message

Roger Kind Kristiansen (rogerkk) wrote on 2014-08-29:

#10

I can add that docking and undocking again re-enables brightness adjustment.

Revision history for this message

Akif D. (adadnc) wrote on 2014-10-01:

#11

I've a X220 with 14.04 and I'm facing the above problem aswell. In my setup I do have a docking station with an external monitor hooked up. Undocking my notebook darkens the notebook screen. Docking it again gives normal brightness and "undocking" again gives again regular brightness. So the problem occuse only the first time of undocking.

A solution would be great.

With regular and unchanged 14.04 installation and kernel version "Linux mybook 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"

Revision history for this message

Matthias Baur (matthiasbaur) wrote on 2014-10-02:

#12

I can also confirm this for a Lenovo ThinkPad T430s with Lenovo ThinkPad Mini Dock Plus Series 3.

OS: Ubuntu 14.04.1
Kernel: Linux ThinkPad 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

penalvch (penalvch) wrote on 2014-10-03:

#13

Roger Kind Kristiansen / adnc / Matthias Baur, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message

Muelli (ubuntu-bugs-auftrags-killer) wrote on 2014-10-08:

#14

Download full text (9.1 KiB)

FWIW: This is what I get when the problem appears:

[110652.405086] ------------[ cut here ]------------
[110652.405143] WARNING: CPU: 2 PID: 1381 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9237 intel_modeset_check_state+0x62d/0x780 [i915]()
[110652.405146] encoder's hw state doesn't match sw tracking (expected 1, found 0)
[110652.405148] Modules linked in: xt_tcpudp xt_REDIRECT xt_hl iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables usb_storage hid_generic hid_logitech_dj ctr ccm rfcomm bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm uvcvideo videobuf2_vmalloc snd_hda_intel videobuf2_memops btusb videobuf2_core arc4 snd_hda_codec joydev thinkpad_acpi serio_raw snd_hwdep videodev wacom bluetooth nvram iwldvm snd_pcm mac80211 snd_page_alloc snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi snd_seq lpc_ich nls_iso8859_1 snd_seq_device cfg80211 snd_timer snd soundcore mei_me mac_hid mei parport_pc ppdev lp parport dm_crypt usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci e1000e libahci i2c_algo_bit ptp sdhci_pci sdhci drm_kms_helper pps_core drm wmi video
[110652.405228] CPU: 2 PID: 1381 Comm: Xorg Tainted: G W 3.13.0-36-generic #63-Ubuntu
[110652.405230] Hardware name: LENOVO 3437B52/3437B52, BIOS GCET95WW (2.55 ) 08/05/2013
[110652.405233] 0000000000000009 ffff880210f73b68 ffffffff8171e569 ffff880210f73bb0
[110652.405241] ffff880210f73ba0 ffffffff8106775d ffff880210f73c20 0000000000000001
[110652.405249] ffff88020c805800 ffff88020c805af8 ffff88020c806800 ffff880210f73c00
[110652.405256] Call Trace:
[110652.405266] [<ffffffff8171e569>] dump_stack+0x45/0x56
[110652.405273] [<ffffffff8106775d>] warn_slowpath_common+0x7d/0xa0
[110652.405278] [<ffffffff810677cc>] warn_slowpath_fmt+0x4c/0x50
[110652.405312] [<ffffffffa015c4cd>] intel_modeset_check_state+0x62d/0x780 [i915]
[110652.405340] [<ffffffffa015c6b5>] intel_set_mode+0x25/0x30 [i915]
[110652.405366] [<ffffffffa015cf5b>] intel_crtc_set_config+0x7ab/0x9a0 [i915]
[110652.405396] [<ffffffffa0029ebd>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
[110652.405423] [<ffffffffa002cda7>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
[110652.405432] [<ffffffff8164dff9>] ? netlink_broadcast_filtered+0x129/0x3b0
[110652.405453] [<ffffffffa001dc22>] drm_ioctl+0x502/0x630 [drm]
[110652.405466] [<ffffffff811d3c9c>] ? dput+0x4c/0x180
[110652.405473] [<ffffffff811d0390>] do_vfs_ioctl+0x2e0/0x4c0
[110652.405480] [<ffffffff811bef1e>] ? ____fput+0xe/0x10
[110652.405488] [<ffffffff8108823c>] ? task_work_run+0xac/0xe0
[110652.405495] [<ffffffff811d05f1>] SyS_ioctl+0x81/0xa0
[110652.405500] [<ffffffff8172efad>] system_call_fastpath+0x1a/0x1f
[110652.405504] ---[ end trace 0da629c82eacbf79 ]---
[110652.405521] [drm:intel_pipe_config_compare] *ERROR* mismatch in has_dp_encoder (expected 1, found 0)
[110652.405524] ------------[ cut here ]------------
[110652.405551] WARNING: CPU: 2 PID: 1381 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display....

FWIW: This is what I get when the problem appears:

[110652.405086] ------------[ cut here ]------------
[110652.405143] WARNING: CPU: 2 PID: 1381 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9237 intel_modeset_check_state+0x62d/0x780 [i915]()
[110652.405146] encoder's hw state doesn't match sw tracking (expected 1, found 0)
[110652.405148] Modules linked in: xt_tcpudp xt_REDIRECT xt_hl iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables usb_storage hid_generic hid_logitech_dj ctr ccm rfcomm bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm uvcvideo videobuf2_vmalloc snd_hda_intel videobuf2_memops btusb videobuf2_core arc4 snd_hda_codec joydev thinkpad_acpi serio_raw snd_hwdep videodev wacom bluetooth nvram iwldvm snd_pcm mac80211 snd_page_alloc snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi snd_seq lpc_ich nls_iso8859_1 snd_seq_device cfg80211 snd_timer snd soundcore mei_me mac_hid mei parport_pc ppdev lp parport dm_crypt usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci e1000e libahci i2c_algo_bit ptp sdhci_pci sdhci drm_kms_helper pps_core drm wmi video
[110652.405228] CPU: 2 PID: 1381 Comm: Xorg Tainted: G        W     3.13.0-36-generic #63-Ubuntu
[110652.405230] Hardware name: LENOVO 3437B52/3437B52, BIOS GCET95WW (2.55 ) 08/05/2013
[110652.405233]  0000000000000009 ffff880210f73b68 ffffffff8171e569 ffff880210f73bb0
[110652.405241]  ffff880210f73ba0 ffffffff8106775d ffff880210f73c20 0000000000000001
[110652.405249]  ffff88020c805800 ffff88020c805af8 ffff88020c806800 ffff880210f73c00
[110652.405256] Call Trace:
[110652.405266]  [<ffffffff8171e569>] dump_stack+0x45/0x56
[110652.405273]  [<ffffffff8106775d>] warn_slowpath_common+0x7d/0xa0
[110652.405278]  [<ffffffff810677cc>] warn_slowpath_fmt+0x4c/0x50
[110652.405312]  [<ffffffffa015c4cd>] intel_modeset_check_state+0x62d/0x780 [i915]
[110652.405340]  [<ffffffffa015c6b5>] intel_set_mode+0x25/0x30 [i915]
[110652.405366]  [<ffffffffa015cf5b>] intel_crtc_set_config+0x7ab/0x9a0 [i915]
[110652.405396]  [<ffffffffa0029ebd>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
[110652.405423]  [<ffffffffa002cda7>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
[110652.405432]  [<ffffffff8164dff9>] ? netlink_broadcast_filtered+0x129/0x3b0
[110652.405453]  [<ffffffffa001dc22>] drm_ioctl+0x502/0x630 [drm]
[110652.405466]  [<ffffffff811d3c9c>] ? dput+0x4c/0x180
[110652.405473]  [<ffffffff811d0390>] do_vfs_ioctl+0x2e0/0x4c0
[110652.405480]  [<ffffffff811bef1e>] ? ____fput+0xe/0x10
[110652.405488]  [<ffffffff8108823c>] ? task_work_run+0xac/0xe0
[110652.405495]  [<ffffffff811d05f1>] SyS_ioctl+0x81/0xa0
[110652.405500]  [<ffffffff8172efad>] system_call_fastpath+0x1a/0x1f
[110652.405504] ---[ end trace 0da629c82eacbf79 ]---
[110652.405521] [drm:intel_pipe_config_compare] *ERROR* mismatch in has_dp_encoder (expected 1, found 0)
[110652.405524] ------------[ cut here ]------------
[110652.405551] WARNING: CPU: 2 PID: 1381 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9310 check_crtc_state+0x255/0x340 [i915]()
[110652.405554] pipe state doesn't match!
[110652.405556] Modules linked in: xt_tcpudp xt_REDIRECT xt_hl iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables usb_storage hid_generic hid_logitech_dj ctr ccm rfcomm bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm uvcvideo videobuf2_vmalloc snd_hda_intel videobuf2_memops btusb videobuf2_core arc4 snd_hda_codec joydev thinkpad_acpi serio_raw snd_hwdep videodev wacom bluetooth nvram iwldvm snd_pcm mac80211 snd_page_alloc snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi snd_seq lpc_ich nls_iso8859_1 snd_seq_device cfg80211 snd_timer snd soundcore mei_me mac_hid mei parport_pc ppdev lp parport dm_crypt usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci e1000e libahci i2c_algo_bit ptp sdhci_pci sdhci drm_kms_helper pps_core drm wmi video
[110652.405627] CPU: 2 PID: 1381 Comm: Xorg Tainted: G        W     3.13.0-36-generic #63-Ubuntu
[110652.405630] Hardware name: LENOVO 3437B52/3437B52, BIOS GCET95WW (2.55 ) 08/05/2013
[110652.405632]  0000000000000009 ffff880210f738a8 ffffffff8171e569 ffff880210f738f0
[110652.405639]  ffff880210f738e0 ffffffff8106775d ffff880035f046e0 ffff880210f73970
[110652.405646]  ffff88020c805800 ffff880035f04000 ffff88020c805b28 ffff880210f73940
[110652.405653] Call Trace:
[110652.405660]  [<ffffffff8171e569>] dump_stack+0x45/0x56
[110652.405666]  [<ffffffff8106775d>] warn_slowpath_common+0x7d/0xa0
[110652.405672]  [<ffffffff810677cc>] warn_slowpath_fmt+0x4c/0x50
[110652.405700]  [<ffffffffa014d23b>] ? intel_pipe_config_compare+0x60b/0xae0 [i915]
[110652.405725]  [<ffffffffa014ea55>] check_crtc_state+0x255/0x340 [i915]
[110652.405753]  [<ffffffffa015c15b>] intel_modeset_check_state+0x2bb/0x780 [i915]
[110652.405777]  [<ffffffffa015c6b5>] intel_set_mode+0x25/0x30 [i915]
[110652.405801]  [<ffffffffa015cf5b>] intel_crtc_set_config+0x7ab/0x9a0 [i915]
[110652.405827]  [<ffffffffa0029ebd>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
[110652.405852]  [<ffffffffa002cda7>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
[110652.405861]  [<ffffffff8164dff9>] ? netlink_broadcast_filtered+0x129/0x3b0
[110652.405881]  [<ffffffffa001dc22>] drm_ioctl+0x502/0x630 [drm]
[110652.405893]  [<ffffffff811d3c9c>] ? dput+0x4c/0x180
[110652.405900]  [<ffffffff811d0390>] do_vfs_ioctl+0x2e0/0x4c0
[110652.405907]  [<ffffffff811bef1e>] ? ____fput+0xe/0x10
[110652.405913]  [<ffffffff8108823c>] ? task_work_run+0xac/0xe0
[110652.405920]  [<ffffffff811d05f1>] SyS_ioctl+0x81/0xa0
[110652.405925]  [<ffffffff8172efad>] system_call_fastpath+0x1a/0x1f
[110652.405929] ---[ end trace 0da629c82eacbf7a ]---
[110652.411472] ------------[ cut here ]------------
[110652.411533] WARNING: CPU: 0 PID: 1381 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_dp.c:2747 intel_dp_link_down+0x1d2/0x210 [i915]()
[110652.411536] Modules linked in: xt_tcpudp xt_REDIRECT xt_hl iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables usb_storage hid_generic hid_logitech_dj ctr ccm rfcomm bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm uvcvideo videobuf2_vmalloc snd_hda_intel videobuf2_memops btusb videobuf2_core arc4 snd_hda_codec joydev thinkpad_acpi serio_raw snd_hwdep videodev wacom bluetooth nvram iwldvm snd_pcm mac80211 snd_page_alloc snd_seq_midi snd_seq_midi_event iwlwifi snd_rawmidi snd_seq lpc_ich nls_iso8859_1 snd_seq_device cfg80211 snd_timer snd soundcore mei_me mac_hid mei parport_pc ppdev lp parport dm_crypt usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 psmouse ahci e1000e libahci i2c_algo_bit ptp sdhci_pci sdhci drm_kms_helper pps_core drm wmi video
[110652.411649] CPU: 0 PID: 1381 Comm: Xorg Tainted: G        W     3.13.0-36-generic #63-Ubuntu
[110652.411653] Hardware name: LENOVO 3437B52/3437B52, BIOS GCET95WW (2.55 ) 08/05/2013
[110652.411657]  0000000000000009 ffff880210f73a80 ffffffff8171e569 0000000000000000
[110652.411663]  ffff880210f73ab8 ffffffff8106775d ffff88020c8068c8 ffff88020c805800
[110652.411670]  ffff880035f04000 0000000084580304 ffff88020c404000 ffff880210f73ac8
[110652.411676] Call Trace:
[110652.411686]  [<ffffffff8171e569>] dump_stack+0x45/0x56
[110652.411694]  [<ffffffff8106775d>] warn_slowpath_common+0x7d/0xa0
[110652.411700]  [<ffffffff8106783a>] warn_slowpath_null+0x1a/0x20
[110652.411734]  [<ffffffffa0169402>] intel_dp_link_down+0x1d2/0x210 [i915]
[110652.411767]  [<ffffffffa016d770>] intel_disable_dp+0x70/0x80 [i915]
[110652.411796]  [<ffffffffa015280e>] ironlake_crtc_disable+0x1ae/0x940 [i915]
[110652.411805]  [<ffffffff81614274>] ? consume_skb+0x34/0x80
[110652.411834]  [<ffffffffa0159459>] __intel_set_mode+0x2c9/0x9d0 [i915]
[110652.411863]  [<ffffffffa015c6a6>] intel_set_mode+0x16/0x30 [i915]
[110652.411890]  [<ffffffffa015cf5b>] intel_crtc_set_config+0x7ab/0x9a0 [i915]
[110652.411921]  [<ffffffffa0029ebd>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
[110652.411948]  [<ffffffffa002cda7>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
[110652.411969]  [<ffffffffa001dc22>] drm_ioctl+0x502/0x630 [drm]
[110652.411982]  [<ffffffff8108ea92>] ? __hrtimer_start_range_ns+0x1a2/0x3a0
[110652.411991]  [<ffffffff811d0390>] do_vfs_ioctl+0x2e0/0x4c0
[110652.411998]  [<ffffffff8160b2b5>] ? __sys_recvmsg+0x65/0x80
[110652.412005]  [<ffffffff811d05f1>] SyS_ioctl+0x81/0xa0
[110652.412012]  [<ffffffff8172efad>] system_call_fastpath+0x1a/0x1f
[110652.412016] ---[ end trace 0da629c82eacbf7b ]---
[110652.793723] thinkpad_acpi: EC reports that Thermal Table has changed
[110652.897172] thinkpad_acpi: undocked from hotplug port replicator
[110652.898134] ACPI: \_SB_.GDCK: undocking

$ sudo dmidecode -s bios-version ; sudo dmidecode -s bios-release-date
GCET95WW (2.55 )
08/05/2013

Revision history for this message

Akif D. (adadnc) wrote on 2014-10-08:

#15

Muelli I do have Bios version 8DET69WW (1.39 ) release-date 07/18/2013. Yours has a higher major number but on older date

Revision history for this message

penalvch (penalvch) wrote on 2014-10-08:

#16

Muelli / Akif D., thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message

arnuschky (abrutschy) wrote on 2014-11-19:

#17

I am having the same problem on my X230

Linux hostname 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Found a workaround: press CTRL+ALT+F1 to go into terminal mode, press FN+BrightnessUp to reset brightness, press CTRL+ALT+F7 to go back to Xwindows.

Revision history for this message

Akif D. (adadnc) wrote on 2014-11-19:

#18

There is a kernel that has a fix, I've reported all of it. I don't know why that kernel is not distributed yet.

Revision history for this message

Matthias Baur (matthiasbaur) wrote on 2014-11-22:

#19

Which kernel has a fix?

Revision history for this message

Akif D. (adadnc) wrote on 2014-11-22:

#20

3.14.1-031401-generic has a fix

Revision history for this message

Akif D. (adadnc) wrote on 2014-11-22:

#21

look here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377120

Revision history for this message

eliash (elia-shreidler) wrote on 2014-11-26:

#22

Don't want to douple post, but it's unclear where this bug is maintained, here or in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377120

just in case,
I experience the brightness going to minimum on:
* undock
* after waking up from suspend

Lenovo x230

$ cat /etc/issue
Ubuntu 12.04.5 LTS \n \l

$ uname -a
Linux ****-ubuntu 3.17.3-031703-generic #201411141335 SMP Fri Nov 14 18:36:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

$ gnome-shell --version
GNOME Shell 3.4.1

Revision history for this message

penalvch (penalvch) wrote on 2014-11-26:

#23

eliash, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message

Alex Schmidt (schmidt-k) wrote on 2015-03-05:

#24

This issue is still existing.

Thinkpad X230

$ uname -a
Linux ******* 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

Akif D. (adadnc) wrote on 2015-03-05:

#25

I can confirm that the issue with kernel 3.13.0-46 still exist. The only way around I see is using 3.14-kernel

Bug Watch Updater (bug-watch-updater) on 2017-10-27

Changed in linux (Fedora):
importance:	Unknown → Undecided
status:	Unknown → Fix Released

Revision history for this message

Will Cooke (willcooke) wrote on 2017-10-27:

#50

This issue went away for me sometime in the last year.

penalvch (penalvch) on 2017-10-27

no longer affects:	linux (Fedora)
no longer affects:	linux (Ubuntu)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-10-27:

#51

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message

penalvch (penalvch) wrote on 2017-10-27:

#52

As per https://bugs.launchpad.net/linux/+bug/1308674/comments/50.

Launchpad Janitor (janitor) on 2017-10-27

Changed in linux (Ubuntu):
status:	New → Confirmed

penalvch (penalvch) on 2017-10-27

affects:	linux → linux (Ubuntu)
Changed in linux (Ubuntu):
status:	New → Invalid

Ubuntu
linux package

[Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux package

[Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package