You are not logged in.

#1 2016-02-18 14:27:51

slowdivesouvlaki
Member
Registered: 2015-06-26
Posts: 8

Locking / Unlocking with LightDM only works once

Hi,

I'm using LightDM with a herbstluftwm setup. When I first lock the screen in a session everything works fine and I can unlock it. When I try to lock a second time however the screen goes blank (but doesn't turn off) and I can't do anything, not even switching to other tty's. I used ssh to get the LightDM logs while this happens:

Locking for the first time:

[+362.37s] DEBUG: Seat seat0: Locking
[+362.37s] DEBUG: Seat seat0: Creating greeter session
[+362.37s] DEBUG: Seat seat0: Creating display server of type x
[+362.37s] DEBUG: Using VT 8
[+362.37s] DEBUG: Seat seat0: Starting local X display on VT 8
[+362.37s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
[+362.37s] DEBUG: DisplayServer x-1: Writing X server authority to /run/lightdm/root/:1
[+362.37s] DEBUG: DisplayServer x-1: Launching X Server
[+362.37s] DEBUG: Launching process 6445: /usr/sbin/X :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
[+362.37s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
[+362.60s] DEBUG: Seat seat0 changes active session to 
[+362.94s] DEBUG: Got signal 10 from process 6445
[+362.94s] DEBUG: DisplayServer x-1: Got signal from X server :1
[+362.94s] DEBUG: DisplayServer x-1: Connecting to XServer :1
[+362.95s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+362.95s] DEBUG: Session pid=6453: Started with service 'lightdm-greeter', username 'lightdm'
[+362.97s] DEBUG: Session pid=6453: Authentication complete with return value 0: Success
[+362.97s] DEBUG: Seat seat0: Session authenticated, running command
[+362.97s] DEBUG: Session pid=6453: Running command /usr/sbin/lightdm-gtk-greeter
[+362.97s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+362.97s] DEBUG: Session pid=6453: Logging to /var/log/lightdm/x-1-greeter.log
[+363.10s] DEBUG: Activating VT 8
[+363.10s] DEBUG: Locking login1 session c2
[+363.10s] DEBUG: Activating login1 session c4
[+363.11s] DEBUG: Seat seat0 changes active session to c4
[+363.11s] DEBUG: Session c4 is already active
[+363.35s] DEBUG: Session pid=6453: Greeter connected version=1.16.7 resettable=false
[+364.09s] DEBUG: Session pid=6453: Greeter start authentication for xyz
[+364.09s] DEBUG: Session pid=6529: Started with service 'lightdm', username 'xyz'
[+364.11s] DEBUG: Session pid=6529: Got 1 message(s) from PAM
[+364.11s] DEBUG: Session pid=6453: Prompt greeter with 1 message(s)

Unlocking:

[+434.29s] DEBUG: Session pid=6453: Continue authentication
[+434.33s] DEBUG: Session pid=6529: Authentication complete with return value 0: Success
[+434.33s] DEBUG: Session pid=6453: Authenticate result for user xyz: Success
[+434.33s] DEBUG: Session pid=6453: User xyz authorized
[+434.44s] DEBUG: Session pid=6453: Greeter requests session herbstluftwm
[+434.44s] DEBUG: Seat seat0: Returning to existing user session xyz
[+434.44s] DEBUG: Unlocking login1 session c2
[+434.44s] DEBUG: Activating VT 7
[+434.45s] WARNING: Error using VT_WAITACTIVE 7 on /dev/console: Interrupted system call
[+434.45s] DEBUG: Seat seat0: Stopping greeter
[+434.45s] DEBUG: Session pid=6453: Sending SIGTERM
[+434.45s] DEBUG: Activating login1 session c2
[+434.45s] DEBUG: Session pid=6529: Exited with return value 0
[+434.45s] DEBUG: Seat seat0: Session stopped
[+434.51s] DEBUG: Session pid=6453: Greeter closed communication channel
[+434.51s] DEBUG: Session pid=6453: Exited with return value 0
[+434.51s] DEBUG: Seat seat0: Session stopped
[+434.51s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+434.51s] DEBUG: Sending signal 15 to process 6445
[+434.66s] DEBUG: Seat seat0 changes active session to c2
[+434.66s] DEBUG: Session c2 is already active
[+434.72s] DEBUG: Process 6445 exited with return value 0
[+434.72s] DEBUG: DisplayServer x-1: X server stopped
[+434.72s] DEBUG: Releasing VT 8
[+434.72s] DEBUG: DisplayServer x-1: Removing X server authority /run/lightdm/root/:1
[+434.72s] DEBUG: Seat seat0: Display server stopped

Locking the second time only gives this:

[+520.37s] DEBUG: Seat seat0: Creating greeter session
[+520.37s] DEBUG: Seat seat0: Creating display server of type x
[+520.37s] DEBUG: Using VT 8
[+520.37s] DEBUG: Seat seat0: Starting local X display on VT 8
[+520.37s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
[+520.37s] DEBUG: DisplayServer x-1: Writing X server authority to /run/lightdm/root/:1
[+520.37s] DEBUG: DisplayServer x-1: Launching X Server
[+520.37s] DEBUG: Launching process 9948: /usr/sbin/X :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
[+520.37s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
[+520.59s] DEBUG: Seat seat0 changes active session to 

Looking at it it seems like maybe X isn't sending the ready signal? I'm not really sure where to look further.

Offline

#2 2016-02-18 17:19:05

slowdivesouvlaki
Member
Registered: 2015-06-26
Posts: 8

Re: Locking / Unlocking with LightDM only works once

This workaround
https://bbs.archlinux.org/viewtopic.php … 8#p1581078
solves the problem but using AccelMethod uxa gives me some laggy issues.

I'd like to avoid it if possible so if anyone else has an idea I'd be glad to hear it.

Offline

#3 2016-02-20 13:05:45

eggze
Member
Registered: 2016-02-20
Posts: 3

Re: Locking / Unlocking with LightDM only works once

I have the same issue for almost 3 weeks for now. It's annoying and I wasn't able to find out what's wrong or what can I do with it. Reinstalling intel drivers neither downgrade didn't help.

For me there is also crash of i915 kernel module, according to logs (journalctl):

Feb 20 13:28:44 jprokop lightdm[508]: ** (lightdm:508): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: Interrupted system call
Feb 20 13:28:46 jprokop gnome-session[1154]: (gnome-shell:1274): GLib-CRITICAL **: g_source_remove: assertion 'tag > 0' failed
Feb 20 13:28:52 jprokop kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
Feb 20 13:28:54 jprokop kernel: IP: [<ffffffffa07b891c>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
Feb 20 13:28:54 jprokop kernel: PGD 7f84b2067 PUD 7f916b067 PMD 0 
Feb 20 13:28:54 jprokop kernel: Oops: 0000 [#1] PREEMPT SMP 
Feb 20 13:28:54 jprokop kernel: Modules linked in: mousedev input_leds led_class hid_generic usbhid hid fuse snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm i915 irqbypass snd_hda_intel cr
Feb 20 13:28:54 jprokop kernel:  nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_connt
Feb 20 13:28:54 jprokop kernel: CPU: 0 PID: 546 Comm: Xorg Not tainted 4.4.1-2-ARCH #1
Feb 20 13:28:54 jprokop kernel: Hardware name: Dell Inc. OptiPlex 9020/0N4YC8, BIOS A14 09/14/2015
Feb 20 13:28:54 jprokop kernel: task: ffff8807f8815280 ti: ffff8807f86d4000 task.ti: ffff8807f86d4000
Feb 20 13:28:54 jprokop kernel: RIP: 0010:[<ffffffffa07b891c>]  [<ffffffffa07b891c>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
Feb 20 13:28:54 jprokop kernel: RSP: 0018:ffff8807f86d7a58  EFLAGS: 00010246
Feb 20 13:28:54 jprokop kernel: RAX: ffff8807f8815280 RBX: ffff8806688a5500 RCX: 000000001e0d1080
Feb 20 13:28:54 jprokop kernel: RDX: ffff8807f9184e40 RSI: 0000000000000000 RDI: ffff8806688a5500
Feb 20 13:28:54 jprokop kernel: RBP: ffff8807f86d7a80 R08: 0000000000018ac0 R09: ffffffffa06e7cf6
Feb 20 13:28:54 jprokop kernel: R10: ffffea000234e580 R11: ffff88008d396d40 R12: 0000000000000000
Feb 20 13:28:54 jprokop kernel: R13: 0000000000000000 R14: 0000000000200001 R15: 0000000000000080
Feb 20 13:28:54 jprokop kernel: FS:  00007fd6a89a6940(0000) GS:ffff88081ea00000(0000) knlGS:0000000000000000
Feb 20 13:28:54 jprokop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 20 13:28:54 jprokop kernel: CR2: 0000000000000060 CR3: 00000007f86c0000 CR4: 00000000001406f0
Feb 20 13:28:54 jprokop kernel: Stack:
Feb 20 13:28:54 jprokop kernel:  ffff880037870400 ffff8807fa5a7800 0000000000000000 0000000000200001
Feb 20 13:28:54 jprokop kernel:  0000000000000080 ffff8807f86d7aa0 ffffffffa07c2443 00000000f86d7aa8
Feb 20 13:28:54 jprokop kernel:  ffff8807f86d7c48 ffff8807f86d7c18 ffffffff8133c3e6 ffff8807fa5a7860
Feb 20 13:28:54 jprokop kernel: Call Trace:
Feb 20 13:28:54 jprokop kernel:  [<ffffffffa07c2443>] intel_fbdev_set_par+0x43/0x60 [i915]
Feb 20 13:28:54 jprokop kernel:  [<ffffffff8133c3e6>] fb_set_var+0x236/0x460
Feb 20 13:28:54 jprokop kernel:  [<ffffffff810bd68e>] ? cpuacct_charge+0x4e/0x60
Feb 20 13:28:54 jprokop kernel:  [<ffffffff810a9f15>] ? update_curr+0xd5/0x160
Feb 20 13:28:54 jprokop kernel:  [<ffffffff810a733b>] ? set_next_entity+0xab/0x8c0
Feb 20 13:28:54 jprokop kernel:  [<ffffffff8133308f>] fbcon_blank+0x30f/0x350
Feb 20 13:28:54 jprokop kernel:  [<ffffffff813af743>] do_unblank_screen+0xc3/0x190
Feb 20 13:28:54 jprokop kernel:  [<ffffffff813a56d9>] complete_change_console+0x59/0xe0
Feb 20 13:28:54 jprokop kernel:  [<ffffffff813a5e70>] vt_ioctl+0x710/0x12e0
Feb 20 13:28:54 jprokop kernel:  [<ffffffff81192d0d>] ? do_wp_page+0xdd/0x610
Feb 20 13:28:54 jprokop kernel:  [<ffffffffa06ce7e9>] ? drm_ioctl+0x189/0x540 [drm]
Feb 20 13:28:54 jprokop kernel:  [<ffffffff8139a061>] tty_ioctl+0x361/0xc20
Feb 20 13:28:54 jprokop kernel:  [<ffffffff81195a10>] ? handle_mm_fault+0xa20/0x1980
Feb 20 13:28:54 jprokop kernel:  [<ffffffff811f0b68>] do_vfs_ioctl+0x298/0x480
Feb 20 13:28:54 jprokop kernel:  [<ffffffff811fabe7>] ? __fget+0x77/0xb0
Feb 20 13:28:54 jprokop kernel:  [<ffffffff811f0dc9>] SyS_ioctl+0x79/0x90
Feb 20 13:28:54 jprokop kernel:  [<ffffffff81591b2e>] entry_SYSCALL_64_fastpath+0x12/0x71
Feb 20 13:28:54 jprokop kernel: Code: 41 5f 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 41 89 f5 53 4c 8b 67 08 48 89 fb <41> 8b 44 24 60 4d 8b 74 24 28 83 f8 01 74 58 8b b3 5c 01 00 00 
Feb 20 13:28:54 jprokop kernel: RIP  [<ffffffffa07b891c>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
Feb 20 13:28:55 jprokop kernel:  RSP <ffff8807f86d7a58>
Feb 20 13:28:55 jprokop kernel: CR2: 0000000000000060
Feb 20 13:28:55 jprokop kernel: ---[ end trace 1a32a81a5eb0b85d ]---

I also did diff of lsmod command and that the result (I don't know if it's useful information though):

8c8
< fuse                   90112  3
---
> fuse                   90112  5
19c19
< i915                 1134592  6
---
> i915                 1134592  9
28c28
< drm                   286720  7 i915,drm_kms_helper
---
> drm                   286720  10 i915,drm_kms_helper
47c47
< evdev                  24576  10
---
> evdev                  24576  4

Offline

#4 2016-02-23 16:24:00

slowdivesouvlaki
Member
Registered: 2015-06-26
Posts: 8

Re: Locking / Unlocking with LightDM only works once

Seems like it's just a problem with the intel driver then. Everything works fine on my other laptop with the ATI driver.
Have you tried using AccelMethod uxa? I did for a while but it's just unusable for me, maybe it works for you though.

Offline

#5 2016-03-08 16:46:17

VLSPSY
Member
Registered: 2016-03-08
Posts: 1

Re: Locking / Unlocking with LightDM only works once

I have the same problem (at least as eggze) it seems, running on my HP. Looking at my kernel stack (see below) it looks like the same problem as in [1]  which led to [2], which in turn led to a patch on the i915 driver: https://patchwork.freedesktop.org/patch/67152/

It does not seem it has been backported to 4.4 though.. But will be available in the 4.5 kernel... Think I'll try to maybe run an older kernel version.

[1] https://bugzilla.novell.com/show_bug.cgi?id=962866#c7
[2] https://bugs.freedesktop.org/show_bug.cgi?id=93822

[  447.321367] ------------[ cut here ]------------
[  447.321391] WARNING: CPU: 1 PID: 514 at include/linux/kref.h:46 drm_framebuffer_reference+0x64/0x70 [drm]()
[  447.321455] Modules linked in: cmac ecb rfcomm fuse bnep snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support joydev hp_wmi snd_hda_codec_idt sparse_keymap snd_hda_codec_generic ppdev intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass pcspkr psmouse serio_raw i2c_i801 arc4 iwldvm mac80211 btusb btrtl btbcm btintel bluetooth iwlwifi cfg80211 lpc_ich rfkill uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm i915 snd_timer shpchp snd soundcore input_leds evdev mousedev mac_hid e1000e drm_kms_helper mei_me ptp pps_core drm mei intel_gtt syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_algo_bit tpm_infineon thermal wmi battery parport_pc parport hp_accel tpm_tis
[  447.321505]  lis3lv02d tpm input_polldev video fjes hp_wireless ac processor button sch_fq_codel nfs lockd grace sunrpc fscache ip_tables x_tables jitterentropy_rng hmac drbg ansi_cprng algif_skcipher af_alg hid_generic usbhid hid sd_mod atkbd libps2 crct10dif_pclmul crc32_pclmul crc32c_intel ahci libahci aesni_intel lrw gf128mul glue_helper ablk_helper cryptd libata ehci_pci ehci_hcd scsi_mod sdhci_pci xhci_pci sdhci led_class xhci_hcd mmc_core usbcore usb_common i8042 serio sha512_ssse3 sha512_generic sha256_ssse3 sha256_generic aes_x86_64 ext4 crc16 mbcache jbd2 dm_crypt dm_mod
[  447.321509] CPU: 1 PID: 514 Comm: Xorg Tainted: G        W       4.4.3-1-ARCH #1
[  447.321511] Hardware name: Hewlett-Packard HP EliteBook Folio 9470m/18DF, BIOS 68IBD Ver. F.47 10/08/2013
[  447.321516]  0000000000000286 0000000013d73ce7 ffff88022e397a78 ffffffff812cac81
[  447.321519]  0000000000000000 ffffffffa053a7f3 ffff88022e397ab0 ffffffff810776e2
[  447.321523]  ffff880037bbaf00 ffff8801ed8b86c0 ffff8801ed8b86c0 ffff88023306d000
[  447.321524] Call Trace:
[  447.321532]  [<ffffffff812cac81>] dump_stack+0x63/0x82
[  447.321539]  [<ffffffff810776e2>] warn_slowpath_common+0x82/0xc0
[  447.321544]  [<ffffffff8107782a>] warn_slowpath_null+0x1a/0x20
[  447.321559]  [<ffffffffa0514e84>] drm_framebuffer_reference+0x64/0x70 [drm]
[  447.321570]  [<ffffffffa05268dd>] drm_atomic_set_fb_for_plane+0x2d/0x90 [drm]
[  447.321580]  [<ffffffffa058cc5e>] __drm_atomic_helper_set_config+0xde/0x3c0 [drm_kms_helper]
[  447.321586]  [<ffffffffa058f10c>] drm_fb_helper_pan_display+0x18c/0x230 [drm_kms_helper]
[  447.321624]  [<ffffffffa06b303a>] intel_fbdev_pan_display+0x1a/0x60 [i915]
[  447.321630]  [<ffffffff8133edbf>] fb_pan_display+0xcf/0x160
[  447.321635]  [<ffffffff81339080>] bit_update_start+0x20/0x50
[  447.321640]  [<ffffffff813369e0>] fbcon_switch+0x3b0/0x640
[  447.321645]  [<ffffffff813b11be>] redraw_screen+0x19e/0x280
[  447.321651]  [<ffffffff813a867f>] complete_change_console+0x3f/0xe0
[  447.321655]  [<ffffffff813a8e30>] vt_ioctl+0x710/0x12e0
[  447.321660]  [<ffffffff81194f3d>] ? do_wp_page+0xdd/0x610
[  447.321673]  [<ffffffffa050b7e9>] ? drm_ioctl+0x189/0x540 [drm]
[  447.321676]  [<ffffffff8139cf41>] tty_ioctl+0x361/0xc30
[  447.321680]  [<ffffffff81197c40>] ? handle_mm_fault+0xa20/0x1980
[  447.321684]  [<ffffffff811f3058>] do_vfs_ioctl+0x298/0x480
[  447.321688]  [<ffffffff811fd0f7>] ? __fget+0x77/0xb0
[  447.321692]  [<ffffffff811f32b9>] SyS_ioctl+0x79/0x90
[  447.321698]  [<ffffffff81595eae>] entry_SYSCALL_64_fastpath+0x12/0x6d
[  447.321701] ---[ end trace 7b5f02c7f0c691fa ]---
[  447.334501] BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
[  447.334544] IP: [<ffffffffa06a95ac>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
[  447.334548] PGD b1aeb067 PUD b1ae5067 PMD 0 
[  447.334552] Oops: 0000 [#1] PREEMPT SMP 
[  447.334612] Modules linked in: cmac ecb rfcomm fuse bnep snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support joydev hp_wmi snd_hda_codec_idt sparse_keymap snd_hda_codec_generic ppdev intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass pcspkr psmouse serio_raw i2c_i801 arc4 iwldvm mac80211 btusb btrtl btbcm btintel bluetooth iwlwifi cfg80211 lpc_ich rfkill uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm i915 snd_timer shpchp snd soundcore input_leds evdev mousedev mac_hid e1000e drm_kms_helper mei_me ptp pps_core drm mei intel_gtt syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_algo_bit tpm_infineon thermal wmi battery parport_pc parport hp_accel tpm_tis
[  447.334657]  lis3lv02d tpm input_polldev video fjes hp_wireless ac processor button sch_fq_codel nfs lockd grace sunrpc fscache ip_tables x_tables jitterentropy_rng hmac drbg ansi_cprng algif_skcipher af_alg hid_generic usbhid hid sd_mod atkbd libps2 crct10dif_pclmul crc32_pclmul crc32c_intel ahci libahci aesni_intel lrw gf128mul glue_helper ablk_helper cryptd libata ehci_pci ehci_hcd scsi_mod sdhci_pci xhci_pci sdhci led_class xhci_hcd mmc_core usbcore usb_common i8042 serio sha512_ssse3 sha512_generic sha256_ssse3 sha256_generic aes_x86_64 ext4 crc16 mbcache jbd2 dm_crypt dm_mod
[  447.334662] CPU: 1 PID: 514 Comm: Xorg Tainted: G        W       4.4.3-1-ARCH #1
[  447.334664] Hardware name: Hewlett-Packard HP EliteBook Folio 9470m/18DF, BIOS 68IBD Ver. F.47 10/08/2013
[  447.334666] task: ffff8800b1b20000 ti: ffff88022e394000 task.ti: ffff88022e394000
[  447.334697] RIP: 0010:[<ffffffffa06a95ac>]  [<ffffffffa06a95ac>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
[  447.334699] RSP: 0018:ffff88022e397a58  EFLAGS: 00010246
[  447.334701] RAX: ffff8800b1b20000 RBX: ffff8801edef8500 RCX: 0000000001af6281
[  447.334702] RDX: ffff880037bbaf00 RSI: 0000000000000000 RDI: ffff8801edef8500
[  447.334704] RBP: ffff88022e397a80 R08: 0000000000018ac0 R09: ffffffffa0524d46
[  447.334705] R10: ffffea0007b7a3c0 R11: ffff8801ed8b80c0 R12: 0000000000000000
[  447.334707] R13: 0000000000000000 R14: 0000000000200001 R15: 0000000000000080
[  447.334710] FS:  00007fdc01c7a940(0000) GS:ffff88023ea40000(0000) knlGS:0000000000000000
[  447.334711] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  447.334713] CR2: 0000000000000060 CR3: 00000000b1ae9000 CR4: 00000000001406e0
[  447.334714] Stack:
[  447.334718]  ffff880037550c00 ffff880233e58000 0000000000000000 0000000000200001
[  447.334722]  0000000000000080 ffff88022e397aa0 ffffffffa06b3123 000000002e397aa8
[  447.334725]  ffff88022e397c48 ffff88022e397c18 ffffffff8133f256 ffff880233e58060
[  447.334726] Call Trace:
[  447.334758]  [<ffffffffa06b3123>] intel_fbdev_set_par+0x43/0x60 [i915]
[  447.334765]  [<ffffffff8133f256>] fb_set_var+0x236/0x460
[  447.334770]  [<ffffffff810becde>] ? cpuacct_charge+0x4e/0x60
[  447.334774]  [<ffffffff810ab4d5>] ? update_curr+0xd5/0x180
[  447.334778]  [<ffffffff810a88bb>] ? set_next_entity+0xab/0x8c0
[  447.334786]  [<ffffffff81335eff>] fbcon_blank+0x30f/0x350
[  447.334797]  [<ffffffff813b2703>] do_unblank_screen+0xc3/0x190
[  447.334805]  [<ffffffff813a8699>] complete_change_console+0x59/0xe0
[  447.334810]  [<ffffffff813a8e30>] vt_ioctl+0x710/0x12e0
[  447.334816]  [<ffffffff81194f3d>] ? do_wp_page+0xdd/0x610
[  447.334836]  [<ffffffffa050b7e9>] ? drm_ioctl+0x189/0x540 [drm]
[  447.334842]  [<ffffffff8139cf41>] tty_ioctl+0x361/0xc30
[  447.334848]  [<ffffffff81197c40>] ? handle_mm_fault+0xa20/0x1980
[  447.334856]  [<ffffffff811f3058>] do_vfs_ioctl+0x298/0x480
[  447.334862]  [<ffffffff811fd0f7>] ? __fget+0x77/0xb0
[  447.334867]  [<ffffffff811f32b9>] SyS_ioctl+0x79/0x90
[  447.334875]  [<ffffffff81595eae>] entry_SYSCALL_64_fastpath+0x12/0x6d
[  447.334934] Code: 41 5f 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 41 89 f5 53 4c 8b 67 08 48 89 fb <41> 8b 44 24 60 4d 8b 74 24 28 83 f8 01 74 58 8b b3 5c 01 00 00 
[  447.334975] RIP  [<ffffffffa06a95ac>] intel_fb_obj_invalidate+0x1c/0xf0 [i915]
[  447.334977]  RSP <ffff88022e397a58>
[  447.334979] CR2: 0000000000000060
[  447.334983] ---[ end trace 7b5f02c7f0c691fb ]---

Last edited by VLSPSY (2016-03-08 16:49:27)

Offline

#6 2016-03-08 23:04:47

eworm
Trusted User (TU)
From: Oberhausen, Germany
Registered: 2010-01-30
Posts: 101
Website

Re: Locking / Unlocking with LightDM only works once

I have the same issue with my Lenovo Thinkpad X250. This only hits me when connected to docking stations, though.

I cherry-picked these patches for linux 4.4.4:

ca40ba855c9e3f19f2715fd8a1ced5128359d3d9
51f1385b90c1ad30896bd62b1ff97aa4edb1a163
366e39b4d2c53b198b072f984caa0ebc4220ad4d
581da2cab557fa6e8a954c148c487eb7e0658979
0c82312f3f15538f4e6ceda2a82caee8fbac4501

Anybody wants to give it a try?
linux-4.4.4-1.1-x86_64
linux-headers-4.4.4-1.1-x86_64


ArchLinux - make it simple & lightweight

Offline

#7 2016-03-24 06:52:49

shved
Member
Registered: 2012-12-11
Posts: 54

Re: Locking / Unlocking with LightDM only works once

Hi! Does the last version of xf86-video-intel fixed this issue? Or we need to wait for 4.5?

UPD: Nope... seems it doesn't

UPD2: Updating to linux-4.5-1 from testing fixed the issue two.

Last edited by shved (2016-03-25 05:16:48)


Sorry for my english

Offline

Board footer

Powered by FluxBB