Activity log for bug #1776887

Date Who What changed Old value New value Message
2018-06-14 10:37:08 Alan Jenkins bug added bug
2018-06-14 10:37:08 Alan Jenkins attachment added lspci-vnvn.log https://bugs.launchpad.net/bugs/1776887/+attachment/5152515/+files/lspci-vnvn.log
2018-06-14 10:39:56 Alan Jenkins attachment added A copy of the original patch that was merged upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+attachment/5152516/+files/0001-block-do-not-use-interruptible-wait-anywhere.patch
2018-06-14 11:00:06 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2018-06-14 11:00:08 Ubuntu Kernel Bot tags bionic
2018-06-14 12:21:51 Alan Jenkins linux (Ubuntu): status Incomplete Confirmed
2018-06-14 12:25:51 Ubuntu Foundations Team Bug Bot tags bionic bionic patch
2018-06-14 12:25:52 Ubuntu Foundations Team Bug Bot bug added subscriber Joseph Salisbury
2018-06-14 14:41:42 Joseph Salisbury linux (Ubuntu): importance Undecided High
2018-06-14 14:41:48 Joseph Salisbury nominated for series Ubuntu Bionic
2018-06-14 14:41:48 Joseph Salisbury bug task added linux (Ubuntu Bionic)
2018-06-14 14:41:52 Joseph Salisbury linux (Ubuntu Bionic): importance Undecided High
2018-06-14 14:41:55 Joseph Salisbury linux (Ubuntu Bionic): status New Triaged
2018-06-14 14:41:58 Joseph Salisbury linux (Ubuntu): status Confirmed Triaged
2018-06-14 14:42:08 Joseph Salisbury linux (Ubuntu Bionic): assignee Joseph Salisbury (jsalisbury)
2018-06-14 14:42:10 Joseph Salisbury linux (Ubuntu): assignee Joseph Salisbury (jsalisbury)
2018-06-14 16:13:33 Joseph Salisbury linux (Ubuntu Bionic): status Triaged In Progress
2018-06-14 16:13:45 Joseph Salisbury linux (Ubuntu): status Triaged In Progress
2018-06-15 04:01:19 penalvch tags bionic patch bionic cherry-pick kernel-fixed-upstream patch regression-release reverse-bisect-done
2018-06-15 04:02:22 penalvch bug added subscriber Christopher M. Penalver
2018-06-15 04:04:38 penalvch description This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan WORKAROUND: Use kernel parameter: scsi_mod.scan=sync
2018-06-29 13:39:12 Joseph Salisbury description This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan WORKAROUND: Use kernel parameter: scsi_mod.scan=sync == SRU Justification == This upstream bug has been confirmed to affect Ubuntu users[1]. As per the fix commit (below), the most frequent symptom is a crash of Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken from system sleep. Frequency of the bug is described as once every few days[2]. [1] E.g. this user confirms the bug & very specific workaround: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11 [2] E.g. this log of crashes: https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23 This is a bug in blk-core.c. It is not specific to any one hardware driver. Technically the suspend bug is triggered by the SCSI core - which is used by *all SATA devices*. The commit also includes a test which quickly and reliably proves the existence of a horrifying bug. I guess you might avoid this bug only if you have root on NVMe. The other way to not hit the Xorg crash is if you don't use all your RAM, so there's no pressure that leads to cold pages of Xorg being swapped. Also, you won't reproduce the Xorg crash if you suspend+resume immediately. (This frustrated my tests at one point, it only triggered after left the system suspended over lunch :). Fix: "block: do not use interruptible wait anywhere" in kernel 4.17: https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428 in kernel 4.16.8: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6 lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-core.c?id=Ubuntu-4.15.0-24.26#n856 I.e., this bug is still present in Ubuntu source package linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details (lspci-vnvn.log) of a system where this bug is known to happen. Regards Alan WORKAROUND: Use kernel parameter: scsi_mod.scan=sync == Fix == 1dc3039bc87a ("block: do not use interruptible wait anywhere") == Regression Potential == Low. This patch has been sent to stable, so it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug.
2018-07-02 13:11:02 Paulo Marcel Coelho Aragão bug added subscriber Paulo Marcel Coelho Aragão
2018-07-05 13:05:30 DavidV bug added subscriber DavidV
2018-07-08 09:18:48 Eugene Romanenko bug added subscriber Eugene Romanenko
2018-07-08 13:30:54 masd2020 bug added subscriber masd2020
2018-07-17 14:57:16 Stefan Bader linux (Ubuntu Bionic): status In Progress Fix Committed
2018-07-18 10:01:44 Brad Figg tags bionic cherry-pick kernel-fixed-upstream patch regression-release reverse-bisect-done bionic cherry-pick kernel-fixed-upstream patch regression-release reverse-bisect-done verification-needed-bionic
2018-07-20 10:40:22 Kleber Sacilotto de Souza linux (Ubuntu Bionic): status Fix Committed In Progress
2018-07-20 11:05:48 Kleber Sacilotto de Souza tags bionic cherry-pick kernel-fixed-upstream patch regression-release reverse-bisect-done verification-needed-bionic bionic cherry-pick kernel-fixed-upstream patch regression-release reverse-bisect-done
2018-07-20 15:39:45 Launchpad Janitor linux (Ubuntu Bionic): status In Progress Fix Released
2018-07-21 18:39:05 penalvch linux (Ubuntu Bionic): status Fix Released In Progress
2018-07-26 05:13:52 Launchpad Janitor linux (Ubuntu): status In Progress Fix Released
2018-07-26 07:09:43 penalvch linux (Ubuntu): status Fix Released In Progress
2018-08-08 19:19:41 Joseph Salisbury linux (Ubuntu Bionic): status In Progress Fix Committed
2018-08-08 19:19:44 Joseph Salisbury linux (Ubuntu): status In Progress Fix Committed
2018-08-10 03:16:13 Ryan C. Underwood bug added subscriber Ryan C. Underwood
2018-09-05 17:22:14 Luca Capasso linux (Ubuntu): status Fix Committed Confirmed
2018-09-06 05:32:03 penalvch linux (Ubuntu): status Confirmed Triaged
2018-11-06 13:00:27 Meike Hecker bug added subscriber Meike Hecker
2019-07-24 21:05:31 Brad Figg tags bionic cherry-pick kernel-fixed-upstream patch regression-release reverse-bisect-done bionic cherry-pick cscc kernel-fixed-upstream patch regression-release reverse-bisect-done
2019-07-25 00:22:13 Ubuntu Foundations Team Bug Bot bug added subscriber Terry Rudd
2019-11-01 12:41:38 Julien Olivier bug added subscriber Julien Olivier