[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226 intel_modeset_check_state+0x62d/0x780 [i915]()

[KeithG]

Dmesg is filled with this:
[32582.450283] ------------[ cut here ]------------
[32582.450302] WARNING: CPU: 1 PID: 1154 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226 intel_modeset_check_state+0x62d/0x780 [i915]()
[32582.450304] encoder's hw state doesn't match sw tracking (expected 0, found 1)
[32582.450306] Modules linked in: nfsv3 ctr ccm rfcomm bnep bluetooth rpcsec_gss_krb5 nfsv4 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache arc4 gpio_ich dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dell_laptop dcdbas snd_hda_codec_idt snd_hda_codec_hdmi b43 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm bcma coretemp snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi joydev snd_seq serio_raw mac80211 snd_seq_device snd_timer snd lpc_ich cfg80211 ssb_hcd soundcore mac_hid wmi parport_pc ppdev lp parport psmouse ahci libahci sky2 ssb i915 video i2c_algo_bit drm_kms_helper drm
[32582.450357] CPU: 1 PID: 1154 Comm: Xorg Tainted: G W 3.13.0-27-generic #50-Ubuntu
[32582.450359] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009
[32582.450361] 0000000000000009 ffff88000003bb68 ffffffff817199c4 ffff88000003bbb0
[32582.450365] ffff88000003bba0 ffffffff810676bd ffff88000003bc20 0000000000000001
[32582.450369] ffff88003684c800 ffff88003684caf8 ffff8800364a9800 ffff88000003bc00
[32582.450373] Call Trace:
[32582.450378] [<ffffffff817199c4>] dump_stack+0x45/0x56
[32582.450381] [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
[32582.450384] [<ffffffff8106772c>] warn_slowpath_fmt+0x4c/0x50
[32582.450405] [<ffffffffa012fd25>] ? intel_sdvo_get_hw_state+0x55/0xc0 [i915]
[32582.450423] [<ffffffffa011a16d>] intel_modeset_check_state+0x62d/0x780 [i915]
[32582.450441] [<ffffffffa011a355>] intel_set_mode+0x25/0x30 [i915]
[32582.450459] [<ffffffffa011abfb>] intel_crtc_set_config+0x7ab/0x9a0 [i915]
[32582.450463] [<ffffffff810428ad>] ? lapic_next_event+0x1d/0x30
[32582.450477] [<ffffffffa000fe9d>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
[32582.450492] [<ffffffffa0012d87>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
[32582.450503] [<ffffffffa0003c22>] drm_ioctl+0x502/0x630 [drm]
[32582.450508] [<ffffffff81077dd2>] ? __set_task_blocked+0x32/0x70
[32582.450513] [<ffffffff811cf810>] do_vfs_ioctl+0x2e0/0x4c0
[32582.450517] [<ffffffff8109dd84>] ? vtime_account_user+0x54/0x60
[32582.450520] [<ffffffff811cfa71>] SyS_ioctl+0x81/0xa0
[32582.450524] [<ffffffff8172a5bf>] tracesys+0xe1/0xe6
[32582.450526] ---[ end trace 8e8416ac0cd5b971 ]---

Resume results in black screen. Graphics can appear completely messed up (i.e. torn last jpg viewed over top of latest jpg). This happens in Ubuntu 13.10 and 14.04. It happens with: no intel drivers installed, and with or without the i915 and intel_agp modules explicitly enabled in /etc/initramfs-tools/modules.

WORKAROUND: Using the following kernel parameters I no longer get the message in the log, the video does not appear to be as crisp somehow, but I can suspend and wake from the command:
linemodeset=0 video.allow_duplicates=1

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-27-generic 3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kgrider 2212 F.... pulseaudio
Date: Fri May 30 08:03:14 2014
HibernationDevice: RESUME=UUID=4957c02d-b4ca-4dce-8983-450640c97f46
MachineType: Dell Inc. Inspiron 1525
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=7682c6bb-cf2f-413f-9243-eab8172b5bbc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-27-generic N/A
 linux-backports-modules-3.13.0-27-generic N/A
 linux-firmware 1.127.2
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-05-30 (0 days ago)
WifiSyslog:
 May 30 06:59:26 Inspiron-1525 NetworkManager[938]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
 May 30 07:11:21 Inspiron-1525 wpa_supplicant[1092]: message repeated 29 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
 May 30 07:13:02 Inspiron-1525 wpa_supplicant[1092]: wlan0: WPA: Group rekeying completed with 10:0d:7f:52:8a:71 [GTK=TKIP]
 May 30 07:13:21 Inspiron-1525 wpa_supplicant[1092]: wlan0: CTRL-EVENT-SCAN-STARTED
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc7-utopic/

[Brad Figg (brad-figg)]

This change was made by a bot.

[KeithG (grider-4)]

Tried latest mainline intel kernel I could find (3.15.0-994-generic) and same issue. This appears to be from, at least, 13.10 to current kernel.

I got this latest kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ and selected this one: drm-intel-nightly from 5/30/14

I see that the bot confirmed it and gave it medium priority. Never have used an intel gpu, but this experience confirms my previous reservations.

Keith

[KeithG (grider-4)]

3.15.0-031500rc7-generic kernel has it as well.

[penalvch (penalvch)]

KeithG, does the WARNING only come up after you attempt to suspend/resume, or does it also occur coming up from a restart/shutdown?

As well, did this problem not occur in a release prior to Saucy?

[KeithG (grider-4)]

Just installed it and checked dmesg and this warning was there. I recently got this computer and have only tried 13.10 and 14.04. THis si after a cold boot. If I try to suspend, it appears to suspend correctly. When I resume, it has black screen. I have done a ton of updates, so I need to try suspend/resume again.

Dell Inspiron 1425

Been using it today and just noticed this in the dmesg:
[Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.

I'll try that as well. I am guessing I need to put this in the /etc/modules file somehow?

Keith

[penalvch (penalvch)]

KeithG, regarding your Dell Inspiron 1525, for regression testing purposes, could you please test 12.04.0 via http://old-releases.ubuntu.com/releases/12.04.0/ and advise to the results?

As well, so you have an additional Dell computer, a 1425? If so, please file a new report about that via a terminal:
ubuntu-bug linux

[KeithG (grider-4)]

Actually, that was mis-typed. It is only one and the computer is a Dell Inspiron 1525.

I will not get to testing with 12.04 today. I did make a couple of config edits and no longer get that message in the log.

I edited /etc/initramfs-tools/modules I added these parameters after the i915 module call
modeset=0 video.allow_duplicates=1

I no longer get the message in the log. The video does not appear to be as crisp somehow, but I can suspend and wake from the command line (tty or terminal) I get a black screen on resume when I allow the UI to timeout and suspend.

KeithG

[KeithG (grider-4)]

If I set modeset=1 or -1, I get the crash on resume. Black screen on all ttys and no reconnect to network (I cannot ssh back in).

modeset = 0 will allow normal function, but no KMS.

KeithG

[KeithG (grider-4)]

I loaded 12.04 amd64 on it this morning. This appears to work correctly. I can suspend and resume with no issues. There is no warning in the log other than the 'duplicate interface' which does not seem to affect anything. I have not upgraded anything, just installed xubuntu 12.04 then installed the wifi driver and chrome.

uname -a
Linux Inspiron-1525 3.2.0-58-generic #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

lsmod
Module Size Used by
michael_mic 12612 4
arc4 12529 2
rfcomm 47604 4
bnep 18281 2
bluetooth 180113 10 rfcomm,bnep
parport_pc 32866 0
ppdev 17113 0
snd_hda_codec_idt 70795 1
snd_hda_codec_hdmi 32530 1
joydev 17693 0
lib80211_crypt_tkip 17390 0
wl 3074895 0
snd_hda_intel 33719 4
snd_hda_codec 127706 3 snd_hda_codec_idt,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 17764 1 snd_hda_codec
snd_pcm 97275 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_seq_midi 13324 0
snd_rawmidi 30748 1 snd_seq_midi
dell_wmi 12681 0
sparse_keymap 13890 1 dell_wmi
snd_seq_midi_event 14899 1 snd_seq_midi
snd_seq 61929 2 snd_seq_midi,snd_seq_midi_event
dell_laptop 18119 0
snd_timer 29990 2 snd_pcm,snd_seq
dcdbas 14490 1 dell_laptop
snd_seq_device 14540 3 snd_seq_midi,snd_rawmidi,snd_seq
snd 79041 18 snd_hda_codec_idt,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
cfg80211 205774 1 wl
lib80211 14381 2 lib80211_crypt_tkip,wl
psmouse 97519 0
serio_raw 13211 0
soundcore 15091 1 snd
snd_page_alloc 18529 2 snd_hda_intel,snd_pcm
uvcvideo 72627 0
videodev 98259 1 uvcvideo
v4l2_compat_ioctl32 17128 1 videodev
mac_hid 13253 0
i915 478471 3
drm_kms_helper 46978 1 i915
wmi 19256 1 dell_wmi
drm 241971 4 i915,drm_kms_helper
i2c_algo_bit 13423 1 i915
video 19651 1 i915
lp 17799 0
parport 46562 3 parport_pc,ppdev,lp
sky2 59043 0

[penalvch (penalvch)]

KeithG, the next step is to fully commit bisect the kernel in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[KeithG (grider-4)]

I have started the process. Strange that this bug has crept in and no one has noticed. It is pretty limiting, actually.

KeithG

[KeithG (grider-4)]

Christopher,

I am willing to do this, but need a bit more hand holding to do it. I have collected the ubuntu-saucy abd ubuntu-precise kernel folders. I am trying to follow the example, but do not get very far.

What I think I know: linux 3.2.0.63-generic works well. This is the latest kernel from precise (12.04). The initial kernel from Saucy does not work, it is linux 3.11.0-12.19. That is a huge jump in revision (3.2 to 3.11) and the example shows how to bisect within a release. Do I need to try the 12.10, then 13.04 releases first in order to do this bisect or can it be done with what I know now? If so, I need a bit more help to do it.

KeithG

[penalvch (penalvch)]

Keith G, you could techncially begin git bisecting between 3.2 and 3.11, you may want to try 12.10/13.04 first to further narrow it down more quickly.

[KeithG (grider-4)]

I tried 12.10 and 13.04. 12.10 appears to work. Initial install of 13.04 appears to work. When I dist-upgraded 13.04 after I installed it, I got the warning in the log. I think I have narrowed it down to this release. I was going to respond with the kernel versions at beginning and end of 13.04, but I cannot get 'in' to this computer remotely, now. With 12.04, I could WoL this computer and SSH in. With 13.04, I cannot and, therefore, cannot work on this today until I get back home. I checked it and rebooted with the initial kernel and the warning was not there and then booted with the last kernel and the warning was there. I will double check and see if I can figure out why it will not WoL and more.

From here: https://launchpad.net/ubuntu/raring/+source/linux

It appears that the initial kernel is: 3.8.0.19-29 and the upgrade installed 3.8.0.35-50 (I think)

I was able to get the kernel repository
$ git clone git://kernel.ubuntu.com/ubuntu-archive/ubuntu-raring.git
$ git checkout -b mybisect origin/master

I tried to do a
$ git log --oneline Ubuntu-3.8.0.19-29..3.8.0.35-50
fatal: ambiguous argument 'Ubuntu-3.8.0.19-29..3.8.0.35-50': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

When I try:
$ git bisect start Ubuntu-3.8.0.19-29 3.8.0.35-50

I get no returns at all. I am not doing this right. Can I get some more help?

[penalvch (penalvch)]

KeithG, you were very close. You would want:
git bisect start Ubuntu-3.8.0.19-29 Ubuntu-3.8.0.35-50

[KeithG (grider-4)]

Ok, I did my first bisect with 3.8.0-28.42 and it came up bad. Now I am here:

$ git bisect bad
Bisecting: 388 revisions left to test after this (roughly 9 steps)
error: Your local changes to the following files would be overwritten by checkout:
 debian.master/changelog
Please, commit your changes or stash them before you can switch branches.
Aborting

It is not clear to me what I am to do next.

[penalvch (penalvch)]

keith G, you would want to map the Ubuntu kernel to the mainline one via http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html and then switch to bisecting the mainline kernel following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_bisect_the_upstream_kernel.3F .

[KeithG (grider-4)]

This is extremely confusing. 1) The kernels I am using do not appear in that mainline map (version numbers are just not there) 2) I'd rather just keep going with my first attempt. 3) the example on the https://wiki.ubuntu.com/Kernel/KernelBisection apparently uses a older version of git than in Raring, so the syntax of some of the example commands do not work

Please help me continue with where I am and not change a bunch of things. I have done one bisect. I get the concept and want to continue to narrow this down. It takes a LONG time to compile the kernel on this old laptop, so this may take a while. I want to help and want to get this resolved, but lets try to keep it on one track with some examples so I can feel my way along.

How do I tell git to disregard my last edits and just do a new bisect with different end points? If I can figure this out, I can, hopefully, narrow down which of the many i915 commits broke this for me and others. I do not want to download this again as it takes a long time.

[KeithG (grider-4)]

I figured it out. I was able to start over. The key is to not edit any of the files as it bisects. The revision numbers are good enough for me to keep track of where I am. As it is, I have done 4 or 5 bisects and am narrowing it down.

[KeithG (grider-4)]

Ok, Something is going wrong. It stalled at 3.8.0-26.38. It is 'good', but when I go and do 'git bisect good', it does some stuff and returns and appears to have a new version to build. WHen I build it, it is the same version 3.8.0-26.38.

[KeithG (grider-4)]

Please help! I am trying to follow the instructions to find this bug and am a bit lost. I have determined that this bug is between 3.8.0-26.38 and 3.8.0-28.42. These do not 'map' to the Mainline kernel map, directly. so I am guessing near these 2 end points. Following the Mainline instructions, I have pulled the Mainline kernel
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
I have done a
git checkout 3.8.13.2 (which I htink is in the 'good' range)
Now, when I try to do a git bisect, the only possibilities in 3.8 are:
v3.8 v3.8-rc2 v3.8-rc4 v3.8-rc6
v3.8-rc1 v3.8-rc3 v3.8-rc5 v3.8-rc7

and all I can bisect between are 3.8 and 3.9 which leaves me 13 steps!

How do I get the xx.xx versions so I can have this narrowed?

[penalvch (penalvch)]

KeithG, following the mapping as noted in https://wiki.ubuntu.com/Kernel/KernelBisection#Map_Ubuntu_kernel_to_Mainline_kernel_for_mainline_bisection you would want to bisect the upstream (not Ubuntu) kernel between 3.8.13.2 and 3.8.13.5 .

[KeithG (grider-4)]

Christopher,

I Appreciate the help and apologize for being so dense. I think I get it, but am still a bit lost with the mainline kernel. From the kernel mapping, I see the 2 kernel versions you are referring to. I have git cloned the kernel. When I try to tell it that I want 3.8.13.2, though, that version is not 'there'. The only selections I have are what I listed above.
I got the kernel via git
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux/
$ cp /boot/config-`uname -r` .config
$ yes '' | make oldconfig
$ make clean
$ git checkout v3.8.13.2
error: pathspec 'v3.8.13.2' did not match any file(s) known to git.
When I start it and 'tab' to see the options, I get this
$ git checkout v3.8
v3.8 v3.8-rc2 v3.8-rc4 v3.8-rc6
v3.8-rc1 v3.8-rc3 v3.8-rc5 v3.8-rc7

so I went a bit further just to see what happened

$ git bisect start
git bisect bad v3.9
git bisect good v3.8
$ make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom

This also makes a 625Mb kernel image. I need to free up more space.

[KeithG (grider-4)]

Poked around some more and was able to get other versions in my copy of the mainline kernel.

this command got me some more kernel versions:
git remote set-url origin git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

now, when I 'tab' to see what is there, I get:
$ git checkout -f v3.8.
v3.8.1 v3.8.11 v3.8.13 v3.8.3 v3.8.5 v3.8.7 v3.8.9
v3.8.10 v3.8.12 v3.8.2 v3.8.4 v3.8.6 v3.8.8

Still trying to figure out how to get the last decimal version.

Anyway, I built v3.8.11, 12 and 13. Problem is that I do nto have any modules. I found this instruction on building the mainline kernel: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

The kernel builds, but no modules are built when I use the command suggested:

CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom --overlay-dir=$HOME/ubuntu-package kernel_image kernel_headers

There are no errors with v3.8.13, but there are also no i915 drivers installed and I think that is where the bug is. Any help appreciated.

[KeithG (grider-4)]

Am now getting full builds with modules. Still no 4th decimal. There is some disconnect, though, between the Ubuntu Kernels and the Mainline kernels. All V3.8.x kernels build and do not exhibit the error. The V3.9 Kernel does not exhibit the error. The v3.8.15 does, though. I am building the v3.10 Kernel now and will try it tonight. If it fails, I will bisect between the v3.9 and v3.10.

Keith

[KeithG (grider-4)]

I guess the bisect has run to its completion. 10 trials between v3.9 and v3.10. The output of my last 'git bisect bad' is this:

The merge base c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1 is bad.
This means the bug has been fixed between c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1 and [2794b5d408c625e104de813d3de7ac0ec34d46d9 62c3b4bf66bfff62faf4556ee5ba251ba5e8b506 92ddcf4a011a95dac98d3bbb0211a2fa42f13dc1 c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1 ed34add734e33afa33e7bf5ee5826650efdc0fe8].

What is my next step?

Keith

[penalvch (penalvch)]

KeithG, you would actually have to test the fix commit itself in order to verify these findings.

[KeithG (grider-4)]

Christopher,

Can you point me to some instructions on this? It appears that there are 5
commits that need to be checked. How do I get the diff and for each commit?
I guess I need to apply these to the 'last good' kernel. How do I find out
which one this is without trying all the versions again. I do not remember
which kernel version was the last 'good' one.

Keith

On Tue, Jun 17, 2014 at 6:00 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> KeithG, you would actually have to test the fix commit itself in order
> to verify these findings.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1324935
>
> Title:
> [Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
> /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
> intel_modeset_check_state+0x62d/0x780 [i915]()
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> Dmesg is filled with this:
> [32582.450283] ------------[ cut here ]------------
> [32582.450302] WARNING: CPU: 1 PID: 1154 at
> /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
> intel_modeset_check_state+0x62d/0x780 [i915]()
> [32582.450304] encoder's hw state doesn't match sw tracking (expected 0,
> found 1)
> [32582.450306] Modules linked in: nfsv3 ctr ccm rfcomm bnep bluetooth
> rpcsec_gss_krb5 nfsv4 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc
> fscache arc4 gpio_ich dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc
> videobuf2_memops videobuf2_core videodev dell_laptop dcdbas
> snd_hda_codec_idt snd_hda_codec_hdmi b43 snd_hda_intel snd_hda_codec
> snd_hwdep snd_pcm bcma coretemp snd_page_alloc snd_seq_midi
> snd_seq_midi_event snd_rawmidi joydev snd_seq serio_raw mac80211
> snd_seq_device snd_timer snd lpc_ich cfg80211 ssb_hcd soundcore mac_hid wmi
> parport_pc ppdev lp parport psmouse ahci libahci sky2 ssb i915 video
> i2c_algo_bit drm_kms_helper drm
> [32582.450357] CPU: 1 PID: 1154 Comm: Xorg Tainted: G W
> 3.13.0-27-generic #50-Ubuntu
> [32582.450359] Hardware name: Dell Inc. Inspiron 1525
> /0U990C, BIOS A17 10/27/2009
> [32582.450361] 0000000000000009 ffff88000003bb68 ffffffff817199c4
> ffff88000003bbb0
> [32582.450365] ffff88000003bba0 ffffffff810676bd ffff88000003bc20
> 0000000000000001
> [32582.450369] ffff88003684c800 ffff88003684caf8 ffff8800364a9800
> ffff88000003bc00
> [32582.450373] Call Trace:
> [32582.450378] [<ffffffff817199c4>] dump_stack+0x45/0x56
> [32582.450381] [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
> [32582.450384] [<ffffffff8106772c>] warn_slowpath_fmt+0x4c/0x50
> [32582.450405] [<ffffffffa012fd25>] ? intel_sdvo_get_hw_state+0x55/0xc0
> [i915]
> [32582.450423] [<ffffffffa011a16d>]
> intel_modeset_check_state+0x62d/0x780 [i915]
> [32582.450441] [<ffffffffa011a355>] intel_set_mode+0x25/0x30 [i915]
> [32582.450459] [<ffffffffa011abfb>] intel_crtc_set_config+0x7ab/0x9a0
> [i915]
> [32582.450463] [<ffffffff810428ad>] ? lapic_next_event+0x1d/0x30
> [32582.450477] [<ffffffffa000fe9d>]
> drm_mode_set_config_internal+0x5d/0xe0 [drm]
> [32582.450492] [<ffffffffa00...

[penalvch (penalvch)]

KeithG, you would just build your kernel up to a commit in the middle and see where you stand specifically.

[KeithG (grider-4)]

Christopher,

I really want to squash this bug, but need a bit more hand holding on this.
I am not that conversant in git.

Would it be something like this?

git checkout -f ed34add734e33afa33e7bf5ee5826650efdc0fe8

and start from there?

Keith

On Tue, Jun 17, 2014 at 7:08 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> KeithG, you would just build your kernel up to a commit in the middle
> and see where you stand specifically.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1324935
>
> Title:
> [Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
> /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
> intel_modeset_check_state+0x62d/0x780 [i915]()
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> Dmesg is filled with this:
> [32582.450283] ------------[ cut here ]------------
> [32582.450302] WARNING: CPU: 1 PID: 1154 at
> /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
> intel_modeset_check_state+0x62d/0x780 [i915]()
> [32582.450304] encoder's hw state doesn't match sw tracking (expected 0,
> found 1)
> [32582.450306] Modules linked in: nfsv3 ctr ccm rfcomm bnep bluetooth
> rpcsec_gss_krb5 nfsv4 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc
> fscache arc4 gpio_ich dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc
> videobuf2_memops videobuf2_core videodev dell_laptop dcdbas
> snd_hda_codec_idt snd_hda_codec_hdmi b43 snd_hda_intel snd_hda_codec
> snd_hwdep snd_pcm bcma coretemp snd_page_alloc snd_seq_midi
> snd_seq_midi_event snd_rawmidi joydev snd_seq serio_raw mac80211
> snd_seq_device snd_timer snd lpc_ich cfg80211 ssb_hcd soundcore mac_hid wmi
> parport_pc ppdev lp parport psmouse ahci libahci sky2 ssb i915 video
> i2c_algo_bit drm_kms_helper drm
> [32582.450357] CPU: 1 PID: 1154 Comm: Xorg Tainted: G W
> 3.13.0-27-generic #50-Ubuntu
> [32582.450359] Hardware name: Dell Inc. Inspiron 1525
> /0U990C, BIOS A17 10/27/2009
> [32582.450361] 0000000000000009 ffff88000003bb68 ffffffff817199c4
> ffff88000003bbb0
> [32582.450365] ffff88000003bba0 ffffffff810676bd ffff88000003bc20
> 0000000000000001
> [32582.450369] ffff88003684c800 ffff88003684caf8 ffff8800364a9800
> ffff88000003bc00
> [32582.450373] Call Trace:
> [32582.450378] [<ffffffff817199c4>] dump_stack+0x45/0x56
> [32582.450381] [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
> [32582.450384] [<ffffffff8106772c>] warn_slowpath_fmt+0x4c/0x50
> [32582.450405] [<ffffffffa012fd25>] ? intel_sdvo_get_hw_state+0x55/0xc0
> [i915]
> [32582.450423] [<ffffffffa011a16d>]
> intel_modeset_check_state+0x62d/0x780 [i915]
> [32582.450441] [<ffffffffa011a355>] intel_set_mode+0x25/0x30 [i915]
> [32582.450459] [<ffffffffa011abfb>] intel_crtc_set_config+0x7ab/0x9a0
> [i915]
> [32582.450463] [<ffffffff810428ad>] ? lapic_next_event+0x1d/0x30
> [32582.450477] [<ffffffffa000fe9d>]
> drm_mode_set_config_internal+0x5d/0xe0 [drm]
> [32582.450492] [<ffffffffa0012d87>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
> [32582.450503] [<ffffffffa0003c22>] drm_ioctl+0x502/0x630 [drm]
>...

[penalvch (penalvch)]

KeithG, following https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_upstream_kernel_versions it's going to look something like:
sudo apt-get -y install git build-essential kernel-package fakeroot libncurses5-dev && cd $HOME && git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git && cd linux-stable && git checkout COMMIT && cp /boot/config-`uname -r` .config && yes '' | make oldconfig && make clean && make -j `getconf _NPROCESSORS_ONLN` deb-pkg LOCALVERSION=-custom && cd .. && sudo dpkg -i *.deb

where COMMIT is the number you want to test against.

[KeithG (grider-4)]

Christopher.

I think know how to do those steps. Is it important that I git clone again? Should my repository be linux-stable? Mine is currently ~/linux

I was able to build commit ed34add734e33afa33e7bf5ee5826650efdc0fe8 and that works.

I am confused as to how to go about selecting which versions to build. Which commits came first in the list and which ones are later? I just did a "git checkout c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1" (the second to last commit in the list) and the previous commit ed34add... does not appear when I grep the git log. Can I use commit numbers and bisect further? If so, which commits do I use as the end points? As a test, I checked out the 'bad' commit listed above :

 git checkout 2794b5d408c625e104de813d3de7ac0ec34d46d9

then grepped for the commit for the build I just built. (ed34add734e33afa33e7bf5ee5826650efdc0fe8) and I cannot find that commit in the new checkout. This is the source of my confusion.

Keith

[KeithG (grider-4)]

Christopher.

I used the commit numbers and did the bisect again. Now it points to one commit which causes the error:

8164f7af88d9ad3a757bd14f634b23997ee77f6b is the first bad commit
commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b
Author: Stephen Boyd <email address hidden>
Date: Mon Mar 18 19:44:15 2013 +0100

    ARM: 7680/1: Detect support for SDIV/UDIV from ISAR0 register

    The ISAR0 register indicates support for the SDIV and UDIV
    instructions in both the Thumb and ARM instruction set. Read the
    register to detect the supported instructions and update the
    elf_hwcap mask as appropriate. This is better than adding more
    and more cpuid checks in proc-v7.S for each new cpu variant that
    supports these instructions.

    Acked-by: Will Deacon <email address hidden>
    Cc: Stepan Moskovchenko <email address hidden>
    Signed-off-by: Stephen Boyd <email address hidden>
    Signed-off-by: Russell King <email address hidden>

:040000 040000 b755a983671af20cd916e8abdfb5faeec65cd992 c188c1b1dd42e6631d19cf718f9b6e15d1bc1e94 M arch

What next. That was a bunch of compiling.

Keith

[penalvch (penalvch)]

KeithG, did you actually test the commit to verify the proble exists, and test one commit older to verify it's gone?

[KeithG (grider-4)]

Yes. Bisecting between commits actually did that for me. My 8th pass used commit c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 which was 'good' and was the next older commit. The next newer commit was the 9th pass which used commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b which was 'bad'. Should I contact the author of the commit?

[KeithG (grider-4)]

It seems odd as the diff shows only changes to the arm branch of the code. the result of the lshw command are attached.

[penalvch (penalvch)]

KeithG, allow me to rephrase my question. Just to be clear, git bisecting doesn't verify if the problem was in the commit or not. What verifies it is actually building a kernel against that commit, and then testing it to verify the git bisect results. So my question is did you actually build the kernel and test it, and then build one commit (not bisect point) back to verify the results?

[KeithG (grider-4)]

Christoper, I am not sure. My second git bisect was done using commits as the end points and not versions. I tracked the commit numbers as bisect did its work and it appeared that the 8th run actually built to that commit. I have done a git pull to the commit right before this (c40e3641670eb6ebfdb71d4b0c775416ef95f4f0) and am building that right now (build #32 :-() which 'i think' is the 8thn pass. I'll know in a couple hours and post back.

[KeithG (grider-4)]

it turned up bad. I am going one back from that. e651eab0af88aa7a281fe9e8c36c0846552aa7fc. and will test that.

[KeithG (grider-4)]

So far I have tested 5 back and still have the error. Isn't this what git
bisect is supposed to do? At this rate I'll be compiling for a week, one at
a time.
On Jun 28, 2014 2:55 PM, "KeithG" <email address hidden> wrote:

> it turned up bad. I am going one back from that.
> e651eab0af88aa7a281fe9e8c36c0846552aa7fc. and will test that.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1324935
>
> Title:
> [Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
> /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
> intel_modeset_check_state+0x62d/0x780 [i915]()
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> Dmesg is filled with this:
> [32582.450283] ------------[ cut here ]------------
> [32582.450302] WARNING: CPU: 1 PID: 1154 at
> /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
> intel_modeset_check_state+0x62d/0x780 [i915]()
> [32582.450304] encoder's hw state doesn't match sw tracking (expected 0,
> found 1)
> [32582.450306] Modules linked in: nfsv3 ctr ccm rfcomm bnep bluetooth
> rpcsec_gss_krb5 nfsv4 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc
> fscache arc4 gpio_ich dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc
> videobuf2_memops videobuf2_core videodev dell_laptop dcdbas
> snd_hda_codec_idt snd_hda_codec_hdmi b43 snd_hda_intel snd_hda_codec
> snd_hwdep snd_pcm bcma coretemp snd_page_alloc snd_seq_midi
> snd_seq_midi_event snd_rawmidi joydev snd_seq serio_raw mac80211
> snd_seq_device snd_timer snd lpc_ich cfg80211 ssb_hcd soundcore mac_hid wmi
> parport_pc ppdev lp parport psmouse ahci libahci sky2 ssb i915 video
> i2c_algo_bit drm_kms_helper drm
> [32582.450357] CPU: 1 PID: 1154 Comm: Xorg Tainted: G W
> 3.13.0-27-generic #50-Ubuntu
> [32582.450359] Hardware name: Dell Inc. Inspiron 1525
> /0U990C, BIOS A17 10/27/2009
> [32582.450361] 0000000000000009 ffff88000003bb68 ffffffff817199c4
> ffff88000003bbb0
> [32582.450365] ffff88000003bba0 ffffffff810676bd ffff88000003bc20
> 0000000000000001
> [32582.450369] ffff88003684c800 ffff88003684caf8 ffff8800364a9800
> ffff88000003bc00
> [32582.450373] Call Trace:
> [32582.450378] [<ffffffff817199c4>] dump_stack+0x45/0x56
> [32582.450381] [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
> [32582.450384] [<ffffffff8106772c>] warn_slowpath_fmt+0x4c/0x50
> [32582.450405] [<ffffffffa012fd25>] ? intel_sdvo_get_hw_state+0x55/0xc0
> [i915]
> [32582.450423] [<ffffffffa011a16d>]
> intel_modeset_check_state+0x62d/0x780 [i915]
> [32582.450441] [<ffffffffa011a355>] intel_set_mode+0x25/0x30 [i915]
> [32582.450459] [<ffffffffa011abfb>] intel_crtc_set_config+0x7ab/0x9a0
> [i915]
> [32582.450463] [<ffffffff810428ad>] ? lapic_next_event+0x1d/0x30
> [32582.450477] [<ffffffffa000fe9d>]
> drm_mode_set_config_internal+0x5d/0xe0 [drm]
> [32582.450492] [<ffffffffa0012d87>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
> [32582.450503] [<ffffffffa0003c22>] drm_ioctl+0x502/0x630 [drm]
> [32582.450508] [<ffffffff81077dd2>] ? __set_task_blocked+0x32/0x70
> [32582.450513] [<ffffffff811cf810>] do_v...

[KeithG (grider-4)]

I started with commit c40e36... and worked back according to the git log. The last 'good' build was fb72a0... The next commit breaks it.

c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 bad
e651eab0af88aa7a281fe9e8c36c0846552aa7fc bad
7fb476c231bbc551ede5b4afb189d9ca5ab7406d bad
3500ed90b26a9935b943b5e2e4cd3226600d6b58 bad
9abd5f0555df6cd36130feb742f1def6d99c60fe bad
79b16641efabd14944dbfc2fde2ae1e8ae8413bc bad
fb72a0590b770f7da6a02bde6b8a147a3d9f6168 good

commit 79b16641efabd14944dbfc2fde2ae1e8ae8413bc
Author: Gregory CLEMENT <email address hidden>
Date: Fri Apr 12 13:57:44 2013 +0200

    clk: add device tree fixed-factor-clock binding support

    Add support for DT "fixed-factor-clock" binding to the common fixed
    factor clock support.

    Signed-off-by: Gregory CLEMENT <email address hidden>
    Tested-by: Christian Ruppert <email address hidden>
    Signed-off-by: Mike Turquette <email address hidden>

What is the next step?

aside: was I using Git bisect incorrectly? Shouldn't it have brought me here automatically? Using version numbers was a waste of time as ubuntu was using a yet lower version mumber than was visible when using the mainline kernel. The commits got me closer to the bad commit.

[KeithG (grider-4)]

I rebooted to 14.04 again and built the kernel from that commit, installed and rebooted 14.04 and the error still shows in the log. Previously, I was using 13.04 as the base. I guess I will continue to buils kernels backwards from here until it goes away. Any other suggestions? I wonder if this is the bug that breaks KMS with i915 for others as well.

[KeithG (grider-4)]

I have no clue what is going on. I have started building kernels from v3.8.13 and back. So far all fail. I am at v3.8.7 and still have the dmesg error. It is not clear from the ubuntu kernel to mainline map as to which is/should be the version that I have on there which works without error. The version lists as '3.8.0-19-generic'. There is no 'raring linux' listing. It appears that v3.8.8 maps to Ubuntu-lts-3.8.0-19.30, but when I built v3.8.8, I still get the error and do not when I boot it with the generic kernel. This is an x64 installation. I am building v3.8.7 right now and will see what happens with it.

[KeithG (grider-4)]

I kept seeing it and eventually built v3.8.0 and it 'appeared' to not show the error. I thought I had found it and started another bisect between the commits for v3.8.0 and v3.8.1, but when I tried to boot back to v3.8.0, the error in the log showed up. It was not there previously. Now if I reboot teh machine and select v3.8.0 I get the error, but earlier I was not. Very confused. The only kernel I can reliably boot in 13.04 and not get the error is the stock one: Ubuntu 3.8.0-19. Any hints on what may be going on?

Keith

[KeithG (grider-4)]

This is too far out of my league. I need more guidance. This bug appears to be imtermittent. I have certain kernels which have never exhibited this error in the dmesg. I have others which sometimes show it. I have built well over 30 kernels on this laptop and it is like trying to find a needle in a haystack. I now understand why the suggestion is to get an nvidia based graphics subsystem and not intel. I tried bisecting with 13.04 and got lost. I then tried with 12.04 and got to a pull that would not build (some USB comedi error). There has to be a better way to target this. I am back with 14.04, updated. It initially did not show the error now it does. When I resume, I now get the black screen with only the cursor showing. I can switch to a vt, but it is still not right. Others have seen that it it non-responsive. I can ssh into it when it is resumed.

frustrated

Keith

[KeithG (grider-4)]

fwiw, I grabbed the latest kernel and the bug is still there. I built v3.16.0-rc5 and still get this filling the log:

 l WARNING: CPU: 1 PID: 1143 at drivers/gpu/drm/i915/intel_display.c:10101 intel_modeset_check_state+0x5f3/0x7a0 [i915]()
[ 115.283641] encoder's hw state doesn't match sw tracking (expected 0, found 1)
[ 115.283643] Modules linked in: pci_stub(E) vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ctr(E) ccm(E) bnep(E) rfcomm(E) bluetooth(E) snd_hda_codec_idt(E) snd_hda_codec_hdmi(E) snd_hda_codec_generic(E) uvcvideo(E) videobuf2_vmalloc(E) arc4(E) videobuf2_memops(E) videobuf2_core(E) v4l2_common(E) videodev(E) snd_hda_intel(E) snd_hda_controller(E) b43(E) snd_hda_codec(E) snd_hwdep(E) snd_pcm(E) snd_seq_midi(E) snd_seq_midi_event(E) snd_rawmidi(E) bcma(E) snd_seq(E) snd_seq_device(E) gpio_ich(E) mac80211(E) dell_wmi(E) sparse_keymap(E) dell_laptop(E) snd_timer(E) dcdbas(E) coretemp(E) cfg80211(E) joydev(E) i915(E) snd(E) serio_raw(E) drm_kms_helper(E) drm(E) ssb_hcd(E) lpc_ich(E) soundcore(E) i2c_algo_bit(E) wmi(E) mac_hid(E) video(E) parport_pc(E) ppdev(E) lp(E) parport(E) psmouse(E) ahci(E) libahci(E) ssb(E) sky2(E)
[ 115.283693] CPU: 1 PID: 1143 Comm: Xorg Tainted: G W OE 3.16.0-rc5-1404+ #2
[ 115.283695] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009
[ 115.283697] 0000000000000009 ffff8800b8577a10 ffffffff8173bd3a ffff8800b8577a58
[ 115.283701] ffff8800b8577a48 ffffffff8106c82d 0000000000000001 ffff8800b8577ad0
[ 115.283705] ffff8800365be310 ffff880036817800 ffff8800365be000 ffff8800b8577aa8
[ 115.283708] Call Trace:
[ 115.283716] [<ffffffff8173bd3a>] dump_stack+0x45/0x56
[ 115.283721] [<ffffffff8106c82d>] warn_slowpath_common+0x7d/0xa0
[ 115.283724] [<ffffffff8106c89c>] warn_slowpath_fmt+0x4c/0x50
[ 115.283747] [<ffffffffa01bcd85>] ? intel_sdvo_get_hw_state+0x55/0xc0 [i915]
[ 115.283768] [<ffffffffa0195cc3>] intel_modeset_check_state+0x5f3/0x7a0 [i915]
[ 115.283790] [<ffffffffa0195f05>] intel_set_mode+0x25/0x30 [i915]
[ 115.283811] [<ffffffffa01964d7>] intel_release_load_detect_pipe+0xa7/0xf0 [i915]
[ 115.283833] [<ffffffffa01c1711>] intel_tv_detect+0x311/0x550 [i915]
[ 115.283842] [<ffffffffa010c9c3>] drm_helper_probe_single_connector_modes_merge_bits+0x293/0x3a0 [drm_kms_helper]
[ 115.283849] [<ffffffffa010cae3>] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper]
[ 115.283871] [<ffffffffa00b258f>] drm_mode_getconnector+0x3cf/0x440 [drm]
[ 115.283883] [<ffffffffa00a3984>] drm_ioctl+0x1a4/0x630 [drm]
[ 115.283889] [<ffffffff811e29d0>] do_vfs_ioctl+0x2e0/0x4c0
[ 115.283893] [<ffffffff810a3964>] ? vtime_account_user+0x54/0x60
[ 115.283896] [<ffffffff811e2c31>] SyS_ioctl+0x81/0xa0
[ 115.283900] [<ffffffff817446ff>] tracesys+0xe1/0xe6
[ 115.283902] ---[ end trace 225c135744ce54f4 ]---

# cat /sys/module/i915/parameters/modeset
-1

this with a fresh reinstall of xubuntu 14.04

Keith

[KeithG (grider-4)]

Since I was unable to successfully use git bisect, I decided to take another tack. I am running 14.04 no mods or edits, just a simple unstall of Xubuntu. I installed the b43 driver so the wifi works. If I try to install and 'install updates', the install crashes. I installed then did an 'apt-get dist-upgrade'. I tried the mainline kernels I have built so far of the 3.x.0 revisons and have this to share:

v3.6.0 is the last '0' rev to work suspend/resume and not have any warnings in the dmesg. i built it under 12.04
v3.7.0 to v3.9.0 will suspend and resume, but have the error in the dmesg
v3.10.0 boots to busybox

still testing others

Keith

[KeithG (grider-4)]

Can you explain something to me. Does v3.6.0-rc7 come before v3.6.0? I thought that release candidates preceeded the release. I am running yet another bisect, this time good is v3.6 and bad is v3.7. I cannot tell where bisect is in the tree while it is running, it just reports UUIDs as it runs, but I just built a kernel at step 5 in the bisect which is v3.6.0-rc7 which appears to me to actually come before my last 'good' release and does not appear to fall between the endpoints of my bisect. What am I missing?

[KeithG (grider-4)]

Now I am at step 8 and the kernel is linux-image-3.5.0-rc4. What am I doing wrong? I would guess that the first bisect would be 3.6.x (somewhere between v3.6.0 and v3.7.0).

[KeithG (grider-4)]

I finished the bisect. I am running xubuntu 14.04. I pulled mainline kernels v3.6 which worked without error and v3.7 which exhibited the error. I then bisected between the 2. It took 14 steps and concluded with this which makes more sense:

24929352481f085c5f85d4d4cbc919ddf106d381 is the first bad commit
commit 24929352481f085c5f85d4d4cbc919ddf106d381
Author: Daniel Vetter <email address hidden>
Date: Mon Jul 2 20:28:59 2012 +0200

    drm/i915: read out the modeset hw state at load and resume time

    ... instead of resetting a few things and hoping that this will work out.

    To properly disable the output pipelines at the initial modeset after
    resume or boot up we need to have an accurate picture of which outputs
    are enabled and connected to which crtcs. Otherwise we risk disabling
    things at the wrong time, which can lead to hangs (or at least royally
    confused panels), both requiring a walk to the reset button to fix.

    Hence read out the hw state with the freshly introduce get_hw_state
    functions and then sanitize it afterwards.

    For a full modeset readout (which would allow us to avoid the initial
    modeset at boot up) a few things are still missing:
    - Reading out the mode from the pipe, especially the dotclock
      computation is quite some fun.
    - Reading out the parameters for the stolen memory framebuffer and
      wrapping it up.
    - Reading out the pch pll connections - luckily the disable code
      simply bails out if the crtc doesn't have a pch pll attached (even
      for configurations that would need one).

    This patch here turned up tons of smelly stuff around resume: We
    restore tons of register in seemingly random way (well, not quite, but
    we're not too careful either), which leaves the hw in a rather
    ill-defined state: E.g. the port registers are sometimes
    unconditionally restore (lvds, crt), leaving us with an active
    encoder/connector but no active pipe connected to it. Luckily the hw
    state sanitizer detects this madness and fixes things up a bit.

    v2: When checking whether an encoder with active connectors has a crtc
    wire up to it, check for both the crtc _and_ it's active state.

    v3:
    - Extract intel_sanitize_encoder.
    - Manually disable active encoders without an active pipe.

    v4: Correclty fix up the pipe<->plane mapping on machines where we
    switch pipes/planes. Noticed by Chris Wilson, who also provided the
    fixup.

    v5: Spelling fix in a comment, noticed by Paulo Zanoni

    Reviewed-by: Jesse Barnes <email address hidden>
    Signed-Off-by: Daniel Vetter <email address hidden>

:040000 040000 27592a2f94f6651cf1e96e8826c0d365de7b298c 416fd34aacc0e3f8248a6ff4a1095157f24ad4dd M drivers

What next?

[KeithG (grider-4)]

The dmesg from this version of the kernel (different line number in the *.c file) is attached.

Keith

[penalvch (penalvch)]

KeithG, last check, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc6-utopic/ and advise to the results?

[KeithG (grider-4)]

yes, it is still present. dmesg attached.

[penalvch (penalvch)]

KeithG, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[KeithG (grider-4)]

3.16.0 - still messages in the log, but it will now suspend and resume with ubuntu GNOME 14.04 and the 3.16.0 kernel

[KeithG (grider-4)]

I don't think it is 'fixed' as I still get my log filled with the error message, but I can use hardware acceleration and it will suspend and resume.

[penalvch (penalvch)]

KeithG, the scope of this report is your ability to suspend/resume.

[penalvch (penalvch)]

KeithG, the next step is to fully reverse commit bisect from kernel 3.16-rc6 to 3.16 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

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

[KeithG (grider-4)]

? I do not fully understand your request. As you said, this was a failure to resume bug. That bug has been resolved. I am currently running the current kernel with ubuntu 14.04 and allowing it to update as time progresses. (apt-get dist-upgrade)

I still have tons of errors in my dmesg. I have reported this to the kernel team and it has been assigned to David Vetter but still has not been resolved.

https://bugzilla.kernel.org/show_bug.cgi?id=81291

Am I missing something?

Keith

[penalvch (penalvch)]

KeithG, just to clarify, if you may now resume in the default trusty kernel (not upstream) then please feel free to mark this bug report status Invalid.

Regarding errors in dmesg, this is out of scope for this report. However, if the errors are correlated to some sort of impact on features, performance, etc. please feel free to file a new report via a terminal:
ubuntu-bug linux

[J.G (jg-imbert)]

The report by Keith wasn't invalid. ALL Ubuntu since 14.XX and derivates of it (like Linux Mint 17) get this issue. The result of this issue is a total freeze of the computer (all devices when the freeze comes are disabled).

I got the same log as KeithG. Apparently X.Org was the source of the issue :
http://ubuntuforums.org/showthread.php?t=2252748&p=13168746#post13168746

PC specs :
- Intel(R) Core(TM) i7 CPU (2.80GHz)
- 8 Go RAM
- NVIDIA GeForce GT 230 (using nvidia 340.58)
- Kernel 3.18.X

xserver-xorg-video-nouveau and others packages that use the "Nouveau" driver were removed to the system to avoid conflict. But the issue is still here.

The computer doesn't freeze on previous versions of L/X/Ubuntu (13.04 for instance)

[J.G (jg-imbert)]

According to this, and after execute "uname -r" to see versions of kernel that they are, freezes now appear to occur very frequently/everyday with kernel versions after 3.2.1

Report on Fedora :
https://bugzilla.redhat.com/show_bug.cgi?id=786879

<email address hidden> 2012-02-03 05:25:08 EST
Got frozen out again today: got the following log from /var/log/messages:
While these failures were happening very infrequently with previous kernels, they now appear to occur very frequently/everyday since upgrade to 3.2.1-3.fc16.i686

[J.G (jg-imbert)]

How can we use an old version of kernel package to test the report of brendan on Fedora?

[penalvch (penalvch)]

J.G, please do not assign yourself to a bug report unless you are going to release a fix patch imminently, as outlined in https://wiki.ubuntu.com/Bugs/Status .

Despite this, if you have a problem in Ubuntu, and so your hardware and problem may be tracked, 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

[J.G (jg-imbert)]

So why you won't repair this bug ? It's useless to change the status as incomplete. The status is confirmed by these informations. The bug came from one of these cases : Kernel, X.Org or the both. The bug is not on the hardware but on the software.

The bug is confirmed too around the Web in ALL distributions that uses the new kernel. So I will try to change it. It isn't normal that you published a version that you don't verify it. I can say that Ubuntu 14.XX (and derivates specially Lubuntu that adds a bad configuration system of the LXDE environment) are garbage versions. I regret the previous version like 12.04 and 13.04 that works better without issue like freezes.

[J.G (jg-imbert)]

And it's useless to create a new report. The bug, even if I use a different video card (here NVIDIA), is the same for all video cards compagnies (ATI, Intel, NVIDIA, ...) like KeithG had.

[J.G (jg-imbert)]

The log file :

Nov 17 16:57:36 jackobo-MS-7616 kernel: [ 41.127845] nvidia 0000:01:00.0: irq 35 for MSI/MSI-X
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.799569] NVRM: Your system is not currently configured to drive a VGA console
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.799575] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.799578] NVRM: requires the use of a text-mode VGA console. Use of other console
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.799581] NVRM: drivers including, but not limited to, vesafb, may result in
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.799583] NVRM: corruption and stability problems, and is not supported.
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921815] ------------[ cut here ]------------
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921841] WARNING: CPU: 1 PID: 1603 at /home/apw/COD/linux/drivers/gpu/drm/drm_ioctl.c:143 drm_set_busid.isra.4+0xdf/0xf0 [drm]()
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921928] No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921930] Modules linked in: bnep rfcomm bluetooth binfmt_misc nvidia(POE) snd_hda_codec_realtek snd_hda_codec_generic joydev snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi gpio_ich snd_seq_midi_event snd_rawmidi snd_seq dm_multipath snd_seq_device snd_timer drm snd coretemp soundcore kvm_intel kvm scsi_dh serio_raw i7core_edac lpc_ich edac_core mac_hid parport_pc ppdev hid_wiimote ff_memless lp parport dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid hid psmouse firewire_ohci ahci r8169 firewire_core libahci mii crc_itu_t
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921988] CPU: 1 PID: 1603 Comm: Xorg Tainted: P W OE 3.18.0-031800rc4-generic #201411091835
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921991] Hardware name: MEDIONPC MS-7616/MS-7616, BIOS A7616MLN.10F 01/15/2010
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921993] 000000000000008f ffff8800ba56fcd8 ffffffff8179f058 0000000000000007
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921998] ffff8800ba56fd28 ffff8800ba56fd18 ffffffff8106eafc ffff8800b76fbc00
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922002] ffff880036018300 ffff8800b75c1800 00000000ffffffea ffff8800ba56fe30
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922007] Call Trace:
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922016] [<ffffffff8179f058>] dump_stack+0x46/0x58
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922023] [<ffffffff8106eafc>] warn_slowpath_common+0x8c/0xc0
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922028] [<ffffffff8106ebe6>] warn_slowpath_fmt+0x46/0x50
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922045] [<ffffffffc039023f>] drm_set_busid.isra.4+0xdf/0xf0 [drm]
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922059] [<ffffffffc03902a2>] drm_setversion+0x52/0xc0 [drm]
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.922074] [<ffffffffc038fdb7>] drm_ioctl+0x257/0x590 [drm]
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ ...

[J.G (jg-imbert)]

See this :

Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921988] CPU: 1 PID: 1603 Comm: Xorg Tainted: P W OE 3.18.0-031800rc4-generic #201411091835

If you don't see that Xorg or Kernel have an issue, so I don't know how to prove it to you.....

[penalvch (penalvch)]

J.G, just to clarify, this report is not scoped to you, your hardware, or your problem. if you want your bug addressed, please again see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/comments/67 .

[Gurvinder Dadyala (gurvinder)]

Hi there, I am also facing the same issue. I have Dell Inspiron 1525 running 14.04.1 LTS and kernel version 3.13.0-39-generic.
System becomes unusable completly and screen goes off as well. Following is what i have found in dmesg

[ 47.428521] WARNING: CPU: 1 PID: 1146 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:4197 intel_modeset_check_state+0x76c/0x780 [i915]()
[ 47.428523] wrong connector dpms state
[ 47.428525] Modules linked in: ctr ccm bnep rfcomm bluetooth gpio_ich snd_hda_codec_idt snd_hda_codec_hdmi dell_wmi sparse_keymap uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dell_laptop dcdbas dm_multipath scsi_dh coretemp arc4 r852 joydev sm_common serio_raw nand nand_ecc nand_bch bch iwl3945 nand_ids iwlegacy mtd r592 mac80211 memstick lpc_ich cfg80211 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event mac_hid snd_rawmidi snd_seq snd_seq_device snd_timer snd i915 soundcore wmi video drm_kms_helper drm i2c_algo_bit parport_pc ppdev lp parport hid_generic usbhid hid psmouse sdhci_pci firewire_ohci sdhci firewire_core ahci crc_itu_t libahci sky2
[ 47.428589] CPU: 1 PID: 1146 Comm: Xorg Tainted: G W 3.13.0-39-generic #66-Ubuntu
[ 47.428591] Hardware name: Dell Inc. Inspiron 1525 /0WP007, BIOS A17 10/27/2009
[ 47.428594] 0000000000000009 ffff8800acfcb9f8 ffffffff8171ece7 ffff8800acfcba40
[ 47.428599] ffff8800acfcba30 ffffffff8106773d ffff8800afcdb000 ffff8800b75dd000
[ 47.428602] ffff8800b84a0000 ffff8800b84a02f8 0000000000000012 ffff8800acfcba90
[ 47.428607] Call Trace:
[ 47.428615] [<ffffffff8171ece7>] dump_stack+0x45/0x56
[ 47.428621] [<ffffffff8106773d>] warn_slowpath_common+0x7d/0xa0
[ 47.428624] [<ffffffff810677ac>] warn_slowpath_fmt+0x4c/0x50
[ 47.428651] [<ffffffffa018e60c>] intel_modeset_check_state+0x76c/0x780 [i915]
[ 47.428675] [<ffffffffa018e6b5>] intel_set_mode+0x25/0x30 [i915]
[ 47.428698] [<ffffffffa018e786>] intel_release_load_detect_pipe+0xc6/0xf0 [i915]
[ 47.428725] [<ffffffffa01b6859>] intel_tv_detect+0x359/0x500 [i915]
[ 47.428735] [<ffffffffa013325b>] drm_helper_probe_single_connector_modes+0x1eb/0x380 [drm_kms_helper]
[ 47.428761] [<ffffffffa00de617>] drm_mode_getconnector+0x417/0x480 [drm]
[ 47.428766] [<ffffffff8108ea82>] ? __hrtimer_start_range_ns+0x1a2/0x3a0
[ 47.428781] [<ffffffffa00cfc22>] drm_ioctl+0x502/0x630 [drm]
[ 47.428787] [<ffffffff81077eb2>] ? __set_task_blocked+0x32/0x70
[ 47.428794] [<ffffffff811d03c0>] do_vfs_ioctl+0x2e0/0x4c0
[ 47.428799] [<ffffffff811d0621>] SyS_ioctl+0x81/0xa0
[ 47.428803] [<ffffffff8172f7ed>] system_call_fastpath+0x1a/0x1f
[ 47.428806] ---[ end trace ce38d32fc85a4372 ]---

