<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jan 8, 2015 at 8:08 PM, Karl Newman <span dir="ltr"><<a href="mailto:newmank1@asme.org" target="_blank">newmank1@asme.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Thu, Jan 8, 2015 at 7:09 PM, Matt Garman <span dir="ltr"><<a href="mailto:matthew.garman@gmail.com" target="_blank">matthew.garman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On Wed, Jan 7, 2015 at 9:04 AM, Karl Newman <<a href="mailto:newmank1@asme.org" target="_blank">newmank1@asme.org</a>> wrote:<br>
> Just to follow up on this--after I downgraded xscreensaver I still got a<br>
> freeze, so I upgraded my main frontend (Sandy Bridge) to xf86-video-intel<br>
> version 2.99.917. I'll see if that fixes it.<br>
<br>
</span>Any success with this? Or too early to say?<br>
<div><div><br>
Thanks!<br></div></div></blockquote><div><br></div></span><div>Nope, that didn't fix it either. In fact it made it worse, because after it froze I hit Esc and End and eventually it restarted X but it came back with a black screen and I had to reboot. So I reverted to the latest stable version (which was still freezing but at least recoverable). So I'm back on xf86-video-intel 2.21.15. Oh, kernel 3.17.7 (with Gentoo patches) by the way.<span class=""><font color="#888888"><br><br></font></span></div></div></div></div>
</blockquote></div>I did poke into the kernel log and while there's nothing at the time of the freeze, it does show an event when I exit X. Here's the relevant snippet:<br>Jan 09 06:11:18 [kernel] [43706.644369] ------------[ cut here ]------------<br>Jan 09 06:11:18 [kernel] [43706.644378] WARNING: CPU: 1 PID: 12472 at drivers/gpu/drm/i915/intel_display.c:3361 intel_crtc_wait_for_<br>pending_flips+0x180/0x190()<br>Jan 09 06:11:18 [kernel] [43706.644393] Modules linked in: w83627ehf hwmon_vid iptable_nat nf_nat_ipv4 nf_nat fuse ivtv_alsa wm8775<br>tuner cx25840 ivtv tveeprom coretemp imon hwmon cx2341x x86_pkg_temp_thermal crc32c_intel pcspkr psmouse wmi ata_generic pata_acpi x<br>hci_hcd pata_via ehci_pci ehci_hcd<br>Jan 09 06:11:18 [kernel] [43706.644396] CPU: 1 PID: 12472 Comm: X Not tainted 3.17.7-gentoo #2<br>Jan 09 06:11:18 [kernel] [43706.644397] Hardware name: System manufacturer System Product Name/P8H67-M PRO, BIOS 3904 04/27/2013<br>Jan 09 06:11:18 [kernel] [43706.644400] 0000000000000009 ffff8801f54bf800 ffffffff81893f00 0000000000000000<br>Jan 09 06:11:18 [kernel] [43706.644401] ffff8801f54bf838 ffffffff81059a83 0000000000000000 ffff880225f6e000<br>Jan 09 06:11:18 [kernel] [43706.644403] ffff880037788150 ffff8802246a2000 0000000000000000 ffff8801f54bf848<br>Jan 09 06:11:18 [kernel] [43706.644404] Call Trace:<br>Jan 09 06:11:18 [kernel] [43706.644410] [<ffffffff81893f00>] dump_stack+0x4d/0x6f<br>Jan 09 06:11:18 [kernel] [43706.644414] [<ffffffff81059a83>] warn_slowpath_common+0x73/0x90<br>Jan 09 06:11:18 [kernel] [43706.644416] [<ffffffff81059b55>] warn_slowpath_null+0x15/0x20<br>Jan 09 06:11:18 [kernel] [43706.644420] [<ffffffff81509b60>] intel_crtc_wait_for_pending_flips+0x180/0x190<br>Jan 09 06:11:18 [kernel] [43706.644423] [<ffffffff8108af90>] ? prepare_to_wait_event+0x100/0x100<br>Jan 09 06:11:18 [kernel] [43706.644425] [<ffffffff81510d4f>] intel_crtc_disable_planes+0x2f/0x160<br>Jan 09 06:11:18 [kernel] [43706.644427] [<ffffffff815114a5>] ironlake_crtc_disable+0x45/0x790<br>Jan 09 06:11:18 [kernel] [43706.644430] [<ffffffff81503e47>] ? intel_dump_pipe_config.isra.55+0x37/0x350<br>Jan 09 06:11:18 [kernel] [43706.644434] [<ffffffff814b3392>] ? drm_match_cea_mode+0x12/0x20<br>Jan 09 06:11:18 [kernel] [43706.644436] [<ffffffff8150bc51>] __intel_set_mode+0x7a1/0x1620<br>Jan 09 06:11:18 [kernel] [43706.644438] [<ffffffff81514021>] intel_set_mode+0x11/0x30<br>Jan 09 06:11:18 [kernel] [43706.644440] [<ffffffff81514f6c>] intel_crtc_set_config+0x91c/0xe50<br>Jan 09 06:11:18 [kernel] [43706.644443] [<ffffffff814aa794>] drm_mode_set_config_internal+0x64/0xf0<br>Jan 09 06:11:18 [kernel] [43706.644447] [<ffffffff81499b9b>] restore_fbdev_mode+0xab/0xd0<br>Jan 09 06:11:18 [kernel] [43706.644450] [<ffffffff81499bde>] drm_fb_helper_restore_fbdev_mode_unlocked+0x1e/0x40<br>Jan 09 06:11:18 [kernel] [43706.644452] [<ffffffff8149b6e3>] drm_fb_helper_set_par+0x23/0x70<br>Jan 09 06:11:18 [kernel] [43706.644455] [<ffffffff8151f345>] intel_fbdev_set_par+0x15/0x60<br>Jan 09 06:11:18 [kernel] [43706.644457] [<ffffffff814517ef>] fb_set_var+0x19f/0x410<br>Jan 09 06:11:18 [kernel] [43706.644462] [<ffffffff810e3105>] ? pagecache_get_page+0xf5/0x1e0<br>Jan 09 06:11:18 [kernel] [43706.644466] [<ffffffff8144c44e>] fbcon_blank+0x1ce/0x320<br>Jan 09 06:11:18 [kernel] [43706.644469] [<ffffffff814327e3>] do_unblank_screen+0xa3/0x1c0<br>Jan 09 06:11:18 [kernel] [43706.644472] [<ffffffff8142a0d3>] vt_ioctl+0x10c3/0x1140<br>Jan 09 06:11:18 [kernel] [43706.644474] [<ffffffff818918f4>] ? __slab_free+0xf9/0x2af<br>Jan 09 06:11:18 [kernel] [43706.644477] [<ffffffff811645e9>] ? __fsnotify_inode_delete+0x9/0x10<br>Jan 09 06:11:18 [kernel] [43706.644481] [<ffffffff8141fc65>] tty_ioctl+0x265/0xb90<br>Jan 09 06:11:18 [kernel] [43706.644483] [<ffffffff811256d0>] ? kfree+0xd0/0x110<br>Jan 09 06:11:18 [kernel] [43706.644485] [<ffffffff8114a2f3>] ? mntput_no_expire+0x23/0x130<br>Jan 09 06:11:18 [kernel] [43706.644488] [<ffffffff8113e670>] do_vfs_ioctl+0x2e0/0x4c0<br>Jan 09 06:11:18 [kernel] [43706.644489] [<ffffffff81147eb9>] ? __fget+0x69/0xb0<br>Jan 09 06:11:18 [kernel] [43706.644491] [<ffffffff8113e88c>] SyS_ioctl+0x3c/0x80<br>Jan 09 06:11:18 [kernel] [43706.644495] [<ffffffff8189d0d2>] system_call_fastpath+0x16/0x1b<br>Jan 09 06:11:18 [kernel] [43706.644496] ---[ end trace 28be35dfe0d311ab ]---<br><br></div><div class="gmail_extra">I haven't had time to search on this yet. It appears something in the kernel changed and caused this instability, I'm guessing around kernel version 3.14. It's entirely possibly my freeze has a different root cause than yours though...<br><br>Karl<br></div></div>