[Kernel-packages] [Bug 1767360] Re: 16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-image-4.4.0-121-generic or linux-image-4.4.0-119-generic

2018-05-19 Thread Christopher M. Penalver
Rod B., the next step is to fully reverse commit bisect from kernel 4.4
to 4.16 in order to identify the last bad commit, followed immediately
by the first good one. Once this good commit has been identified, it may
be reviewed for backporting. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions, or providing a commit
from a kernel version bisect is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Description changed:

  I am reporting this using the most recent auto updated version of the
  kernel linux-image-4.4.0-122-generic. But boot also fails on the two
  previous auto updated images linux-image-4.4.0-121-generic and linux-
  image-4.4.0-119-generic.
  
  Last bootable kernel was linux-image-4.4.0-116-generic which is what I
  have to run to update and submit this report.
  
  The boot failures occur on two Asus S200E laptops. It does not effect my
  desktop.
  
- I can't seem to get any details about why boot is failing. It "blows up"
- and returns to BIOS warn start during or right after the ramdisk is
- loaded. It also does not matter if I select "recovery mode" kernel. I
- can boot my older kernels like 4.4.0-116-generic without a problem.
  
- Below is a link to a video of the failure. I boot the kernels in this
- order: 121, 119, 116.
- 
+ Below is a link to a video of the failure. I boot the kernels in this order: 
121, 119, 116.
  https://drive.google.com/file/d/1l_-aiRw-a5by9RkQzfDDQfHF5LbHygeZ/view
  
  I ran memory test on both laptops - no problems found.
  
  I removed options quite and splash in hopes it might show more info but
  it did not help.
  
  For what it is worth I used gunzip to test the integrity of the
  compressed initrd.img files. No errors from gunzip.
  
  The disk UUID and other options I can see from Grub edit ('e') are
  identical.
  
  Before 121 kernel update was release I uninstalled and reinstalled 119
  but that did not help. IE: sudo apt-get --purge remove linux-
  image-4.4.0-119-generic; sudo apt-get install linux-generic
  
- 
- $ lsb_release -rd
- 
- Description:  Ubuntu 16.04.4 LTS
- Release:  16.04
- 
- 
- $ cat /proc/version_signature
- 
- Ubuntu 4.4.0-116.140-generic 4.4.98  (but this is the version that boots
- so I can submit this report)
- 
- 
- $ sudo lspci -vnvn 
- 
- 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
-   Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
-   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
-   Kernel driver in use: ivb_uncore
- 
- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
-   Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
-   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
-   Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
-   Address: fee0200c  Data: 41d1
-   Capabilities: [d0] Power Management version 2
-   Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
-   Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
-   Capabilities: [a4] PCI Advanced Features
-   AFCap: TP+ FLR+
-   AFCtrl: FLR-
-   AFStatus: TP-
-   Kernel driver in use: i915
-   Kernel modules: i915
- 
- 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
-   Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
-   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
-   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
-   PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
-   Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
-   DevCap: MaxPayload 128 bytes, PhantFunc 0
-   ExtTag- RBE+
-   DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
-   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
-   MaxPayload 128 bytes, MaxReadReq 128 bytes
-   DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
-   LnkCap: Port 

[Kernel-packages] [Bug 1767360] Re: 16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-image-4.4.0-121-generic or linux-image-4.4.0-119-generic

2018-05-04 Thread Rod B.
I discovered that reducing the BIOS setting for DVMT Pre-Allocated
Memory below 512M gets around the bug. IE: The three problem kernels
listed in this report will boot if DVMT Pre-Allocated is set less then
512M. As mentioned in this report kernels 4.4.0-116 and before worked
fine with DVMT Pre-Alloc set to 512M.

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

