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

[Derek L]

Looks like it's in master-next (-31.33).  See https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-next
and https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-31.33#n856

-- 
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&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.

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 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

[Derek L]

I ran into this exact same problem under Artful after updating to Linux
kernel 4.13.0-38-generic.  Can anyone confirm that the fix will be
backported to Artful in an upcoming kernel update?

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

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
  The regression was introduced by patches in LP: #1730550.

  [Fix]
  Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
  e1000e now reports correct link status.

  [Test]
  With the extra commit, the e1000e starts to working again.

  [Regression Potential]
  Low.
  It says:
  Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
  So it's pretty clear this patch is to fix the regression.

  It's in upstream linux-stable, so only Arftul needs this patch.

  ===Original Bug Report===
  When my computer boots with the most recent kernel 4.13.0-38-generic, I don't 
have a working network connection. ethtool reports that my network interface 
doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
     drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137] e