How can i solve this?

[penalvch (penalvch)]

Gurvinder Dadyala, 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

[Gurvinder Dadyala (gurvinder)]

As per your instructions, I have submitted bug report. Following is the link

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1406982

[KeithG (grider-4)]

Just upgraded to 15.04. I still get the error and sometimes it will not shut down and takes a long time to reboot.

Is this just that the i915 driver is not very good or that my hardware is not well supported?

# lspci
...
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
...

# dmesg | tail -28
[ 50.714016] ------------[ cut here ]------------
[ 50.714036] WARNING: CPU: 1 PID: 967 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:10801 intel_modeset_check_state+0x3c8/0x6a0 [i915]()
[ 50.714037] encoder's hw state doesn't match sw tracking (expected 0, found 1)
[ 50.714069] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ctr ccm binfmt_misc arc4 uvcvideo b43 snd_hda_codec_idt videobuf2_vmalloc snd_hda_codec_hdmi videobuf2_memops snd_hda_codec_generic videobuf2_core i915 snd_hda_intel v4l2_common snd_hda_controller bcma videodev snd_hda_codec dell_wmi mac80211 media snd_hwdep sparse_keymap gpio_ich snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi r852 dell_laptop sm_common dcdbas cfg80211 nand nand_ecc i8k nand_bch snd_seq bch coretemp r592 nand_ids mtd snd_seq_device drm_kms_helper memstick snd_timer joydev drm ssb_hcd snd serio_raw soundcore i2c_algo_bit lpc_ich shpchp wmi mac_hid video sunrpc parport_pc ppdev lp parport autofs4 hid_generic usbhid hid ahci psmouse libahci firewire_ohci pata_acpi sdhci_pci firewire_core sdhci
[ 50.714071] crc_itu_t ssb sky2
[ 50.714073] CPU: 1 PID: 967 Comm: Xorg Tainted: G W 3.19.0-15-generic #15-Ubuntu
[ 50.714074] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009
[ 50.714076] ffffffffc07fae10 ffff8800aa5577e8 ffffffff817c2205 00000000807e807e
[ 50.714078] ffff8800aa557838 ffff8800aa557828 ffffffff8107595a 0000000000000002
[ 50.714080] 0000000000000001 ffff8800ba2bfb60 ffff8800ba2df000 ffff8800ba2bfb30
[ 50.714080] Call Trace:
[ 50.714083] [<ffffffff817c2205>] dump_stack+0x45/0x57
[ 50.714085] [<ffffffff8107595a>] warn_slowpath_common+0x8a/0xc0
[ 50.714087] [<ffffffff810759d6>] warn_slowpath_fmt+0x46/0x50
[ 50.714106] [<ffffffffc07a6e18>] intel_modeset_check_state+0x3c8/0x6a0 [i915]
[ 50.714126] [<ffffffffc07a84dc>] intel_crtc_set_config+0xd9c/0xf70 [i915]
[ 50.714140] [<ffffffffc043ee36>] drm_mode_set_config_internal+0x66/0x100 [drm]
[ 50.714147] [<ffffffffc049dd18>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper]
[ 50.714154] [<ffffffffc049fd89>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper]
[ 50.714156] [<ffffffff8101e74a>] ? native_sched_clock+0x2a/0x90
[ 50.714163] [<ffffffffc049fe02>] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper]
[ 50.714182] [<ffffffffc07b429a>] intel_fbdev_set_par+0x1a/0x60 [i915]
[ 50.714185] [<ffffffff814339da>] fb_set_var+0x18a/0x410
[ 50.714187] [<ffffffff8109eb89>] ? check_preempt_curr+0x89/0xa0
[ 50.714189] [<ffffffff810a6108>] ? __enqueue_entity+0x78/0x80
[ 50.714191] [<ffffffff810adad0>] ? enqueue_ent...