Title:
  16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
  image-4.4.0-121-generic or linux-image-4.4.0-119-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I am reporting this using the most recent auto updated version of the
  kernel linux-image-4.4.0-122-generic. But boot also fails on the two
  previous auto updated images linux-image-4.4.0-121-generic and linux-
  image-4.4.0-119-generic.

  Last bootable kernel was linux-image-4.4.0-116-generic which is what I
  have to run to update and submit this report.

  The boot failures occur on two Asus S200E laptops. It does not effect
  my desktop.

  I can't seem to get any details about why boot is failing. It "blows
  up" and returns to BIOS warn start during or right after the ramdisk
  is loaded. It also does not matter if I select "recovery mode" kernel.
  I can boot my older kernels like 4.4.0-116-generic without a problem.

  Below is a link to a video of the failure. I boot the kernels in this
  order: 121, 119, 116.

  https://drive.google.com/file/d/1l_-aiRw-a5by9RkQzfDDQfHF5LbHygeZ/view

  I ran memory test on both laptops - no problems found.

  I removed options quite and splash in hopes it might show more info
  but it did not help.

  For what it is worth I used gunzip to test the integrity of the
  compressed initrd.img files. No errors from gunzip.

  The disk UUID and other options I can see from Grub edit ('e') are
  identical.

  Before 121 kernel update was release I uninstalled and reinstalled 119
  but that did not help. IE: sudo apt-get --purge remove linux-
  image-4.4.0-119-generic; sudo apt-get install linux-generic

  
  $ lsb_release -rd

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  
  $ cat /proc/version_signature

  Ubuntu 4.4.0-116.140-generic 4.4.98  (but this is the version that
  boots so I can submit this report)

  
  $ sudo lspci -vnvn 

  00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0200c  Data: 41d1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <16us
ClockPM- Surprise- 

[Kernel-packages] [Bug 1767360] Re: 16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-image-4.4.0-121-generic or linux-image-4.4.0-119-generic

2018-04-30 Thread Rod B.
** Tags added: kernel-fixed-upstream

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

Title:
  16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
  image-4.4.0-121-generic or linux-image-4.4.0-119-generic

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

Bug description:
  I am reporting this using the most recent auto updated version of the
  kernel linux-image-4.4.0-122-generic. But boot also fails on the two
  previous auto updated images linux-image-4.4.0-121-generic and linux-
  image-4.4.0-119-generic.

  Last bootable kernel was linux-image-4.4.0-116-generic which is what I
  have to run to update and submit this report.

  The boot failures occur on two Asus S200E laptops. It does not effect
  my desktop.

  I can't seem to get any details about why boot is failing. It "blows
  up" and returns to BIOS warn start during or right after the ramdisk
  is loaded. It also does not matter if I select "recovery mode" kernel.
  I can boot my older kernels like 4.4.0-116-generic without a problem.

  Below is a link to a video of the failure. I boot the kernels in this
  order: 121, 119, 116.

  https://drive.google.com/file/d/1l_-aiRw-a5by9RkQzfDDQfHF5LbHygeZ/view

  I ran memory test on both laptops - no problems found.

  I removed options quite and splash in hopes it might show more info
  but it did not help.

  For what it is worth I used gunzip to test the integrity of the
  compressed initrd.img files. No errors from gunzip.

  The disk UUID and other options I can see from Grub edit ('e') are
  identical.

  Before 121 kernel update was release I uninstalled and reinstalled 119
  but that did not help. IE: sudo apt-get --purge remove linux-
  image-4.4.0-119-generic; sudo apt-get install linux-generic

  
  $ lsb_release -rd

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  
  $ cat /proc/version_signature

  Ubuntu 4.4.0-116.140-generic 4.4.98  (but this is the version that
  boots so I can submit this report)

  
  $ sudo lspci -vnvn 

  00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0200c  Data: 41d1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-

[Kernel-packages] [Bug 1767360] Re: 16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-image-4.4.0-121-generic or linux-image-4.4.0-119-generic

2018-04-30 Thread Rod B.
Used kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
It boots/works.
Added tag and changed status as requested. 1st time Launchpad user so hope I 
did it correctly.

Thanks for the help.

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

Title:
  16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
  image-4.4.0-121-generic or linux-image-4.4.0-119-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I am reporting this using the most recent auto updated version of the
  kernel linux-image-4.4.0-122-generic. But boot also fails on the two
  previous auto updated images linux-image-4.4.0-121-generic and linux-
  image-4.4.0-119-generic.

  Last bootable kernel was linux-image-4.4.0-116-generic which is what I
  have to run to update and submit this report.

  The boot failures occur on two Asus S200E laptops. It does not effect
  my desktop.

  I can't seem to get any details about why boot is failing. It "blows
  up" and returns to BIOS warn start during or right after the ramdisk
  is loaded. It also does not matter if I select "recovery mode" kernel.
  I can boot my older kernels like 4.4.0-116-generic without a problem.

  Below is a link to a video of the failure. I boot the kernels in this
  order: 121, 119, 116.

  https://drive.google.com/file/d/1l_-aiRw-a5by9RkQzfDDQfHF5LbHygeZ/view

  I ran memory test on both laptops - no problems found.

  I removed options quite and splash in hopes it might show more info
  but it did not help.

  For what it is worth I used gunzip to test the integrity of the
  compressed initrd.img files. No errors from gunzip.

  The disk UUID and other options I can see from Grub edit ('e') are
  identical.

  Before 121 kernel update was release I uninstalled and reinstalled 119
  but that did not help. IE: sudo apt-get --purge remove linux-
  image-4.4.0-119-generic; sudo apt-get install linux-generic

  
  $ lsb_release -rd

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  
  $ cat /proc/version_signature

  Ubuntu 4.4.0-116.140-generic 4.4.98  (but this is the version that
  boots so I can submit this report)

  
  $ sudo lspci -vnvn 

  00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0200c  Data: 41d1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
  

