[Dell Inspiron 1525] Ubuntu freezes when lid closed

[Pavel Selivanov]

Hi. I'm using Dell Inspiron 1525 for several years and it was used with Ubuntu since 10.04 or so.

After upgrading from 13.10 to 14.04 my PC started to freeze completely (no response from anything, requires hard reboot) if I'm closing the lid or display turning off due to inactivity timeout. I also had this problem after wake from suspend, but recently got kernel update and looks like it was fixed (no freezes after wake up). I tried fresh install of 14.04 that I'm using right now, but it doesn't help.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr 22 02:07:31 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:022f]
   Subsystem: Dell Device [1028:022f]
InstallationDate: Installed on 2014-04-20 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Apr 22 01:39:40 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 9076
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2

[Pavel Selivanov (muiriled)]

After updates i got today screen is able to turn off an on by inactivity timeout successfully, without freezing the system.

If the behaviour of lid is to suspend laptop, than closing it suspends successfully. But wakeups from suspend are randomly freezyng the system or not.

If the behaviour of lid is to 'do nothing'- system freezes as soon as lid closes.

[Pavel Selivanov (muiriled)]

Right now my BIOS is A16 and I had zero problems with it with all the previous ubuntus since 9.* series.

A17 has only one fix in it:

Fixes/Enhancements
------------------
(1) Change pre-charge time out from 2hr to 6hr.

So, it doesn't seem it will fix anything, but I'll try to update as soon as I figure out of how to apply their .exe flash utility.

[Pavel Selivanov (muiriled)]

Ok, I updated BIOS and the output Christopher requested is:
A17
10/27/2009

I made another series of experiments. In short, bios update didn't help at all.

If I'm not logged in system, so just lightdm works: 10 out of 10 the system is able to go to sleep after lid is closed and successfully wake up after i opened the lid.

Logging in default Unity:

If I'm setting the 'suspend' option in power settings for the lid, the system looks like successfully going to sleep every time, but just 3 of 10 was able to wake up, complete freeze other 7.

If I'm setting 'do nothing' for the lid on AC power, closing of lid successfully turns off display and system still functions without problems (i used a music player and ssh connection to monitor), but as soon as I'm opening lid- complete system freeze.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Pavel Selivanov, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.15-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Pavel Selivanov (muiriled)]

Christopher, I just tried 3.15 rc1 and rc2 as well as 3.14.0-997 and looks like these kernels require some xorg upgrade since I got a blank screen as soon as xorg starts (and actually some green line artifacts while booting as well). OS is working, but display just turns off so I wasn't able to test anything.

I also tried 3.13.11-031311. This one starts well, but lid opening still results in a complete freeze.

Maybe some directions of how to fix 3.15 series? (I had no errors during installation except my wifi card driver wasn't able to compile).

[Pavel Selivanov (muiriled)]

Well, no idea why, but after several tries and by removing 'quiet' and 'splash' settings from grub I successfully got my lightdm in 3.15.0-031500rc2-generic.

The bug with lid still exists- complete freeze while opening.

[Pavel Selivanov (muiriled)]

It was actually not quiet and splash but uncommenting of GRUB_TERMINAL=console in /etc/default/grub allows me to somehow get a working display in xorg (maybe I should create another bug for this to be fixed?).

So I also tried 3.15-rc3. It's marked for 'utopic', but I found that it's partially fixes the issue.

Opening lid now just results in a display still turned off and keyboard not working, but the system is working and accessible through ssh.

[penalvch (penalvch)]

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

[Žygimantas Beručka (zygis)]

I'm having the same issue with the same Inspiron 1525. I have also tried booting with mainline 3.14.1{,2}, but the issue is still present in these versions. I haven't tried 3.15rc as of yet since the Broadcom wireless kernel module fails to build with it.

I just tried, however, running the 3.11.0-20-generic kernel which is a leftover on the disk from the 13.10. With this version, I have to admit, resume from suspend works just fine.

[Žygimantas Beručka (zygis)]

I also noticed that if I try to suspend the system *before* actually logging in into a Unity session, that is, while lightdm alone is running, resume from suspend works flawlessly. But once I login to a Unity/compiz session, there's no comming back from a suspend.

[Žygimantas Beručka (zygis)]

I have some results from my investigation. I just tried a number of mainline builds: 3.13rc1, 3.13.{0,6,8,9,11}. With all of them, that is, from the first RC to the most current release in the 3.13 series, resuming works flawlessly. It is also of note, as have already been said above, that 3.14.{1,2} mainline builds are problematic. I haven't tried any of the 3.14rc mainline builds though.

This suggests that the custom Ubuntu Trusty kernel, which at the moment of writing is at version 3.13.0-24.46, might include something bad imported from outside the 3.13 tree.

[Žygimantas Beručka (zygis)]

Bad news. I just removed all the kernels I tested except the last one (3.13.11), and after some time tried to suspend it again. It froze again while coming back from a suspend. If this bug likes to hide like this and activates just on some condition, it will be hard to nail it down. I will try, howver, running for a longer time some earlier ones, say, 3.13.8 for now.

[penalvch (penalvch)]

Žygimantas Beručka, 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

[Žygimantas Beručka (zygis)]

Thanks, Christopher. I had wanted to submit those logs apport collects on a fresh boot after the freeze way before, but no matter how many times I tried, once I press the submit button, it would just close and nothing happens. Will try to do it later the way you're suggesting.

And concerning my last comment, after running 3.13.8 for a longer time and trying to suspend the system(i.e., in contrast to suspending just after logging into a Unity session), it's hit by the bug again. This probably means it is necessary to test earlier 3.13 (or even 3.12, I have no idea) releases while letting the system run for somewhat longer periods.

Meanwhile, the issue is temporarily bypassed by going back to the Saucy's 3.11 build.

[Žygimantas Beručka (zygis)]

Christopher, I reported the same issue as bug #1315277

[Pavel Selivanov (muiriled)]

Back from vacations and it's looks like the issue is not or not entirely in kernel.

I'm back to 3.13.0-24-generic and just installed gnome-shell 3.12 and the problem is gone. I can now safely close and open the lid.

So, looks like that at least a 'trigger' for the freeze is somewhere in Unity/compiz.

Gonna try again several different kernels.

[Pavel Selivanov (muiriled)]

Ok I tried 3.13.11-031311-generic and with gnome-shell it works just fine. I'm able to wake up a system from sleep with power button or opening lid. Closing/opening lid works fine, no freezes detected in a series of 6 sleep/wakeup cycles.

I also tried 3.15-rc4 and with 4 tries system was freezing when waking up. Lid closing/opening was working fine.

[Žygimantas Beručka (zygis)]

I suspect that too as I already mentioned I can suspend/resume before a Unity/compiz session is actually started. With only a lightdm running it just works. You trying out a GNOME session just confirms it.

However, it still means there's a bug in the kernel since a piece of third-party software can cause a kernel panic. This is what they say on the freedesktop.org bugzilla.

[Pavel Selivanov (muiriled)]

Ok, switched back to Unity and getting same mess again.

I cut some logs from syslog. First one is what kernel says about closing the lid:

May 8 23:26:00 loki kernel: [ 169.578622] ------------[ cut here ]------------
May 8 23:26:00 loki kernel: [ 169.578679] WARNING: CPU: 1 PID: 1170 at /home/apw/COD/linux/drivers/gpu/drm/i915/intel_display.c:4197 intel_connector_check_state+0x111/0x1d0 [i915]()
May 8 23:26:00 loki kernel: [ 169.578682] wrong connector dpms state
May 8 23:26:00 loki kernel: [ 169.578685] Modules linked in: i8k snd_hda_codec_idt snd_hda_codec_hdmi hid_generic hid_logitech_dj gpio_ich snd_hda_intel dell_wmi sparse_keymap snd_hda_codec snd_hwdep snd_pcm btusb snd_page_alloc snd_seq_midi snd_seq_midi_event coretemp kvm_intel snd_rawmidi dell_laptop dcdbas kvm lib80211_crypt_tkip joydev snd_seq wl(POF) i915 r852 snd_seq_device serio_raw usbhid rfcomm snd_timer bnep hid sm_common bluetooth nand drm_kms_helper nand_ecc snd r592 nand_bch lib80211 bch nand_ids memstick mtd lpc_ich cfg80211 drm soundcore i2c_algo_bit binfmt_misc wmi mac_hid video parport_pc ppdev lp parport mmc_block firewire_ohci psmouse sdhci_pci sdhci firewire_core ahci crc_itu_t libahci sky2
May 8 23:26:00 loki kernel: [ 169.578785] CPU: 1 PID: 1170 Comm: Xorg Tainted: PF W O 3.13.11-031311-generic #201404222035
May 8 23:26:00 loki kernel: [ 169.578789] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009
May 8 23:26:00 loki kernel: [ 169.578792] 0000000000001065 ffff8800d5bb19c8 ffffffff817410a7 0000000000000007
May 8 23:26:00 loki kernel: [ 169.578799] ffff8800d5bb1a18 ffff8800d5bb1a08 ffffffff81069a4c ffff8800d817e800
May 8 23:26:00 loki kernel: [ 169.578805] ffff8800d7570800 ffff8800d817e800 ffff880119781000 ffff8800d5bb1b88
May 8 23:26:00 loki kernel: [ 169.578812] Call Trace:
May 8 23:26:00 loki kernel: [ 169.578823] [<ffffffff817410a7>] dump_stack+0x46/0x58
May 8 23:26:00 loki kernel: [ 169.578831] [<ffffffff81069a4c>] warn_slowpath_common+0x8c/0xc0
May 8 23:26:00 loki kernel: [ 169.578837] [<ffffffff81069b36>] warn_slowpath_fmt+0x46/0x50
May 8 23:26:00 loki kernel: [ 169.578870] [<ffffffffa035f961>] intel_connector_check_state+0x111/0x1d0 [i915]
May 8 23:26:00 loki kernel: [ 169.578901] [<ffffffffa03719d8>] intel_modeset_check_state+0x38/0xa0 [i915]
May 8 23:26:00 loki kernel: [ 169.578931] [<ffffffffa0371a65>] intel_set_mode+0x25/0x30 [i915]
May 8 23:26:00 loki kernel: [ 169.578962] [<ffffffffa0372a6b>] intel_get_load_detect_pipe+0x24b/0x350 [i915]
May 8 23:26:00 loki kernel: [ 169.579001] [<ffffffffa0399eb7>] intel_tv_detect+0x137/0x210 [i915]
May 8 23:26:00 loki kernel: [ 169.579013] [<ffffffffa01fc293>] drm_helper_probe_single_connector_modes+0x203/0x3a0 [drm_kms_helper]
May 8 23:26:00 loki kernel: [ 169.579042] [<ffffffffa00e256c>] drm_mode_getconnector+0x41c/0x460 [drm]
May 8 23:26:00 loki kernel: [ 169.579060] [<ffffffffa00d2e3a>] drm_ioctl+0x4da/0x600 [drm]
May 8 23:26:00 loki kernel: [ 169.579084] [<ffffffffa00e2150>] ? drm_mode_getcrtc+0xe0/0xe0 [drm]
May 8 23:26:00 loki kernel: [ 169.579092] [<ffffffff81116abc>] ? acct_account_cputime+0x1c/0x2...

[Pavel Selivanov (muiriled)]

And this log I was lucky to get when the system in not completly freezing on lid opening (no messages from kernel in this case, just dies completely). So this is what kernel says when I'm opening lid, system still working, but display is turned off and no button except 'power' is working:

May 8 23:49:19 loki kernel: [ 78.188094] divide error: 0000 [#1] SMP
May 8 23:49:19 loki kernel: [ 78.188137] Modules linked in: i8k snd_hda_codec_idt snd_hda_codec_hdmi gpio_ich hid_generic dell_wmi sparse_keymap btusb dell_laptop dcdbas coretemp kvm_intel kvm snd_hda_intel snd_hda_codec joydev serio_raw snd_hwdep r852 sm_common snd_pcm nand snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq lib80211_crypt_tkip nand_ecc snd_seq_device nand_bch snd_timer lpc_ich bch r592 nand_ids wl(POF) mtd memstick bnep rfcomm snd lib80211 bluetooth cfg80211 soundcore mac_hid i915 binfmt_misc drm_kms_helper video drm parport_pc i2c_algo_bit wmi ppdev lp parport hid_logitech_dj usbhid hid mmc_block psmouse ahci libahci firewire_ohci sdhci_pci firewire_core sdhci crc_itu_t sky2
May 8 23:49:19 loki kernel: [ 78.188655] CPU: 0 PID: 32 Comm: kworker/0:1 Tainted: PF W O 3.13.11-031311-generic #201404222035
May 8 23:49:19 loki kernel: [ 78.188700] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009
May 8 23:49:19 loki kernel: [ 78.188742] Workqueue: kacpi_notify acpi_os_execute_deferred
May 8 23:49:19 loki kernel: [ 78.188773] task: ffff8801195697f0 ti: ffff88011957c000 task.ti: ffff88011957c000
May 8 23:49:19 loki kernel: [ 78.188803] RIP: 0010:[<ffffffffa01c46c6>] [<ffffffffa01c46c6>] intel_sdvo_get_config+0xa6/0x1e0 [i915]
May 8 23:49:19 loki kernel: [ 78.188875] RSP: 0018:ffff88011957db68 EFLAGS: 00010246
May 8 23:49:19 loki kernel: [ 78.188902] RAX: 0000000000000000 RBX: ffff880036f216e0 RCX: ffff8800d902c000
May 8 23:49:19 loki kernel: [ 78.188932] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
May 8 23:49:19 loki kernel: [ 78.188961] RBP: ffff88011957dba8 R08: 0000000000000000 R09: 0000000000000001
May 8 23:49:19 loki kernel: [ 78.188990] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8800d92e7800
May 8 23:49:19 loki kernel: [ 78.189019] R13: 0000000000000000 R14: ffff8800d902c000 R15: ffffffffa0207d63
May 8 23:49:19 loki kernel: [ 78.189049] FS: 0000000000000000(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000
May 8 23:49:19 loki kernel: [ 78.189088] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 8 23:49:19 loki kernel: [ 78.189112] CR2: 00007fe791ded170 CR3: 00000000d9e09000 CR4: 00000000000007f0
May 8 23:49:19 loki kernel: [ 78.189141] Stack:
May 8 23:49:19 loki kernel: [ 78.189154] ffff88011957dba8 00ffffffa01c343e 0000000000000000 000000001e000000
May 8 23:49:19 loki kernel: [ 78.189200] ffff8800d92e7800 ffff8800d9d06b28 ffff8800d902c000 ffff8800d9d06800
May 8 23:49:19 loki kernel: [ 78.189245] ffff88011957dc18 ffffffffa019b438 ffffffffa0207d6b ffff880100000041
May 8 23:49:19 loki kernel: [ 78.189290] Call Trace:
May 8 23:49:19 loki kernel: [ 78.189318] [<ffffffffa019b438>] intel_modeset_readout_hw_st...

[Pavel Selivanov (muiriled)]

May 8 23:51:34 loki bluetoothd[487]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/HFPAG
May 8 23:51:34 loki bluetoothd[487]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/HFPHS
May 8 23:51:34 loki bluetoothd[487]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/A2DPSource
May 8 23:51:34 loki bluetoothd[487]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/A2DPSink
May 8 23:51:34 loki bluetoothd[487]: hci0: Remove UUID (0x0011) failed: Busy (0x0a)
May 8 23:51:38 loki colord: device removed: xrandr-AU Optronics
May 8 23:51:38 loki colord: Profile removed: icc-0535614b8024fad3accb859b843efa58
May 8 23:52:02 loki kernel: [ 240.692204] INFO: task kworker/0:1:32 blocked for more than 120 seconds.
May 8 23:52:02 loki kernel: [ 240.692306] Tainted: PF W O 3.13.11-031311-generic #201404222035
May 8 23:52:02 loki kernel: [ 240.692389] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 8 23:52:02 loki kernel: [ 240.696330] kworker/0:1 D 0000000000000001 0 32 2 0x00000000
May 8 23:52:02 loki kernel: [ 240.700258] Workqueue: kacpi_notify acpi_os_execute_deferred
May 8 23:52:02 loki kernel: [ 240.703974] ffff88011957d538 0000000000000002 ffff88011957d4f8 ffff88011957dfd8
May 8 23:52:02 loki kernel: [ 240.708032] 0000000000014440 0000000000014440 ffff880119b2c7d0 ffff8801195697f0
May 8 23:52:02 loki kernel: [ 240.711699] ffff88011fc14440 ffff8800d9d06a38 ffff8800d9d06a3c 00000000ffffffff
May 8 23:52:02 loki kernel: [ 240.715171] Call Trace:
May 8 23:52:02 loki kernel: [ 240.718644] [<ffffffff81749b99>] schedule+0x29/0x70
May 8 23:52:02 loki kernel: [ 240.722096] [<ffffffff81749ebe>] schedule_preempt_disabled+0xe/0x10
May 8 23:52:02 loki kernel: [ 240.725504] [<ffffffff8174bcf4>] __mutex_lock_slowpath+0x114/0x1b0
May 8 23:52:02 loki kernel: [ 240.728917] [<ffffffff8174bdb3>] mutex_lock+0x23/0x37
May 8 23:52:02 loki kernel: [ 240.732277] [<ffffffffa00fd38b>] drm_modeset_lock_all+0x1b/0x60 [drm]
May 8 23:52:02 loki kernel: [ 240.735481] [<ffffffffa0160a6f>] drm_fb_helper_pan_display+0x2f/0xf0 [drm_kms_helper]
May 8 23:52:02 loki kernel: [ 240.738816] [<ffffffff813d20ad>] fb_pan_display+0xbd/0x170
May 8 23:52:02 loki kernel: [ 240.742106] [<ffffffff813e30c9>] bit_update_start+0x29/0x60
May 8 23:52:02 loki kernel: [ 240.745477] [<ffffffff813e28d2>] fbcon_switch+0x3b2/0x560
May 8 23:52:02 loki kernel: [ 240.748803] [<ffffffff8146b469>] redraw_screen+0x179/0x220
May 8 23:52:02 loki kernel: [ 240.752173] [<ffffffff813e0bea>] fbcon_blank+0x21a/0x2d0
May 8 23:52:02 loki kernel: [ 240.755530] [<ffffffff810b4202>] ? up+0x32/0x50
May 8 23:52:02 loki kernel: [ 240.758710] [<ffffffff810c0bd4>] ? wake_up_klogd+0x34/0x40
May 8 23:52:02 loki kernel: [ 240.761903] [<ffffffff810c0e17>] ? console_unlock.part.12+0x237/0x260
May 8 23:52:02 loki kernel: [ 240.765224] [<ffffffff81077040>] ? internal_add_timer+0x20/0x50
May 8 23:52:02 loki kernel: [ 240.768438] [<ffffffff810788ca>] ? mod_timer+0x10a/0x230
May 8 23:52:02 loki kernel: [ 240.771518] [<ffffffff8146bf4e>] do_unblank_screen.part.18+0x9e/0x180
May 8 23:...

[Žygimantas Beručka (zygis)]

Okay, I fooled around here with several mainline kernel versions, letting them run for a decent amount of time, just to make sure the bug is hit on resume.

3.13.0 – the bug IS triggered. I just booted, logged in and forgot about it. When I came back to it, it was sleeping; on resume the bug got triggered again.

3.12.19 (latest in 3.12 series) – the bug is NOT triggered. As a matter of fact, I am writing this after three suspend/resume cycles.

I suppose the bug was introduced early in the 3.13 series.

[Žygimantas Beručka (zygis)]

Played around with Unity/Compiz (moving windows, opening dash, etc.) while running 3.13rc1 to make sure the bug is triggered. And after a suspend it didn't come back. This leaves us with 3.12.19 being the last version which is known for working fine, and 3.13rc1 is the first version which is buggy. This is not a great news as it means there is a lot of new code between 3.12/3.13 series; narrowing down should be quite hard.

Unfortunately I don't have the skills to do the bisecting thing and no time to learn it at the moment.

[Žygimantas Beručka (zygis)]

Maybe it's worth the time to involve Unity/compiz devs in this? After all it's very likely to be their code which screws the kernel up.

[jhansonxi (jhansonxi)]

I'm encountering the same problems with my Dell Inspiron 1525 and Xubuntu 14.04 (Trusty Tahr) x86_64. Most any display change (blanking, add/removing external monitor) results in a non-fatal error:

May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784402] CPU: 1 PID: 1546 Comm: Xorg Tainted: PF W O 3.13.0-24-generic #46-Ubuntu
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784407] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A11 03/10/2008
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784412] 0000000000000009 ffff88007918dbb8 ffffffff81715a64 0000000000000000
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784423] ffff88007918dbf0 ffffffff810676bd ffff880035d0b000 0000000000000000
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784433] ffff880035c17800 ffff880035c17af8 ffff880056704ca0 ffff88007918dc00
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784443] Call Trace:
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784456] [<ffffffff81715a64>] dump_stack+0x45/0x56
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784467] [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784475] [<ffffffff8106779a>] warn_slowpath_null+0x1a/0x20
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784521] [<ffffffffa00ba232>] intel_modeset_check_state+0x6f2/0x780 [i915]
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784568] [<ffffffffa00ba355>] intel_set_mode+0x25/0x30 [i915]
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784615] [<ffffffffa00babfb>] intel_crtc_set_config+0x7ab/0x9a0 [i915]
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784657] [<ffffffffa000fe9d>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784696] [<ffffffffa0012d87>] drm_mode_setcrtc+0xf7/0x5e0 [drm]
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784725] [<ffffffffa0003c22>] drm_ioctl+0x502/0x630 [drm]
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784743] [<ffffffff811cc6e0>] do_vfs_ioctl+0x2e0/0x4c0
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784752] [<ffffffff8109dd84>] ? vtime_account_user+0x54/0x60
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784761] [<ffffffff811cc941>] SyS_ioctl+0x81/0xa0
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784771] [<ffffffff8172663f>] tracesys+0xe1/0xe6
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.784776] ---[ end trace 7832e5d6c3fcdce6 ]---
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.790057] ------------[ cut here ]------------
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.790120] WARNING: CPU: 1 PID: 1546 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226 intel_modeset_check_state+0x62d/0x780 [i915]()
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.790123] encoder's hw state doesn't match sw tracking (expected 0, found 1)
May 20 19:03:18 jhansonxi-l4 kernel: [ 8205.790125] Modules linked in:...