[penalvch (penalvch)]

KeithG, to confirm this is a downstream only issue, could you please test the latest mainline kernel (4.1.1) and advise to the results?

[KeithG (grider-4)]

Just loaded ubuntu 15.10 (kernel 4.2.0-18-generic) and it is still there.

Interestingly, I have this as well:
CPU: 1 PID: 1276 Comm: Xorg Tainted: G W 4.2.0-18-generic #22-Ubuntu.

I do not know why it is tainted as I did not install any private modules. on the 'Software & Updates" "Additional Drivers' none are activated. This is with a clean install, not an update. What further information do I need to send?

Keith

[penalvch (penalvch)]

KeithG:
>"I do not know why it is tainted..."

It's a kernel that has been modified from what was provided upstream.

>" What further information do I need to send?"

It was requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/comments/76 to test the latest mainline kernel. This is now 4.4-rc2+cod1.

[KeithG (grider-4)]

Christopher,

I grabbed kernel 4.4.0-040400rc3-generic as it shows as the latest. I installed it and get the same messages in the dmesg log. I do note that the fans are not running so fast. I have been having problems where it will overheat and shut down. Never had that problem with 15.04 or earlier. It seems more 'normal' with this kernel.

[penalvch (penalvch)]

KeithG, could you please test drm-intel-nightly and advise to the results?

[KeithG (grider-4)]

I still get this:

[ 1.968043] ------------[ cut here ]------------
[ 1.968074] WARNING: CPU: 0 PID: 85 at /home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1216 drm_wait_one_vblank+0x1b5/0x1c0 [drm]()

And it is way laggy. 15.10 is unusable for me with any of these kernels (stock, latest, latest drm) I will go back to 15.04 and wait for a fix. If I can asdd anything more, I can always boot back into this as it is on a different partition.

[penalvch (penalvch)]

KeithG, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (TO Daniel Vetter and Jani Nikula CC intel-gfx)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

[smilingfrog (smilingfrog)]

KeithG,
I have the same problem with my Dell Inspiron 1525. Upgraded from Debian Wheezy to Debian Jessie, and started getting very similar error messages:

Dec 26 09:57:56 localhost kernel: [ 1017.555709] Pid: 1212, comm: Xorg Tainted: G W 3.8.0 #1

Can you post your kernel .config file? I'd like to try to bisect the kernel for the upstream bug to see if I can replicate the errors.
From posts last year, you seem to have had the last good kernel be 3.8, but I get the bug with that as well. Can you recall the last kernel version that did not give you this bug?

[ethanay (ethan-y-us)]

Adding dmesg for latest mainline kernel at http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/ -- the error differs slightly in reporting. Will attach 3.19 snippet as well.

