Created attachment 217511 [details] Zip file including logs,crash report and hardware information Hi, I installed Ubuntu 16.04 (fresh install) on my new convertible "2 in 1" Toshiba Radius 11 (L10W-C10C) with touchscreen and normal HDD. Ubuntu Installation made alongside of pre-installed win10 (dual boot). Ubuntu 16.04 distribution was including kernel version 4.4.022, and it was running ok. Two days ago i manually updated kernel to version 4.6. After booting with Ubuntu kernel 4.6, i can work for 5-10 minutes and then laptop screen stucks / freezes. Also Touchpad stops working and touchscreen stops working. Keyboard seems also that has stopped working, although i can see the caps lock led going on and off every time i press it. The only way to un-stuck my pc is to make a hard reset using power button. Booting Ubuntu with Kernel 4.6 recovery mode, my laptop works (with pure graphics) but it is not getting "stuck", so i can say works somehow ok. Booting Ubuntu with the previous 4.4.022 kernel i have good graphics and good operation as before kernel update. I'm not an expert, but considering that my laptop is not stuck on a recovery boot of 4.6 kernel, i get suspicious of (graphics ?) drivers problem, a problem that obviously is not present in the kernel 4.4.022 distributed with Ubuntu image. I hereunder attach the following files for troubleshooting: a) File 442.txt Hardware / Software information when booted with kernel 4.4.022 PS: txt file includes output of ver_linux script, proc/cpuinfo, lscpu, proc/modules, lsmod, lspci -vvv, proc/scsi/scsi, dmesg, lsusb, hwinfo, xinput list, xrandr. b) File 46.txt Hardware / Software information when booted with kernel 4.6 Text file includes the same information as previous. c) File 46-recovery.txt Hardware / Software information when booted with kernel 4.6 in recovery mode selected in grub menu. Text file includes the same information as previous. d) File log.zip In this file i have zipped the whole /var/log folder of my pc. e) File crash-.zip In this file i have zipped the crash folder of my pc. Hope the above data to be enough for you people to figure out what goes wrong with kernel 4.6 release. Regards, George V.
Created attachment 217591 [details] crash dup it seems that i succeed to dump with dmesg the crash details during screen freeze in this file, using alt+sysrq+1 and then alt+sysrq+t when i was freezed.
Looks like i915 is not too happy.
Created attachment 217861 [details] dmesg latest log Hello, Yes it seems that handling of i915 is the cause of the problem. I attach here last dmesg file during the crash. During hang, I fortunatelly was capable to switch to a new tty1 (ctrl+alt+F1), log in to console, and get a nice dmesg just after the crash. This attached dmesg describes the i915 hang as you mention. Since kernel 4.4.0.22 that came up with my Ubuntu image is handling this chipset without hanging, i suppose that this hang is a 4.6 kernel bug, right? Please let me know if i have to do something more from my side. Regards George V.
I'm also experiencing system freezes on a Toshiba laptop with Arch Linux since today's update to kernel 4.6.2 (x86_64). In my case, the system hangs as soon as gdm (gnome 3.20) is loaded, every time - mouse doesn't work, can't switch to other ttys.
FYI many are also reporting system freezes with kernel 4.6 + intel graphics in this thread: "[Intel] screen freeze after boot with kernel 4.6.1-2" https://bbs.archlinux.org/viewtopic.php?id=213495
(In reply to raoul from comment #4) > I'm also experiencing system freezes on a Toshiba laptop with Arch Linux > since today's update to kernel 4.6.2 (x86_64). In my case, the system hangs > as soon as gdm (gnome 3.20) is loaded, every time - mouse doesn't work, > can't switch to other ttys. So, we are not alone! If you are able to use SysrRQ during freeze (i.e alt-sysrq + REISUB), you could try to use Alt+Sysrq + T, and then booting in a command prompt you might be able to get dmseg in order to upload it here for our beloved kernel people.
(In reply to George Vasiliou from comment #6) > If you are able to use SysrRQ during freeze (i.e alt-sysrq + REISUB), you > could try to use Alt+Sysrq + T, and then booting in a command prompt you > might be able to get dmseg in order to upload it here for our beloved kernel > people. Unfortunately it doesn't seem to do anything when gdm is frozen (tried a couple of times... btw I do have CONFIG_MAGIC_SYSRQ=y in my .config)
Same problem with my setup: Linux version 4.6.2-1-ARCH (builduser@tobias) (gcc version 6.1.1 20160602 (GCC) ) #1 SMP PREEMPT Wed Jun 8 08:40:59 CEST 2016 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) xf86-video-intel 1:2.99.917+654+ga508b11 Tried uninstalling the xf86-video-intel driver and 20-intel.conf to switch to modesetting driver, but in that case the laptop display does not work (black screen), only the externally plugged in VGA monitor works. In that modesetting state, once the laptop powersave kicks in and I wake it up again, both the laptop display as well as the VGA monitor "work", but the system is frozen - need to hard reset it. I can understand if this modesetting driver issue is a completely different problem, but thought I mention this here as well.
Hello, Just an update on this issue from my side: I installed Debian Jessie Stable in a dedicated partition of my hdd. Jessie stable uses a 3.16 kernel version. This version just not works with my display. My screen is not recognized, xrandr reports only default screen and i only get 800x600 resolution. Without willing to resolve this 3.16 issue, i just upgraded to Debian sid/unstable which installs kernel 4.6.0 - Debian version 2.2 In this case my convertible laptop screen was recognized correctly, i could get the maximum 1366x768 resolution but desktop still freezes like in Ubuntu. I further upgraded Debian Kernel to version 4.7.rc4-amd64 from Debian experimental repos. With this new debian kernel version 4.7.rc4-amd64 everything is fine. Screen recognized, resolution ok and -surprise!- no more graphical freezing! As a result i could say problem is solved (for my case at least) using kernel 4.7. I had a quick look to kernel 4.7 changelog and i could see that some pathces have been applied for the i915. I'm not an expert, but seems that whatever patch applied for i915 in 4.7 kernel worked for me.
Please try with kernel v4.6.x whether adding the following kernel boot parameter avoids the freeze: i915.enable_fbc=0.
See also http://thread.gmane.org/gmane.linux.kernel/2212036.
(In reply to Bart Van Assche from comment #10) > Please try with kernel v4.6.x whether adding the following kernel boot > parameter avoids the freeze: i915.enable_fbc=0. Still hangs for me on kernel 4.6.4 / intel driver 1:2.99.917+684+g6988b87 with i915.enable_fbc=0.
I have switched to kernel v4.7. The i915 driver in that kernel is working reliably for me.
(In reply to Bart Van Assche from comment #13) > I have switched to kernel v4.7. The i915 driver in that kernel is working > reliably for me. Are you using the Intel driver, or the modesetting one? Do you still require the i915.enable_fbc=0 setting on 4.7?
I'm using kernel 4.7 with default settings, that means without i915.enable_fbc=0.
I've had the same problem since 4.6 and still have it with kernel 4.7 on Arch. So I still have to use i915.enable_psr=0
Reporting the same here for me: 4.7.0 works, but only with i915.enable_psr=0
Please file all drm/i915 bugs at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel