[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

2018-04-16 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu Artful)
   Status: New => Confirmed

-- 
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] e1000e :00:1f.6 eth0: changing MTU from 1500

[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

2018-04-16 Thread 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]

[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

2018-04-16 Thread Kai-Heng Feng 
It should. I've already made an SRU [1] to backport this fix.

[1] https://lists.ubuntu.com/archives/kernel-team/2018-April/091539.html

-- 
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] e1000e :00:1f.6 eth0: changing MTU from 1500 to

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-16 Thread Zhanglei Mao 
The screen also get blur after ubuntu 18.04 beta2 was installed by
legacy bios on Huawei server (VGA card is SM750 which was embedded in
Hi1710 iMBC chips).  The ubuntu-destktop was installed by "apt-get
install ubuntu-desktop and init 5 to switch to x.

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

Title:
  Ubuntu 18.04 install screen becomes blur on Huawei server

Status in install-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+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 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-16 Thread Zhanglei Mao 
** Attachment added: "bure screen picture for 18.04 beta2 atfter switch to 
x-window on Huawei server"
   
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118758/+files/creen_picture_for_blur.png

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

Title:
  Ubuntu 18.04 install screen becomes blur on Huawei server

Status in install-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+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 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-16 Thread Zhanglei Mao 
** Attachment added: "sos-report for Ubuntu 18.04 after ubuntu-desktop 
installed. it also become screen blur after witch to x-window (init 5)."
   
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118756/+files/sosreport-2288Hv5-20180417044501.tar.xz

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

Title:
  Ubuntu 18.04 install screen becomes blur on Huawei server

Status in install-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+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 1762928] Comment bridged from LTC Bugzilla

2018-04-16 Thread bugproxy 
--- Comment From bssrika...@in.ibm.com 2018-04-16 05:47 EDT---
When are we getting patches 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/1762928

Title:
  [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  ---Problem Description---
  tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] 
guests on a P9 host running bionic final beta version.
   
  Contact Information = srikanth/bssrika...@in.ibm.com 
   
  ---uname output---

  16.04.04 Guest running in P8compat mode:

  Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  18.04 guest running in P8compat mode:
  Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Log into P9 Ubuntu 18.04 host, take console of guest 
`srikanth_ubuntu160404`
  2. Run TM selftests
  git clone --depth 1 https://github.com/torvalds/linux.git;cd 
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm 
run_tests

  We will observe one of the tm tests failing, mentioned below:

  selftests: tm-trap
  
  test: tm_trap_test
  tags: git_version:c18bb39
  Little-Endian machine detected. Checking if endianness flips inadvertently on 
trap in TM... yes!
  failure: tm_trap_test
  not ok 1..11 selftests:  tm-trap [FAIL]

  
  Expected result: All tm selftests should have been pass on the P8 compat 
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host 
kernel
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for srikanth/bssrika...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.


  == Comment: #2 - SRIKANTH AITHAL  - 2018-04-10
  01:32:00 ==

  
  == Comment: #3 - SRIKANTH AITHAL  - 2018-04-10 
01:33:41 ==

  
  == Comment: #4 - SRIKANTH AITHAL  - 2018-04-10 
01:34:02 ==

  
  Please pick 

   `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`

  ie. the commit that the test was written for

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762928/+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 1764367] [NEW] Xenial update to 4.4.121 stable release

2018-04-16 Thread Juerg Haefliger 
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree
   or a minimally backported form of that patch. The 4.4.121 upstream
   stable stable patch set is now available. It should be included
   in the Ubuntu kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.121 stable release shall be
   applied:

   * Linux 4.4.121
   * btrfs: preserve i_mode if __btrfs_set_acl() fails
   * bpf, x64: implement retpoline for tail call
   * dm io: fix duplicate bio completion due to missing ref count
   * mpls, nospec: Sanitize array index in mpls_label_ok()
   * net: mpls: Pull common label check into helper
   * sctp: verify size of a new chunk in _sctp_make_chunk()
   * s390/qeth: fix IPA command submission race
   * s390/qeth: fix SETIP command handling
   * sctp: fix dst refcnt leak in sctp_v6_get_dst()
   * sctp: fix dst refcnt leak in sctp_v4_get_dst
   * udplite: fix partial checksum initialization
   * ppp: prevent unregistered channels from connecting to PPP units
   * netlink: ensure to loop over all netns in genlmsg_multicast_allns()
   * net: ipv4: don't allow setting net.ipv4.route.min_pmtu below 68
   * net: fix race on decreasing number of TX queues
   * ipv6 sit: work around bogus gcc-8 -Wrestrict warning
   * hdlc_ppp: carrier detect ok, don't turn off negotiation
   * fib_semantics: Don't match route with mismatching tclassid
   * bridge: check brport attr show in brport_show
   * Revert "led: core: Fix brightness setting when setting delay_off=0"
   * x86/spectre: Fix an error message
   * leds: do not overflow sysfs buffer in led_trigger_show
   * x86/apic/vector: Handle legacy irq data correctly
   * ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux
   * btrfs: Don't clear SGID when inheriting ACLs
   * x86/syscall: Sanitize syscall table de-references under speculation fix
   * KVM: mmu: Fix overlap between public and private memslots
   * ARM: mvebu: Fix broken PL310_ERRATA_753970 selects
   * nospec: Allow index argument to have const-qualified type
   * media: m88ds3103: don't call a non-initalized function
   * cpufreq: s3c24xx: Fix broken s3c_cpufreq_init()
   * ALSA: hda: Add a power_save blacklist
   * ALSA: usb-audio: Add a quirck for B PX headphones
   * tpm_i2c_nuvoton: fix potential buffer overruns caused by bit glitches on 
the bus
   * tpm_i2c_infineon: fix potential buffer overruns caused by bit glitches on 
the bus
   * tpm: st33zp24: fix potential buffer overruns caused by bit glitches on the 
bus

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Description changed:

  
  SRU Justification
  
  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree
 or a minimally backported form of that patch. The 4.4.121 upstream
 stable stable patch set is now available. It should be included
 in the Ubuntu kernel as well.
  
 git://git.kernel.org/
  
  TEST CASE: TBD
  
 The following patches from the 4.4.121 stable release shall be
 applied:
  
- 
+* Linux 4.4.121
+* btrfs: preserve i_mode if __btrfs_set_acl() fails
+* bpf, x64: implement retpoline for tail call
+* dm io: fix duplicate bio completion due to missing ref count
+* mpls, nospec: Sanitize array index in mpls_label_ok()
+* net: mpls: Pull common label check into helper
+* sctp: verify size of a new chunk in _sctp_make_chunk()
+* s390/qeth: fix IPA command submission race
+* s390/qeth: fix SETIP command handling
+* sctp: fix dst refcnt leak in sctp_v6_get_dst()
+* sctp: fix dst refcnt leak in sctp_v4_get_dst
+* udplite: fix partial checksum initialization
+* ppp: prevent unregistered channels from connecting to PPP units
+* netlink: ensure to loop over all netns in genlmsg_multicast_allns()
+* net: ipv4: don't allow setting net.ipv4.route.min_pmtu below 68
+* net: fix race on decreasing number of TX queues
+* ipv6 sit: work around bogus gcc-8 -Wrestrict warning
+* hdlc_ppp: carrier detect ok, don't turn off negotiation
+* fib_semantics: Don't match route with mismatching tclassid
+* bridge: check brport attr show in brport_show
+* Revert "led: core: Fix brightness setting when setting delay_off=0"
+* x86/spectre: Fix an error message
+* leds: do not overflow sysfs buffer in led_trigger_show
+* x86/apic/vector: Handle legacy irq data correctly
+* ARM: dts: LogicPD Torpedo: Fix

[Kernel-packages] [Bug 1764367] Re: Xenial update to 4.4.121 stable release

2018-04-16 Thread Juerg Haefliger 
Skipped the following patch:
   * nospec: Allow index argument to have const-qualified type

This patch modifies code from upstream's Spectre v1 implementation which
we haven't pulled in yet (skipped in the update to 4.4.118:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756866/comments/2)

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

Title:
  Xenial update to 4.4.121 stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree
 or a minimally backported form of that patch. The 4.4.121 upstream
 stable stable patch set is now available. It should be included
 in the Ubuntu kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.121 stable release shall be
 applied:

 * Linux 4.4.121
 * btrfs: preserve i_mode if __btrfs_set_acl() fails
 * bpf, x64: implement retpoline for tail call
 * dm io: fix duplicate bio completion due to missing ref count
 * mpls, nospec: Sanitize array index in mpls_label_ok()
 * net: mpls: Pull common label check into helper
 * sctp: verify size of a new chunk in _sctp_make_chunk()
 * s390/qeth: fix IPA command submission race
 * s390/qeth: fix SETIP command handling
 * sctp: fix dst refcnt leak in sctp_v6_get_dst()
 * sctp: fix dst refcnt leak in sctp_v4_get_dst
 * udplite: fix partial checksum initialization
 * ppp: prevent unregistered channels from connecting to PPP units
 * netlink: ensure to loop over all netns in genlmsg_multicast_allns()
 * net: ipv4: don't allow setting net.ipv4.route.min_pmtu below 68
 * net: fix race on decreasing number of TX queues
 * ipv6 sit: work around bogus gcc-8 -Wrestrict warning
 * hdlc_ppp: carrier detect ok, don't turn off negotiation
 * fib_semantics: Don't match route with mismatching tclassid
 * bridge: check brport attr show in brport_show
 * Revert "led: core: Fix brightness setting when setting delay_off=0"
 * x86/spectre: Fix an error message
 * leds: do not overflow sysfs buffer in led_trigger_show
 * x86/apic/vector: Handle legacy irq data correctly
 * ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux
 * btrfs: Don't clear SGID when inheriting ACLs
 * x86/syscall: Sanitize syscall table de-references under speculation fix
 * KVM: mmu: Fix overlap between public and private memslots
 * ARM: mvebu: Fix broken PL310_ERRATA_753970 selects
 * nospec: Allow index argument to have const-qualified type
 * media: m88ds3103: don't call a non-initalized function
 * cpufreq: s3c24xx: Fix broken s3c_cpufreq_init()
 * ALSA: hda: Add a power_save blacklist
 * ALSA: usb-audio: Add a quirck for B PX headphones
 * tpm_i2c_nuvoton: fix potential buffer overruns caused by bit glitches on 
the bus
 * tpm_i2c_infineon: fix potential buffer overruns caused by bit glitches 
on the bus
 * tpm: st33zp24: fix potential buffer overruns caused by bit glitches on 
the bus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764367/+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 1758364] Re: add audio kernel patches for Raven

2018-04-16 Thread Timo Aaltonen 
please check the proposed kernel(s) and adjust the tags

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

Title:
  add audio kernel patches for Raven

Status in amd:
  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:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [impact]
  Raven platforms don't have audio support.

  Please include these patches in the OEM and HWE kernels for Raven
  platforms:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/pci/hda?h=v4.14.28=ca90f34e2e80597dee73c2e8d55de364a34c112b
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/pci/hda?h=v4.14.28=b177556318a731878a1e9e8a9bb28b98f7bc832c

  [test case]
  boot a kernel with the backported commits on such a system, test that audio 
works.

  [regression potential]
  none, they just add a pci-id and fix a typo

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1758364/+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 1764377] [NEW] [Ubuntu 18.04] Guest fails to boot with "console=ttyS0, 115200" included in kernel param

2018-04-16 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

== Comment: #0 - Balamuruhan S  - 2018-03-29 01:36:52 
==
---Problem Description---
Guest fails to boot with Call Trace by using "console=ttyS0,115200" in kernel 
param

Using latest kernel suggested by Bug 166023 in Host and Guest
 
Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
 
---uname output---
# uname -a Linux ltc-boston17 4.15.0-12-generic #13 SMP Tue Mar 27 08:20:19 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = Boston 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
1. Have a healthy guest booted with latest kernel
2. Boot the guest and enter grub menu to edit kernel param
2. append "console=ttyS0,115200" to kernel param and try to boot
3. Guest fails to boot and goes to shutoff state with Call Trace
 
Call Trace:
[9.184631] random: crng init done
[9.330927] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
[9.330927] 
[9.332928] CPU: 25 PID: 1 Comm: init Not tainted 4.15.0-12-generic #13
 [9.334375] Call Trace:
[9.335077] [c007fd10bc30] [c0ce991c] dump_stack+0xb0/0xf4 
(unreliable)
[9.336334] [c007fd10bc70] [c010b4a0] panic+0x148/0x328
[9.337339] [c007fd10bd10] [c0112888] do_exit+0xc78/0xc80
[9.338359] [c007fd10bdd0] [c0112960] do_group_exit+0x60/0x100
[9.339216] [c007fd10be10] [c0112a24] SyS_exit_group+0x24/0x30
[9.340113] [c007fd10be30] [c000b184] system_call+0x58/0x6c

Oops output:
 no
 
System Dump Info:
  The system is not configured to capture a system dump.
 
*Additional Instructions for Balamuruhan S / balamuruh...@in.ibm.com: 
-Post a private note with access information to the machine that the bug is 
occuring on. 
-Attach sysctl -a output output to the bug.

== Comment: #7 - Balamuruhan S  - 2018-04-13
04:28:22 ==


I have hit it while booting already installed guest from qcow2 and edited its 
commandline from grub menu, so I have attached the full boot log.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-166200 severity-high 
targetmilestone-inin---
-- 
[Ubuntu 18.04] Guest fails to boot with "console=ttyS0,115200" included in 
kernel param
https://bugs.launchpad.net/bugs/1764377
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1758305] Re: Panic during SyS_reboot

2018-04-16 Thread Metta Crawler 
Please see comment #4

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

Title:
  Panic during SyS_reboot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  BUG: unable to handle kernel NULL pointer dereference at (null)
  IP: device_shutdown+0xbb/0x200
  PGD 0 P4D 0
  Oops: 0002 [#1] SMP NOPTI

  See the screenshot for more.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ksta   1624 F pulseaudio
   /dev/snd/controlC2:  ksta   1624 F pulseaudio
   /dev/snd/controlC1:  ksta   1624 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 07:01:58 2018
  InstallationDate: Installed on 2018-03-13 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22b
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

2018-04-16 Thread bugproxy 
Default Comment by Bridge

** Attachment added: "Boot_log"
   https://bugs.launchpad.net/bugs/1764377/+attachment/5117901/+files/Boot.log

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  [Ubuntu 18.04] Guest fails to boot with "console=ttyS0,115200"
  included in kernel param

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Balamuruhan S  - 2018-03-29 
01:36:52 ==
  ---Problem Description---
  Guest fails to boot with Call Trace by using "console=ttyS0,115200" in kernel 
param

  Using latest kernel suggested by Bug 166023 in Host and Guest
   
  Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
   
  ---uname output---
  # uname -a Linux ltc-boston17 4.15.0-12-generic #13 SMP Tue Mar 27 08:20:19 
CDT 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Have a healthy guest booted with latest kernel
  2. Boot the guest and enter grub menu to edit kernel param
  2. append "console=ttyS0,115200" to kernel param and try to boot
  3. Guest fails to boot and goes to shutoff state with Call Trace
   
  Call Trace:
  [9.184631] random: crng init done
  [9.330927] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [9.330927] 
  [9.332928] CPU: 25 PID: 1 Comm: init Not tainted 4.15.0-12-generic #13
   [9.334375] Call Trace:
  [9.335077] [c007fd10bc30] [c0ce991c] dump_stack+0xb0/0xf4 
(unreliable)
  [9.336334] [c007fd10bc70] [c010b4a0] panic+0x148/0x328
  [9.337339] [c007fd10bd10] [c0112888] do_exit+0xc78/0xc80
  [9.338359] [c007fd10bdd0] [c0112960] do_group_exit+0x60/0x100
  [9.339216] [c007fd10be10] [c0112a24] SyS_exit_group+0x24/0x30
  [9.340113] [c007fd10be30] [c000b184] system_call+0x58/0x6c

  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Balamuruhan S / balamuruh...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  == Comment: #7 - Balamuruhan S  - 2018-04-13
  04:28:22 ==

  
  I have hit it while booting already installed guest from qcow2 and edited its 
commandline from grub menu, so I have attached the full boot log.

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

<    1   2   3