[ethanay (ethan-y-us)]

see attached Kernel 3.19 dmesg snippet (for comparison).

[ethanay (ethan-y-us)]

attaching additional debug info

[ethanay (ethan-y-us)]

https://bugzilla.kernel.org/show_bug.cgi?id=81291 might be related?

[ethanay (ethan-y-us)]

also reported here: https://bugs.freedesktop.org/show_bug.cgi?id=93511

[KeithG (grider-4)]

ethany,

I do not really remember. Try 13.04 (and 12.04 if it is still in 13.04). It was one of those, IIRC, that did not have it. Problem is that so much has changed in the kernel since then. I went through a huge kernel bisect project to then be told to report it to the kernel i915 group and got no interest. I am over it, now. I am convinced that the i915 driver will never be fixed for our particular hardware as it is so old. <rant> Nobody really cares. Typical 80/20. Get it 80% of the way there then loose interest in doing the rest of the 80% required to get it 'right'. Typical of all open source projects. </rant>

As for the last time I tried 15.10, on all of my machines (3 different hardware, processors, etc), the system just randomly suspends. Without warning and nothing weird shows up in the log. Just browsing in firefox or running an app and then bam instant suspend. It all comes back when powered on, but not really usable. I just updated and am trying again on one machine and see if it is fixed. No bug reports relate to this bug, either. It just did it again. Suspended without warning while I was typing this.

