I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression. It would be very helpful to know the last kernel that had this issue and the first kernel that did not.
Can you test the following kernels and report back? We are looking for the earliest kernel version that does not have this bug: v4.11-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc4/ If v4.11rc-4 exhibits the bug then test v4.11-rc6: v4.11-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc6/ If v4.11-rc4 does not exhibit the bug then test v4.11-rc2: v4.11-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc2/ Thanks in advance! ** Tags added: performing-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682402 Title: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine Status in linux package in Ubuntu: Confirmed Bug description: Running I/O heavy operation (cp) inside terminal in X server session will lock up entire system while running it in a TTY works fine. I am filing this as a kernel bug because the following steps will still hang the system: 1. Open up gnome-terminal 2. Start copying a really large file between two different EXT4 partitions on my local SSD with a "cp" command 3. Switch to a TTY 4. Login to TTY and observe htop or iotop Expected result: I can see the operation happen and after a while it completes Actual result: Keyboard drops out some time during operation (TTY stops responding, caps lock light no longer responds to pressing caps lock, computer appears effectively dead with last screen image frozen) When I run the "cp" operation on the TTY to start with, no matter if the X session is running in parallel or not, it works as expected with no trouble. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-generic 4.10.0.19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC0D0p: jonas 2297 F...m pulseaudio /dev/snd/controlC0: jonas 2297 F.... pulseaudio CurrentDesktop: GNOME Date: Thu Apr 13 13:04:03 2017 InstallationDate: Installed on 2017-04-08 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 005: ID 056a:5047 Wacom Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FDCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/fedora-root ro rootdelay=5 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago) dmi.bios.date: 11/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FDCTO1WW dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
