[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-08-17 Thread Paulo Marcel Coelho Aragão
I left my laptop suspended for a couple of hours while I went out on
some errands, and X crashed when I tried to resume it.

I'm running:

paulo:~$ uname -r
4.15.0-32-generic

Even though it passed the blktests test, the bug is still biting :-(

A crash report was generated, where should I sent it to?

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == 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=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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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


[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-08-15 Thread Paulo Marcel Coelho Aragão
It was already patched in the previous kernel, 4.15.0-31-generic.

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == 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=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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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


[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-08-08 Thread Paulo Marcel Coelho Aragão
I've just booted into 4.15.0-31-generic that hit proposed, and it seems
that the patch was included. From the changelog:

block: do not use interruptible wait anywhere

Just to make sure:

paulo:~/src/blktests (master)$ sudo ./check block/016
block/016 (send a signal to a process waiting on a frozen queue) [passed]
runtime  8,210s  ...  10,261s

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == 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=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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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


[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-08-06 Thread Paulo Marcel Coelho Aragão
4.15.0-30.32 has just been released, and the patch still hasn't been
included.

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == 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=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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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


[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-07-20 Thread Paulo Marcel Coelho Aragão
I had installed 4.15.0-29.31 from proposed, I suppose the packages had
been updated, so reinstalled everything:

Start-Date: 2018-07-20  14:30:02
Commandline: apt install --reinstall linux-generic linux-headers-4.15.0-29 
linux-headers-4.15.0-29-generic linux-headers-generic 
linux-image-4.15.0-29-generic linux-image-generic linux-libc-dev 
linux-modules-4.15.0-29-generic linux-modules-extra-4.15.0-29-generic 
linux-tools-4.15.0-29 linux-tools-4.15.0-29-generic linux-tools-common 
linux-tools-virtual
Requested-By: paulo (1000)
Reinstall: linux-headers-generic:amd64 (4.15.0.29.31), 
linux-image-4.15.0-29-generic:amd64 (4.15.0-29.31), linux-image-generic:amd64 
(4.15.0.29.31), linux-headers-4.15.0-29:amd64 (4.15.0-29.31), 
linux-tools-4.15.0-29:amd64 (4.15.0-29.31), 
linux-modules-extra-4.15.0-29-generic:amd64 (4.15.0-29.31), 
linux-tools-4.15.0-29-generic:amd64 (4.15.0-29.31), 
linux-modules-4.15.0-29-generic:amd64 (4.15.0-29.31), 
linux-headers-4.15.0-29-generic:amd64 (4.15.0-29.31), linux-tools-virtual:amd64 
(4.15.0.29.31), linux-generic:amd64 (4.15.0.29.31)
Upgrade: linux-libc-dev:amd64 (4.15.0-24.26, 4.15.0-29.31), 
linux-tools-common:amd64 (4.15.0-24.26, 4.15.0-29.31)
End-Date: 2018-07-20  14:31:58

and rebooted:

paulo:~$ uname -r
4.15.0-29-generic

but the patch still hasn't been included:

paulo:~/src/blktests (master)$ sudo ./check block/016
block/016 (send a signal to a process waiting on a frozen queue) [failed]
runtime  8,390s  ...  8,210s
--- tests/block/016.out 2018-07-18 10:04:54.136492698 -0300
+++ results/nodev/block/016.out.bad 2018-07-20 14:41:04.159809741 -0300
@@ -1,2 +1,3 @@
 Running block/016
+dd: error reading '/dev/nullb0': Input/output error
 Test complete

The changelog mentions a patch that has no relation to this bug:

  * Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after
suspend (LP: #1776887)
- ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == 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=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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-07-18 Thread Paulo Marcel Coelho Aragão
I've just upgraded to 4.15.0.29.31 from proposed, and I can confirm Alan
Jenkins' comment #17: the bug is still present:

$ uname -r
4.15.0-29-generic

$ sudo ./check block/016
block/016 (send a signal to a process waiting on a frozen queue) [failed]
runtime  ...  8,390s
--- tests/block/016.out 2018-07-18 10:04:54.136492698 -0300
+++ results/nodev/block/016.out.bad 2018-07-18 10:22:55.171574748 -0300
@@ -1,2 +1,3 @@
 Running block/016
+dd: error reading '/dev/nullb0': Input/output error
 Test complete

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == 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=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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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


[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-07-02 Thread Paulo Marcel Coelho Aragão
Sorry for the delay, @jsalisbury, I hadn't subscribed myself to this
bug's emails. Yes, I installed all linux-modules* and linux-headers*
packages first.

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == 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=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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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


[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-06-28 Thread Paulo Marcel Coelho Aragão
I'd like to test the patched kernel but I've stumbled across this error
when I try to install the linux-image-unsigned package and I haven't
found out how to solve it:

paulo:~/Downloads$ sudo dpkg -i 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb
dpkg: regarding 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb 
containing linux-image-unsigned-4.15.0-23-generic:
 linux-image-unsigned-4.15.0-23-generic conflicts with 
linux-image-4.15.0-23-generic
  linux-image-4.15.0-23-generic (version 4.15.0-23.25) is present and installed.

dpkg: error processing archive 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb 
(--install):
 conflicting packages - not installing linux-image-unsigned-4.15.0-23-generic
Errors were encountered while processing:
 linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb

I suspect I'm missing something very basic.

My current kernel image is: 4.15.0-23.25

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug 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=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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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


[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-06-27 Thread Paulo Marcel Coelho Aragão
I mistakenly filed this exact same bug against xorg-server [1], until
Alan Jenkins made a comment [2] about this one. I'm surprised that not
more people have reported it or registered as affected users.

[1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1775593
[2] 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1775593/comments/10

-- 
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/1776887

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug 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=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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+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