The latest kernel update for 15.10
4.2.0-23-generic

shows this:
------------[ cut here ]------------
[ 163.795945] WARNING: CPU: 1 PID: 1162 at /build/linux-AFqQDb/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12256 intel_modeset_check_state+0x3ab/0x6d0 [i915]()
[ 163.795947] encoder's hw state doesn't match sw tracking (expected 0, found 1)
[ 163.795948] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache binfmt_misc arc4 uvcvideo b43 videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common snd_hda_codec_idt videodev snd_hda_codec_generic bcma snd_hda_codec_hdmi media dell_wmi mac80211 sparse_keymap snd_hda_intel r852 gpio_ich dell_laptop sm_common snd_hda_codec nand snd_hda_core nand_ecc snd_hwdep snd_pcm nand_bch dcdbas snd_seq_midi bch snd_seq_midi_event snd_rawmidi nand_ids cfg80211 dell_smm_hwmon mtd snd_seq snd_seq_device ssb_hcd input_leds r592 joydev snd_timer serio_raw memstick snd lpc_ich soundcore shpchp mac_hid coretemp sunrpc parport_pc ppdev lp parport autofs4 hid_generic usbhid hid psmouse i915 ahci libahci sdhci_pci firewire_ohci sdhci pata_acpi ssb firewire_core crc_itu_t sky2 i2c_algo_bit
[ 163.796030] wmi drm_kms_helper drm video
[ 163.796036] CPU: 1 PID: 1162 Comm: Xorg Tainted: G W 4.2.0-23-generic #28-Ubuntu
[ 163.796044] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009
[ 163.796048] 0000000000000000 000000004b9aede5 ffff8800b9e9f8f8 ffffffff817e94c9
[ 163.796052] 0000000000000000 ffff8800b9e9f950 ffff8800b9e9f938 ffffffff8107b3d6
[ 163.796055] 01ff8800b9e9f948 ffff8800358ce000 0000000000000001 ffff8800358ce350
[ 163.796058] Call Trace:
[ 163.796063] [<ffffffff817e94c9>] dump_stack+0x45/0x57
[ 163.796066] [<ffffffff8107b3d6>] warn_slowpath_common+0x86/0xc0
[ 163.796069] [<ffffffff8107b465>] warn_slowpath_fmt+0x55/0x70
[ 163.796093] [<ffffffffc01b9ceb>] intel_modeset_check_state+0x3ab/0x6d0 [i915]
[ 163.796120] [<ffffffffc01ba0ca>] intel_set_mode+0x4a/0x60 [i915]
[ 163.796146] [<ffffffffc01ba806>...

[ethanay (ethan-y-us)]

It did not exist in 12.04. IIRC, the graphical artifacts symptomatic of
the issue for me appeared during an upgrade in Elementary OS Freya (based
on Ubuntu 14.04) from kernel 3.13 to 3.19 -- an upgrade intended to fix
another kernel bug! :P

I get no random suspend issues. The possibility exists for hardware
problems. I had to bypass my hardware wireless switch because it started
randomly turning the card on and off. Maybe something similar is happening
via a suspend parameter on your computer (did you try registering and
logging hardware keypresses? Those showed up with my wireless issue)

This bug seems fairly well confirmed as a software/kernel/driver issue,
though. Let me know if there's somewhere I can make noise and verify that
this is a problem.

ethan

“A society grows great when its elders plant trees whose shade they know
they shall never sit in.” -- an ironic Greek proverb

On Sat, Jan 9, 2016 at 10:55 AM, KeithG <email address hidden> wrote:

> ethany,
>
> I do not really remember. Try 13.04 (and 12.04 if it is still in 13.04).
> It was one of those, IIRC, that did not have it. Problem is that so much
> has changed in the kernel since then. I went through a huge kernel
> bisect project to then be told to report it to the kernel i915 group and
> got no interest. I am over it, now. I am convinced that the i915 driver
> will never be fixed for our particular hardware as it is so old. <rant>
> Nobody really cares. Typical 80/20. Get it 80% of the way there then
> loose interest in doing the rest of the 80% required to get it 'right'.
> Typical of all open source projects. </rant>
>
> As for the last time I tried 15.10, on all of my machines (3 different
> hardware, processors, etc), the system just randomly suspends. Without
> warning and nothing weird shows up in the log. Just browsing in firefox
> or running an app and then bam instant suspend. It all comes back when
> powered on, but not really usable. I just updated and am trying again on
> one machine and see if it is fixed. No bug reports relate to this bug,
> either. It just did it again. Suspended without warning while I was
> typing this.
>
> The latest kernel update for 15.10
> 4.2.0-23-generic
>
> shows this:
> ------------[ cut here ]------------
> [ 163.795945] WARNING: CPU: 1 PID: 1162 at
> /build/linux-AFqQDb/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12256
> intel_modeset_check_state+0x3ab/0x6d0 [i915]()
> [ 163.795947] encoder's hw state doesn't match sw tracking (expected 0,
> found 1)
> [ 163.795948] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs
> lockd grace fscache binfmt_misc arc4 uvcvideo b43 videobuf2_vmalloc
> videobuf2_memops videobuf2_core v4l2_common snd_hda_codec_idt videodev
> snd_hda_codec_generic bcma snd_hda_codec_hdmi media dell_wmi mac80211
> sparse_keymap snd_hda_intel r852 gpio_ich dell_laptop sm_common
> snd_hda_codec nand snd_hda_core nand_ecc snd_hwdep snd_pcm nand_bch dcdbas
> snd_seq_midi bch snd_seq_midi_event snd_rawmidi nand_ids cfg80211
> dell_smm_hwmon mtd snd_seq snd_seq_device ssb_hcd input_leds r592 joydev
> snd_timer serio_raw memstick snd lpc_ich soundcore shpchp mac_hid coretemp
> sunrpc parport_pc ...

[KeithG (grider-4)]

Fix released! Awesome. Is there a link to anything that will allow me to verify that it is fixed? Is it in the current 16.04 kernel? 16.10? 17.04? Upstream?

Thanks.

Keith