Suspend/hibernate fails also. Closing the lid results in a freeze.

The "encoder's hw state doesn't match sw tracking" seems to be the problem. A fix for the same error was made last year:
http://linux-kernel.2935.n7.nabble.com/Re-Re-drm-i915-new-warning-regression-in-3-7-10-and-3-8-3-td631548.html
https://bugzilla.redhat.com/show_bug.cgi?id=962386

The current probl...

[penalvch (penalvch)]

jhansonxi, 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

[Iuri Diniz (iuridiniz)]

Could I consider this bug as a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331654 ?

A bug report on kernel.org was done by Žygimantas Beručka (zygis) under https://bugzilla.kernel.org/show_bug.cgi?id=78381 after a bisect that I did.

I can confirm that I cannot resume from suspend ONLY if logged on unity/compiz

[penalvch (penalvch)]

luri Diniz, 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

[Žygimantas Beručka (zygis)]

Just noting that the patch seems to have been included in Linux 3.13.11.5,
released on 18 July[1]. Looking forward to its inclusion in the official
Ubuntu kernel builds.

1. http://patchwork.ozlabs.org/patch/370345/

2014-08-03 1:00 GMT+02:00 Michael <email address hidden>:

> *** This bug is a duplicate of bug 1331654 ***
> https://bugs.launchpad.net/bugs/1331654
>
> ** This bug has been marked a duplicate of bug 1331654
> [Dell Inspiron 1525] Cannot resume from suspend
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1310823
>
> Title:
> [Dell Inspiron 1525] Ubuntu freezes when lid closed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310823/+subscriptions
>

[Rob (rob-de-langhe)]

Can you please confirm that this patch, which is by now listed as included in Linux kernel 3.13.11.5, is also included in
- the latest 3.17 kernel ?
- Ubuntu 14.10 ?

[Greg Wilson (greg2)]

I have this problem as well:
- My Dell Latitude D400 freezes when I close the lid (it then requires hard reboot).
- However, I have no problem when display is turned off due to inactivity timeout.
I am running Ubuntu 16.10 Server (32-bits) in forcepae mode.
I understand a patch has been developed. Has it been released?