[Kernel-packages] [Bug 1767360] Re: 16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-image-4.4.0-121-generic or linux-image-4.4.0-119-generic

2018-04-30 Thread Rod B.
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => 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/1767360

Title:
  16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
  image-4.4.0-121-generic or linux-image-4.4.0-119-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I am reporting this using the most recent auto updated version of the
  kernel linux-image-4.4.0-122-generic. But boot also fails on the two
  previous auto updated images linux-image-4.4.0-121-generic and linux-
  image-4.4.0-119-generic.

  Last bootable kernel was linux-image-4.4.0-116-generic which is what I
  have to run to update and submit this report.

  The boot failures occur on two Asus S200E laptops. It does not effect
  my desktop.

  I can't seem to get any details about why boot is failing. It "blows
  up" and returns to BIOS warn start during or right after the ramdisk
  is loaded. It also does not matter if I select "recovery mode" kernel.
  I can boot my older kernels like 4.4.0-116-generic without a problem.

  Below is a link to a video of the failure. I boot the kernels in this
  order: 121, 119, 116.

  https://drive.google.com/file/d/1l_-aiRw-a5by9RkQzfDDQfHF5LbHygeZ/view

  I ran memory test on both laptops - no problems found.

  I removed options quite and splash in hopes it might show more info
  but it did not help.

  For what it is worth I used gunzip to test the integrity of the
  compressed initrd.img files. No errors from gunzip.

  The disk UUID and other options I can see from Grub edit ('e') are
  identical.

  Before 121 kernel update was release I uninstalled and reinstalled 119
  but that did not help. IE: sudo apt-get --purge remove linux-
  image-4.4.0-119-generic; sudo apt-get install linux-generic

  
  $ lsb_release -rd

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  
  $ cat /proc/version_signature

  Ubuntu 4.4.0-116.140-generic 4.4.98  (but this is the version that
  boots so I can submit this report)

  
  $ sudo lspci -vnvn 

  00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0200c  Data: 41d1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- 

[Kernel-packages] [Bug 1767360] Re: 16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-image-4.4.0-121-generic or linux-image-4.4.0-119-generic

2018-04-30 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Incomplete

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

** Tags added: kernel-da-key

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

Title:
  16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
  image-4.4.0-121-generic or linux-image-4.4.0-119-generic

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

Bug description:
  I am reporting this using the most recent auto updated version of the
  kernel linux-image-4.4.0-122-generic. But boot also fails on the two
  previous auto updated images linux-image-4.4.0-121-generic and linux-
  image-4.4.0-119-generic.

  Last bootable kernel was linux-image-4.4.0-116-generic which is what I
  have to run to update and submit this report.

  The boot failures occur on two Asus S200E laptops. It does not effect
  my desktop.

  I can't seem to get any details about why boot is failing. It "blows
  up" and returns to BIOS warn start during or right after the ramdisk
  is loaded. It also does not matter if I select "recovery mode" kernel.
  I can boot my older kernels like 4.4.0-116-generic without a problem.

  Below is a link to a video of the failure. I boot the kernels in this
  order: 121, 119, 116.

  https://drive.google.com/file/d/1l_-aiRw-a5by9RkQzfDDQfHF5LbHygeZ/view

  I ran memory test on both laptops - no problems found.

  I removed options quite and splash in hopes it might show more info
  but it did not help.

  For what it is worth I used gunzip to test the integrity of the
  compressed initrd.img files. No errors from gunzip.

  The disk UUID and other options I can see from Grub edit ('e') are
  identical.

  Before 121 kernel update was release I uninstalled and reinstalled 119
  but that did not help. IE: sudo apt-get --purge remove linux-
  image-4.4.0-119-generic; sudo apt-get install linux-generic

  
  $ lsb_release -rd

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  
  $ cat /proc/version_signature

  Ubuntu 4.4.0-116.140-generic 4.4.98  (but this is the version that
  boots so I can submit this report)

  
  $ sudo lspci -vnvn 

  00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0200c  Data: 41d1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. VivoBook X202EV [1043:108d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-