[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

** Changed in: linux-lts-xenial (Ubuntu Xenial)
 Assignee: Eric Desrochers (slashd) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-xenial - 4.4.0-42.62~14.04.1

---
linux-lts-xenial (4.4.0-42.62~14.04.1) trusty; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of FOU/GUE

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (4.4.0-41.61) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1628204

  * nvme drive probe failure (LP: #1626894)
- (fix) NVMe: Don't unmap controller registers on reset

linux (4.4.0-40.60) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1627074

  * Permission denied in CIFS with kernel 4.4.0-38 (LP: #1626112)
- Fix memory leaks in cifs_do_mount()
- Compare prepaths when comparing superblocks
- SAUCE: Fix regression which breaks DFS mounting

  * Backlight does not change when adjust it higher than 50% after S3
(LP: #1625932)
- SAUCE: i915_bpo: drm/i915/backlight: setup and cache pwm alternate
  increment value
- SAUCE: i915_bpo: drm/i915/backlight: setup backlight pwm alternate
  increment on backlight enable

linux (4.4.0-39.59) xenial; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1625303

  * thunder: chip errata w/ multiple CQEs for a TSO packet (LP: #1624569)
- net: thunderx: Fix for issues with multiple CQEs posted for a TSO packet

  * thunder: faulty TSO padding (LP: #1623627)
- net: thunderx: Fix for HW issue while padding TSO packet

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * Sennheiser Officerunner - cannot get freq at ep 0x83 (LP: #1622763)
- SAUCE: (no-up) ALSA: usb-audio: Add quirk for sennheiser officerunner

  * Backport E3 Skylake Support in ie31200_edac to Xenial (LP: #1619766)
- EDAC, ie31200_edac: Add Skylake support

  * Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices (LP: #1602724)
- SAUCE: nvme: Don't suspend admin queue that wasn't created

  * ISST-LTE:pNV: system ben is hung during ST (nvme) (LP: #1620317)
- blk-mq: Allow timeouts to run while queue is freezing
- blk-mq: improve warning for running a queue on the wrong CPU
- blk-mq: don't overwrite rq->mq_ctx

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

  * radeon: monitor connected to onboard VGA doesn't work with Xenial
(LP: #1600092)
- drm/radeon/dp: add back special handling for NUTMEG

  * initramfs includes qle driver, but not firmware (LP: #1623187)
- qed: add MODULE_FIRMWARE()

  * [Hyper-V] Rebase Hyper-V to 4.7.2 (stable) (LP: #1616677)
- hv_netvsc: Implement support for VF drivers on Hyper-V
- hv_netvsc: Fix the list processing for network change event
- Drivers: hv: vmbus: Introduce functions for estimating room in the ring
  buffer
- Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile
- Drivers: hv: vmbus: Export the vmbus_set_event() API
- lcoking/barriers, arch: Use smp barriers in smp_store_release()
- asm-generic: guard smp_store_release/load_acquire
- x86: reuse asm-generic/barrier.h
- asm-generic: add __smp_xxx wrappers
- x86: define __smp_xxx
- asm-generic: implement virt_xxx memory barriers
- Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h
- Drivers: hv: vmbus: Implement APIs to support "in place" consumption of
  vmbus packets
- drivers:hv: Lock access to hyperv_mmio resource tree
- drivers:hv: Make a function to free mmio regions through vmbus
- drivers:hv: Track allocations of children of hv_vmbus in private resource
  tree
- drivers:hv: Separate out frame buffer logic when picking MMIO range
- Drivers: hv: vmbus: handle various crash scenarios
- Drivers: hv: balloon: don't crash when memory is added in non-sorted order
- Drivers: hv: balloon: reset host_specified_ha_region
- tools: hv: lsvmbus: add pci pass-through UUID
- hv_netvsc: move start_remove flag to net_device_context
- hv_netvsc: use start_remove flag to protect netvsc_link_change()
- hv_netvsc: untangle the pointer mess
- hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
- hv_netvsc: synchronize netvsc_change_mtu()/netvsc_set_channels() with
  netvsc_remove()
- hv_netvsc: set nvdev link after populating chn_table
- hv_netvsc: Fix VF register on vlan devices
- hv_netvsc: remove redundant assignment in netvsc_recv_callback()
- hv_netvsc: introduce {net, hv}_device_to_netvsc_device() helpers
- hv_netvsc: pass struct netvsc_device to rndis_filter_{open, close}()
- hv_netvsc: pass struct net_device to rndis_filter_set_device_mac()
- hv_netvsc: pass struct net_device to 

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Launchpad Bug Tracker]

This bug was fixed in the package linux-lts-xenial - 4.4.0-42.62~14.04.1

---
linux-lts-xenial (4.4.0-42.62~14.04.1) trusty; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of FOU/GUE

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (4.4.0-41.61) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1628204

  * nvme drive probe failure (LP: #1626894)
- (fix) NVMe: Don't unmap controller registers on reset

linux (4.4.0-40.60) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1627074

  * Permission denied in CIFS with kernel 4.4.0-38 (LP: #1626112)
- Fix memory leaks in cifs_do_mount()
- Compare prepaths when comparing superblocks
- SAUCE: Fix regression which breaks DFS mounting

  * Backlight does not change when adjust it higher than 50% after S3
(LP: #1625932)
- SAUCE: i915_bpo: drm/i915/backlight: setup and cache pwm alternate
  increment value
- SAUCE: i915_bpo: drm/i915/backlight: setup backlight pwm alternate
  increment on backlight enable

linux (4.4.0-39.59) xenial; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1625303

  * thunder: chip errata w/ multiple CQEs for a TSO packet (LP: #1624569)
- net: thunderx: Fix for issues with multiple CQEs posted for a TSO packet

  * thunder: faulty TSO padding (LP: #1623627)
- net: thunderx: Fix for HW issue while padding TSO packet

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * Sennheiser Officerunner - cannot get freq at ep 0x83 (LP: #1622763)
- SAUCE: (no-up) ALSA: usb-audio: Add quirk for sennheiser officerunner

  * Backport E3 Skylake Support in ie31200_edac to Xenial (LP: #1619766)
- EDAC, ie31200_edac: Add Skylake support

  * Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices (LP: #1602724)
- SAUCE: nvme: Don't suspend admin queue that wasn't created

  * ISST-LTE:pNV: system ben is hung during ST (nvme) (LP: #1620317)
- blk-mq: Allow timeouts to run while queue is freezing
- blk-mq: improve warning for running a queue on the wrong CPU
- blk-mq: don't overwrite rq->mq_ctx

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

  * radeon: monitor connected to onboard VGA doesn't work with Xenial
(LP: #1600092)
- drm/radeon/dp: add back special handling for NUTMEG

  * initramfs includes qle driver, but not firmware (LP: #1623187)
- qed: add MODULE_FIRMWARE()

  * [Hyper-V] Rebase Hyper-V to 4.7.2 (stable) (LP: #1616677)
- hv_netvsc: Implement support for VF drivers on Hyper-V
- hv_netvsc: Fix the list processing for network change event
- Drivers: hv: vmbus: Introduce functions for estimating room in the ring
  buffer
- Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile
- Drivers: hv: vmbus: Export the vmbus_set_event() API
- lcoking/barriers, arch: Use smp barriers in smp_store_release()
- asm-generic: guard smp_store_release/load_acquire
- x86: reuse asm-generic/barrier.h
- asm-generic: add __smp_xxx wrappers
- x86: define __smp_xxx
- asm-generic: implement virt_xxx memory barriers
- Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h
- Drivers: hv: vmbus: Implement APIs to support "in place" consumption of
  vmbus packets
- drivers:hv: Lock access to hyperv_mmio resource tree
- drivers:hv: Make a function to free mmio regions through vmbus
- drivers:hv: Track allocations of children of hv_vmbus in private resource
  tree
- drivers:hv: Separate out frame buffer logic when picking MMIO range
- Drivers: hv: vmbus: handle various crash scenarios
- Drivers: hv: balloon: don't crash when memory is added in non-sorted order
- Drivers: hv: balloon: reset host_specified_ha_region
- tools: hv: lsvmbus: add pci pass-through UUID
- hv_netvsc: move start_remove flag to net_device_context
- hv_netvsc: use start_remove flag to protect netvsc_link_change()
- hv_netvsc: untangle the pointer mess
- hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
- hv_netvsc: synchronize netvsc_change_mtu()/netvsc_set_channels() with
  netvsc_remove()
- hv_netvsc: set nvdev link after populating chn_table
- hv_netvsc: Fix VF register on vlan devices
- hv_netvsc: remove redundant assignment in netvsc_recv_callback()
- hv_netvsc: introduce {net, hv}_device_to_netvsc_device() helpers
- hv_netvsc: pass struct netvsc_device to rndis_filter_{open, close}()
- hv_netvsc: pass struct net_device to rndis_filter_set_device_mac()
- hv_netvsc: pass struct net_device to 

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-42.62

---
linux (4.4.0-42.62) xenial; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of FOU/GUE

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (4.4.0-41.61) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1628204

  * nvme drive probe failure (LP: #1626894)
- (fix) NVMe: Don't unmap controller registers on reset

linux (4.4.0-40.60) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1627074

  * Permission denied in CIFS with kernel 4.4.0-38 (LP: #1626112)
- Fix memory leaks in cifs_do_mount()
- Compare prepaths when comparing superblocks
- SAUCE: Fix regression which breaks DFS mounting

  * Backlight does not change when adjust it higher than 50% after S3
(LP: #1625932)
- SAUCE: i915_bpo: drm/i915/backlight: setup and cache pwm alternate
  increment value
- SAUCE: i915_bpo: drm/i915/backlight: setup backlight pwm alternate
  increment on backlight enable

linux (4.4.0-39.59) xenial; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1625303

  * thunder: chip errata w/ multiple CQEs for a TSO packet (LP: #1624569)
- net: thunderx: Fix for issues with multiple CQEs posted for a TSO packet

  * thunder: faulty TSO padding (LP: #1623627)
- net: thunderx: Fix for HW issue while padding TSO packet

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * Sennheiser Officerunner - cannot get freq at ep 0x83 (LP: #1622763)
- SAUCE: (no-up) ALSA: usb-audio: Add quirk for sennheiser officerunner

  * Backport E3 Skylake Support in ie31200_edac to Xenial (LP: #1619766)
- EDAC, ie31200_edac: Add Skylake support

  * Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices (LP: #1602724)
- SAUCE: nvme: Don't suspend admin queue that wasn't created

  * ISST-LTE:pNV: system ben is hung during ST (nvme) (LP: #1620317)
- blk-mq: Allow timeouts to run while queue is freezing
- blk-mq: improve warning for running a queue on the wrong CPU
- blk-mq: don't overwrite rq->mq_ctx

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

  * radeon: monitor connected to onboard VGA doesn't work with Xenial
(LP: #1600092)
- drm/radeon/dp: add back special handling for NUTMEG

  * initramfs includes qle driver, but not firmware (LP: #1623187)
- qed: add MODULE_FIRMWARE()

  * [Hyper-V] Rebase Hyper-V to 4.7.2 (stable) (LP: #1616677)
- hv_netvsc: Implement support for VF drivers on Hyper-V
- hv_netvsc: Fix the list processing for network change event
- Drivers: hv: vmbus: Introduce functions for estimating room in the ring
  buffer
- Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile
- Drivers: hv: vmbus: Export the vmbus_set_event() API
- lcoking/barriers, arch: Use smp barriers in smp_store_release()
- asm-generic: guard smp_store_release/load_acquire
- x86: reuse asm-generic/barrier.h
- asm-generic: add __smp_xxx wrappers
- x86: define __smp_xxx
- asm-generic: implement virt_xxx memory barriers
- Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h
- Drivers: hv: vmbus: Implement APIs to support "in place" consumption of
  vmbus packets
- drivers:hv: Lock access to hyperv_mmio resource tree
- drivers:hv: Make a function to free mmio regions through vmbus
- drivers:hv: Track allocations of children of hv_vmbus in private resource
  tree
- drivers:hv: Separate out frame buffer logic when picking MMIO range
- Drivers: hv: vmbus: handle various crash scenarios
- Drivers: hv: balloon: don't crash when memory is added in non-sorted order
- Drivers: hv: balloon: reset host_specified_ha_region
- tools: hv: lsvmbus: add pci pass-through UUID
- hv_netvsc: move start_remove flag to net_device_context
- hv_netvsc: use start_remove flag to protect netvsc_link_change()
- hv_netvsc: untangle the pointer mess
- hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
- hv_netvsc: synchronize netvsc_change_mtu()/netvsc_set_channels() with
  netvsc_remove()
- hv_netvsc: set nvdev link after populating chn_table
- hv_netvsc: Fix VF register on vlan devices
- hv_netvsc: remove redundant assignment in netvsc_recv_callback()
- hv_netvsc: introduce {net, hv}_device_to_netvsc_device() helpers
- hv_netvsc: pass struct netvsc_device to rndis_filter_{open, close}()
- hv_netvsc: pass struct net_device to rndis_filter_set_device_mac()
- hv_netvsc: pass struct net_device to rndis_filter_set_offload_params()
- netvsc: get 

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-42.62

---
linux (4.4.0-42.62) xenial; urgency=low

  * Fix GRO recursion overflow for tunneling protocols (LP: #1631287)
- tunnels: Don't apply GRO to multiple layers of encapsulation.
- gro: Allow tunnel stacking in the case of FOU/GUE

  * CVE-2016-7039
- SAUCE: net: add recursion limit to GRO

linux (4.4.0-41.61) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1628204

  * nvme drive probe failure (LP: #1626894)
- (fix) NVMe: Don't unmap controller registers on reset

linux (4.4.0-40.60) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1627074

  * Permission denied in CIFS with kernel 4.4.0-38 (LP: #1626112)
- Fix memory leaks in cifs_do_mount()
- Compare prepaths when comparing superblocks
- SAUCE: Fix regression which breaks DFS mounting

  * Backlight does not change when adjust it higher than 50% after S3
(LP: #1625932)
- SAUCE: i915_bpo: drm/i915/backlight: setup and cache pwm alternate
  increment value
- SAUCE: i915_bpo: drm/i915/backlight: setup backlight pwm alternate
  increment on backlight enable

linux (4.4.0-39.59) xenial; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
- LP: #1625303

  * thunder: chip errata w/ multiple CQEs for a TSO packet (LP: #1624569)
- net: thunderx: Fix for issues with multiple CQEs posted for a TSO packet

  * thunder: faulty TSO padding (LP: #1623627)
- net: thunderx: Fix for HW issue while padding TSO packet

  * CVE-2016-6828
- tcp: fix use after free in tcp_xmit_retransmit_queue()

  * Sennheiser Officerunner - cannot get freq at ep 0x83 (LP: #1622763)
- SAUCE: (no-up) ALSA: usb-audio: Add quirk for sennheiser officerunner

  * Backport E3 Skylake Support in ie31200_edac to Xenial (LP: #1619766)
- EDAC, ie31200_edac: Add Skylake support

  * Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices (LP: #1602724)
- SAUCE: nvme: Don't suspend admin queue that wasn't created

  * ISST-LTE:pNV: system ben is hung during ST (nvme) (LP: #1620317)
- blk-mq: Allow timeouts to run while queue is freezing
- blk-mq: improve warning for running a queue on the wrong CPU
- blk-mq: don't overwrite rq->mq_ctx

  * lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
(LP: #1619918)
- btrfs: bugfix: handle FS_IOC32_{GETFLAGS, SETFLAGS, GETVERSION} in
  btrfs_ioctl

  * radeon: monitor connected to onboard VGA doesn't work with Xenial
(LP: #1600092)
- drm/radeon/dp: add back special handling for NUTMEG

  * initramfs includes qle driver, but not firmware (LP: #1623187)
- qed: add MODULE_FIRMWARE()

  * [Hyper-V] Rebase Hyper-V to 4.7.2 (stable) (LP: #1616677)
- hv_netvsc: Implement support for VF drivers on Hyper-V
- hv_netvsc: Fix the list processing for network change event
- Drivers: hv: vmbus: Introduce functions for estimating room in the ring
  buffer
- Drivers: hv: vmbus: Use READ_ONCE() to read variables that are volatile
- Drivers: hv: vmbus: Export the vmbus_set_event() API
- lcoking/barriers, arch: Use smp barriers in smp_store_release()
- asm-generic: guard smp_store_release/load_acquire
- x86: reuse asm-generic/barrier.h
- asm-generic: add __smp_xxx wrappers
- x86: define __smp_xxx
- asm-generic: implement virt_xxx memory barriers
- Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h
- Drivers: hv: vmbus: Implement APIs to support "in place" consumption of
  vmbus packets
- drivers:hv: Lock access to hyperv_mmio resource tree
- drivers:hv: Make a function to free mmio regions through vmbus
- drivers:hv: Track allocations of children of hv_vmbus in private resource
  tree
- drivers:hv: Separate out frame buffer logic when picking MMIO range
- Drivers: hv: vmbus: handle various crash scenarios
- Drivers: hv: balloon: don't crash when memory is added in non-sorted order
- Drivers: hv: balloon: reset host_specified_ha_region
- tools: hv: lsvmbus: add pci pass-through UUID
- hv_netvsc: move start_remove flag to net_device_context
- hv_netvsc: use start_remove flag to protect netvsc_link_change()
- hv_netvsc: untangle the pointer mess
- hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
- hv_netvsc: synchronize netvsc_change_mtu()/netvsc_set_channels() with
  netvsc_remove()
- hv_netvsc: set nvdev link after populating chn_table
- hv_netvsc: Fix VF register on vlan devices
- hv_netvsc: remove redundant assignment in netvsc_recv_callback()
- hv_netvsc: introduce {net, hv}_device_to_netvsc_device() helpers
- hv_netvsc: pass struct netvsc_device to rndis_filter_{open, close}()
- hv_netvsc: pass struct net_device to rndis_filter_set_device_mac()
- hv_netvsc: pass struct net_device to rndis_filter_set_offload_params()
- netvsc: get 

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

ubuntu@10-10-238-247:~$ apt-cache policy linux-generic-lts-xenial
linux-generic-lts-xenial:
  Installed: 4.4.0.41.30
  Candidate: 4.4.0.41.30
  Version table:
 *** 4.4.0.41.30 0
500 http://ubuntu.mirrors.ucloud.cn/ubuntu/ trusty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status

ubuntu@10-10-238-247:~$ uname -a
Linux 10-10-238-247 4.4.0-41-generic #61~14.04.1-Ubuntu SMP Tue Sep 27 18:55:22 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

8 cores vm

works as expected

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

** Changed in: linux-lts-xenial (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: Invalid => In Progress

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

proton, Dale Hamel and all.

Please test this proposed kernel. Details can be found in comment #28.

Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

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

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Tim Gardner]

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

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

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

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

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Eric Desrochers (slashd)
   Status: In Progress

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

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: In Progress => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: In Progress => Invalid

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

** Also affects: linux-lts-xenial (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: New => In Progress

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

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
 Assignee: Eric Desrochers (slashd) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: linux-lts-xenial (Ubuntu Trusty)
 Assignee: (unassigned) => Eric Desrochers (slashd)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

Patches applied in origin/master-next

For more details:
https://wiki.ubuntu.com/KernelTeam/Newsletter

Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

Update:

kernel-team acks on the patches.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

Fix submitted to kernel-t...@lists.ubuntu.com

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

** Description changed:

  [Impact]
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached. The
  panic dump was collected via serial console, as the kernel panics so
  early that we cannot kdump it.
  
  [ 2.650512] [] blk_mq_register_disk+0xa6/0x160
  [ 2.656675] [] blk_register_queue+0xb4/0x160
  [ 2.662661] [] add_disk+0x1ce/0x490
  [ 2.667869] [] loop_add+0x1f0/0x270
  
  [Test Case]
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached.
  
  [Regression Potential]
  
   * Fix implemented upstream starting with v4.6-rc1
  
   * The fix is fairly straightfoward given the stack trace and the
  upstream fix.
  
-  * The fix is hard to verify, but user "Proton" was able to confirmed the 
test kernel including the fix solve this particular problem: 
+  * The fix is hard to verify, but user "Proton" was able to confirmed
+ that upstream mainline 4.6-rc1 solve the situation and that the test
+ kernel I have provided including the fix solves this particular problem
+ as well.
+ 
+ Confirmation by Proton :
  
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/comments/23
  
  [Other Info]
  
   * https://lkml.org/lkml/2016/3/16/40
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e0e827b9
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=897bb0c7
  
  [Original Description]
  We discovered a pretty serious regression introduced in 4.4.0-18.
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached. The
  panic dump was collected via serial console, as the kernel panics so
  early that we cannot kdump it.
  
  [2.650512]  [] blk_mq_register_disk+0xa6/0x160
  [2.656675]  [] blk_register_queue+0xb4/0x160
  [2.662661]  [] add_disk+0x1ce/0x490
  [2.667869]  [] loop_add+0x1f0/0x270
  
  This seems somewhat similar to https://lkml.org/lkml/2016/3/16/40, but
  the trace is not identical.
  
  We discovered this issue when we were experimenting with linux-generic-
  lts-xenial from trusty-updates on a 14.04 installation. When we
  installed it, 4.4.0-15 was the current package, and it worked fine and
  provided a large amount of improvements for us. Background security
  updates installed 4.4.0-18, and this updated and grub and became the
  default kernel. On a reboot, the node panics about 2 seconds in,
  resulting in a machine in a dead state. We were able to boot a rescue
  image and roll bac kto 4.4.0-15, which works nicely. We currently have
  pinning on 4.4.0-15 to prevent this problem from coming back, but would
  prefer to see the problem fixed.
  
  I'll attach lspci, lshw, and dmidecode for our hardware as well, but
  this is happening on pretty vanilla supermicro nodes. We are able to
  consistently reproduce it on our hardware. It is not reproducible in
  EC2, only on metal.

** Description changed:

  [Impact]
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached. The
  panic dump was collected via serial console, as the kernel panics so
  early that we cannot kdump it.
  
  [ 2.650512] [] blk_mq_register_disk+0xa6/0x160
  [ 2.656675] [] blk_register_queue+0xb4/0x160
  [ 2.662661] [] add_disk+0x1ce/0x490
  [ 2.667869] [] loop_add+0x1f0/0x270
  
  [Test Case]
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached.
  
  [Regression Potential]
  
   * Fix implemented upstream starting with v4.6-rc1
- 
-  * The fix is fairly straightfoward given the stack trace and the
- upstream fix.
  
   * The fix is hard to verify, but user "Proton" was able to confirmed
  that upstream mainline 4.6-rc1 solve the situation and that the test
  kernel I have provided including the fix solves this particular problem
  as well.
  
  Confirmation by Proton :
  
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/comments/23
  
  [Other Info]
  
   * https://lkml.org/lkml/2016/3/16/40
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e0e827b9
   * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=897bb0c7
  
  [Original Description]
  We discovered a pretty serious regression introduced in 4.4.0-18.
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached. The
  panic dump was collected via serial console, as the kernel panics so
  early that we cannot kdump it.
  
  [2.650512]  [] blk_mq_register_disk+0xa6/0x160
  [2.656675]  [] blk_register_queue+0xb4/0x160
  [2.662661]  [] add_disk+0x1ce/0x490
  [2.667869]  [] 

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

** Description changed:

+ [Impact]
+ 
+ At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
+ a snippet of the track is below, and full panic dump is attached. The
+ panic dump was collected via serial console, as the kernel panics so
+ early that we cannot kdump it.
+ 
+ [ 2.650512] [] blk_mq_register_disk+0xa6/0x160
+ [ 2.656675] [] blk_register_queue+0xb4/0x160
+ [ 2.662661] [] add_disk+0x1ce/0x490
+ [ 2.667869] [] loop_add+0x1f0/0x270
+ 
+ [Test Case]
+ 
+ At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
+ a snippet of the track is below, and full panic dump is attached.
+ 
+ [Regression Potential]
+ 
+  * Fix implemented upstream starting with v4.6-rc1
+ 
+  * The fix is fairly straightfoward given the stack trace and the
+ upstream fix.
+ 
+  * The fix is hard to verify, but user "Proton" was able to confirmed
+ the test kernel including the fix solve this particular problem.
+ 
+ 
+ [Other Info]
+ 
+  * https://lkml.org/lkml/2016/3/16/40
+  * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e0e827b9
+  * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=897bb0c7
+ 
+ [Original Description]
  We discovered a pretty serious regression introduced in 4.4.0-18.
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached. The
  panic dump was collected via serial console, as the kernel panics so
  early that we cannot kdump it.
  
  [2.650512]  [] blk_mq_register_disk+0xa6/0x160
  [2.656675]  [] blk_register_queue+0xb4/0x160
  [2.662661]  [] add_disk+0x1ce/0x490
  [2.667869]  [] loop_add+0x1f0/0x270
  
  This seems somewhat similar to https://lkml.org/lkml/2016/3/16/40, but
  the trace is not identical.
  
  We discovered this issue when we were experimenting with linux-generic-
  lts-xenial from trusty-updates on a 14.04 installation. When we
  installed it, 4.4.0-15 was the current package, and it worked fine and
  provided a large amount of improvements for us. Background security
  updates installed 4.4.0-18, and this updated and grub and became the
  default kernel. On a reboot, the node panics about 2 seconds in,
  resulting in a machine in a dead state. We were able to boot a rescue
  image and roll bac kto 4.4.0-15, which works nicely. We currently have
  pinning on 4.4.0-15 to prevent this problem from coming back, but would
  prefer to see the problem fixed.
  
  I'll attach lspci, lshw, and dmidecode for our hardware as well, but
  this is happening on pretty vanilla supermicro nodes. We are able to
  consistently reproduce it on our hardware. It is not reproducible in
  EC2, only on metal.

** Description changed:

  [Impact]
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached. The
  panic dump was collected via serial console, as the kernel panics so
  early that we cannot kdump it.
  
  [ 2.650512] [] blk_mq_register_disk+0xa6/0x160
  [ 2.656675] [] blk_register_queue+0xb4/0x160
  [ 2.662661] [] add_disk+0x1ce/0x490
  [ 2.667869] [] loop_add+0x1f0/0x270
  
  [Test Case]
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached.
  
  [Regression Potential]
  
-  * Fix implemented upstream starting with v4.6-rc1
+  * Fix implemented upstream starting with v4.6-rc1
  
-  * The fix is fairly straightfoward given the stack trace and the
+  * The fix is fairly straightfoward given the stack trace and the
  upstream fix.
  
-  * The fix is hard to verify, but user "Proton" was able to confirmed
- the test kernel including the fix solve this particular problem.
- 
+  * The fix is hard to verify, but user "Proton" was able to confirmed the 
test kernel including the fix solve this particular problem: 
+ 
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/comments/23
  
  [Other Info]
  
-  * https://lkml.org/lkml/2016/3/16/40
-  * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e0e827b9
-  * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=897bb0c7
+  * https://lkml.org/lkml/2016/3/16/40
+  * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e0e827b9
+  * 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=897bb0c7
  
  [Original Description]
  We discovered a pretty serious regression introduced in 4.4.0-18.
  
  At boot-time, the kernel will panic somewhere in 'blk_mq_register_disk',
  a snippet of the track is below, and full panic dump is attached. The
  panic dump was collected via serial console, as the kernel panics so
  early that we cannot kdump it.
  
  [2.650512]  [] blk_mq_register_disk+0xa6/0x160
  [2.656675]  [] blk_register_queue+0xb4/0x160
  [2.662661]  [] add_disk+0x1ce/0x490
  [  

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

@proton,

Sorry for the late reply, I was out of the office for a couple of weeks.

Thanks for your feedbacks, I'll submit the patch to be backported into
4.4 kernel.

Note that we will need your help for testing one more time if the patch
is accepted into the -proposed archive.

I'll keep you posted !

Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

@slashd

Sorry for the delay.

The kernel you provided works as expected, while on the same machine
4.4.0-31 fails.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

@proton, have you been able to give a try at my test kernel found on
"ppa:slashd/lp1572630-proton" ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

@proton,

Here's the Xenial v4.4 test kernel for Trusty release.

Instructions:
$ sudo add-apt-repository ppa:slashd/lp1572630-proton
$ sudo apt-get update
$ sudo apt-get install linux-image-4.4.0-34-generic 
linux-image-extra-4.4.0-34-generic linux-headers-4.4.0-34-generic -y

Then reboot the system, and make sure the bootloader load the "4.4.0-34"
kernel.

Validation can be made with command :
$ uname -a

Expected uname output :
Linux  4.4.0-34-generic #53~14.04.1hf1572630v20160802b6-Ubuntu 

Regards,
Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

@slashd

Yes, we are experiencing this on Trusty (with linux-generic-lts-xenial
package).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

@Proton,

The test kernel I made is for the Xenial release, not for Trusty.

Do you experience the problem on Trusty ? Originally the problem was
reported to my on 16.04 (Xenial) so this is why I made the test kernel
for Xenial only.

I'll work on another test kernel this week (if I have time before going
on vacation) based on Xenial kernel (4.4) but for build for Trusty
release.

Regards,
Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

@slashd

Didn't use wget, I am using the procedure you described.


root@10-10-129-197:/home/ubuntu# add-apt-repository ppa:slashd/buglp1572630
 === TEST KERNEL for LP: #1572630 ===
 More info: https://launchpad.net/~slashd/+archive/ubuntu/buglp1572630
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keyring `/tmp/tmpnb1s8b51/secring.gpg' created
gpg: keyring `/tmp/tmpnb1s8b51/pubring.gpg' created
gpg: requesting key 698BC1F3 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpnb1s8b51/trustdb.gpg: trustdb created
gpg: key 698BC1F3: public key "Launchpad PPA for eric.desrochers" imported
gpg: Total number processed: 1
gpg:   imported: 1  (RSA: 1)
OK

# apt-get update
..
Hit http://ubuntu.mirrors.ucloud.cn trusty/multiverse i386 Packages
Hit http://ubuntu.mirrors.ucloud.cn trusty/main Translation-en
Hit http://ubuntu.mirrors.ucloud.cn trusty/multiverse Translation-en
Err http://ppa.launchpad.net trusty/main amd64 Packages
  404  Not Found
Err http://ppa.launchpad.net trusty/main i386 Packages
  404  Not Found
Hit http://ubuntu.mirrors.ucloud.cn trusty/restricted Translation-en
Ign http://ppa.launchpad.net trusty/main Translation-en_US
Ign http://ppa.launchpad.net trusty/main Translation-en
Hit http://ubuntu.mirrors.ucloud.cn trusty/universe Translation-en
Ign http://ubuntu.mirrors.ucloud.cn trusty/main Translation-en_US

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

@Proton,

It won't work using "wget" or else.

Here's the instruction on how to use a PPA:

$ sudo add-apt-repository ppa:slashd/buglp1572630
$ sudo apt-get update 
$ sudo apt-get install 
linux-image-4.4.0-30-generic=4.4.0-30.49hf1572630v20160706b2 -y
$ sudo apt-get install 
linux-image-extra-4.4.0-30-generic=4.4.0-30.49hf1572630v20160706b2 -y
$ sudo apt-get install 
linux-headers-4.4.0-30-generic=4.4.0-30.49hf1572630v20160706b2 -y

## Reboot the sytem and make sure, the boot loader pick the right test
kernel ##

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

@slashd

W: Failed to fetch
http://ppa.launchpad.net/slashd/buglp1572630/ubuntu/dists/trusty/main
/binary-amd64/Packages  404  Not Found

W: Failed to fetch
http://ppa.launchpad.net/slashd/buglp1572630/ubuntu/dists/trusty/main/binary-i386/Packages
404  Not Found

Can't install it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

** Changed in: linux-lts-xenial (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: linux-lts-xenial (Ubuntu)
   Importance: Critical => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

@Proton, Thanks for the feedback for v4.6-rc1.

Dale, Proton,

I built a test kernel [4.4.0-30.49hf1572630v20160706b2] based on Ubuntu Xenial 
kernel v4.4.0-30. 
It is including the fix introduced upstream in v4.6-rc1 that can be found on my 
PPA :

$ sudo add-apt-repository ppa:slashd/buglp1572630

Can you please try this 4.4 test kernel and provide feedbacks as well ?

Regards,
Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

@slashd

v4.6-rc1 works as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

** Changed in: linux-lts-xenial (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: linux-lts-xenial (Ubuntu)
 Assignee: Eric Desrochers (slashd) => (unassigned)

** Changed in: linux-lts-xenial (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

To continue my comment #11 ...

There is more commit to apply, since commit 897bb0c remove ‘int i;’[1]
in function ‘blk_mq_sysfs_init’, it won't build in function
‘blk_mq_sysfs_init’, ‘queue_for_each_hw_ctx’ still load ‘i’ as an
argument, but it is no longer declared after commit 897bb0c[1].

Commit 868f2f0[3], is removing ‘queue_for_each_hw_ctx’ from
‘blk_mq_sysfs_init’, so that might be a good idea to include 868f2f0 or
at least what is needed for this specific fix.


[1] -   int i;
[2] queue_for_each_hw_ctx(q, hctx, i)
[3] 868f2f0 blk-mq: dynamic h/w context count

Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

Hi Dale, Proton,

Can you confirm if you can reproduce the problem or not using the
mainline kernel v4.6-rc1 found in :

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/

Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

At first glance, theses 2 commits are needed to fix the issue, 897bb0c7
is the fix but won't build if e0e827b9, since it removes the function
"queue_for_each_ctx" that will no longer be defined in the header file
after "897bb0c7".

e0e827b9  blk-mq: Reuse hardware context cpumask for tags
897bb0c7  blk-mq: Use proper cpumask iterator

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Eric Desrochers]

There is an upstream fix for this issue.

First introduced upstream in branch : v4.6-rc1

---
commit 897bb0c7f1ea82d7cc882b19790b5e1df00ffc29
Author: Thomas Gleixner 
Date:   Sat Mar 19 11:30:33 2016 +0100

blk-mq: Use proper cpumask iterator

queue_for_each_ctx() iterates over per_cpu variables under the assumption 
that
the possible cpu mask cannot have holes. That's wrong as all cpumasks can 
have
holes. In case there are holes the iteration ends up accessing uninitialized
memory and crashing as a result.

Replace the macro by a proper for_each_possible_cpu() loop and drop the 
unused
macro blk_ctx_sum() which references queue_for_each_ctx().
---

Eric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

Same here, but on virtualized environment.

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+attachment/4691400/+files/Snip20160628_3.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

lspci


00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
Subsystem: Red Hat, Inc Qemu virtual machine
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

falcon-graph
description: Computer
product: KVM ()
vendor: Red Hat
version: RHEL 6.3.0 PC
width: 64 bits
capabilities: smbios-2.4 dmi-2.4 vsyscall32
configuration: boot=normal family=Red Hat Enterprise Linux 
uuid=E1EEF4B2-FA7A-41C7-A815-BF5D5437550D
  *-core
   description: Motherboard
   physical id: 0
 *-firmware
  description: BIOS
  vendor: Seabios
  physical id: 0
  version: 0.5.1
  date: 01/01/2007
  size: 96KiB
 *-cpu:0
  description: CPU
  product: Common KVM CPU
  vendor: Intel Corp.
  physical id: 401
  bus info: cpu@0
  slot: CPU 1
  size: 2GHz
  capacity: 2GHz
  width: 64 bits
  capabilities: fpu fpu_exception wp de pse tsc msr pae mce cx8 apic 
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx x86-64 
constant_tsc nopl pni cx16 sse4_1 sse4_2 x2apic popcnt aes avx hypervisor 
lahf_lm
 *-cpu:1
  description: CPU
  product: Common KVM CPU
  vendor: Intel Corp.
  physical id: 402
  bus info: cpu@1
  slot: CPU 2
  size: 2GHz
  capacity: 2GHz
  width: 64 bits
  capabilities: fpu fpu_exception wp de pse tsc msr pae mce cx8 apic 
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx x86-64 
constant_tsc nopl pni cx16 sse4_1 sse4_2 x2apic popcnt aes avx hypervisor 
lahf_lm
 *-cpu:2
  description: CPU
  product: Common KVM CPU
  vendor: Intel Corp.
  physical id: 403
  bus info: cpu@2
  slot: CPU 3
  size: 2GHz
  capacity: 2GHz
  width: 64 bits
  capabilities: fpu fpu_exception wp de pse tsc msr pae mce cx8 apic 
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx x86-64 
constant_tsc nopl pni cx16 sse4_1 sse4_2 x2apic popcnt aes avx hypervisor 
lahf_lm
 *-cpu:3
  description: CPU
  product: Common KVM CPU
  vendor: Intel Corp.
  physical id: 404
  bus info: cpu@3
  slot: CPU 4
  size: 2GHz
  capacity: 2GHz
  width: 64 bits
  capabilities: fpu fpu_exception wp de pse tsc msr pae mce cx8 apic 
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx x86-64 
constant_tsc nopl pni cx16 sse4_1 sse4_2 x2apic popcnt aes avx hypervisor 
lahf_lm
 *-memory
  description: System Memory
  physical id: 1000
  size: 8GiB
*-bank
 description: DIMM RAM
 physical id: 0
 slot: DIMM 0
 size: 8GiB
 width: 64 bits
 *-pci
  description: Host bridge
  product: 440FX - 82441FX PMC [Natoma]
  vendor: Intel Corporation
  physical id: 100
  bus info: pci@:00:00.0
  version: 02
  width: 32 bits
  clock: 33MHz
*-isa
 description: ISA bridge
 product: 82371SB PIIX3 ISA [Natoma/Triton II]
 vendor: Intel Corporation
 physical id: 1
 bus info: pci@:00:01.0
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: isa
 configuration: latency=0
*-ide
 description: IDE interface
 product: 82371SB PIIX3 IDE [Natoma/Triton II]
 vendor: Intel Corporation
 physical id: 1.1
 bus info: pci@:00:01.1
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: ide bus_master
 configuration: driver=ata_piix latency=0
 resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) 
ioport:376 ioport:c000(size=16)
*-usb
 description: USB controller
 product: 82371SB PIIX3 USB [Natoma/Triton II]
 vendor: Intel Corporation
 physical id: 1.2
 bus info: pci@:00:01.2
 version: 01
 width: 32 bits
 clock: 33MHz
 capabilities: uhci bus_master
 configuration: driver=uhci_hcd latency=0
 resources: irq:11 ioport:c020(size=32)
*-bridge
 description: Bridge
 product: 82371AB/EB/MB PIIX4 ACPI
 vendor: Intel Corporation
 physical id: 1.3
 bus info: pci@:00:01.3
 version: 03
 width: 32 bits
 clock: 33MHz
 capabilities: bridge
 configuration: driver=piix4_smbus latency=0
 resources: irq:9
*-display
 description: VGA compatible controller
 product: GD 5446
 vendor: Cirrus Logic
 physical id: 2
 bus info: pci@:00:02.0
 version: 00
 width: 32 bits
 clock: 33MHz
 

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Proton]

# dmidecode 2.12
SMBIOS 2.4 present.
15 structures occupying 479 bytes.
Table at 0xDE20.

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Seabios
Version: 0.5.1
Release Date: 01/01/2007
Address: 0xE8000
Runtime Size: 96 kB
ROM Size: 64 kB
Characteristics:
BIOS characteristics not supported
Targeted content distribution is supported
BIOS Revision: 1.0

Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Red Hat
Product Name: KVM
Version: RHEL 6.3.0 PC
Serial Number: Not Specified
UUID: E1EEF4B2-FA7A-41C7-A815-BF5D5437550D
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Red Hat Enterprise Linux

Handle 0x0300, DMI type 3, 20 bytes
Chassis Information
Manufacturer: Red Hat
Type: Other
Lock: Not Present
Version: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: Unknown
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: Unspecified

Handle 0x0401, DMI type 4, 32 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Other
Manufacturer: Bochs
ID: 61 0F 00 00 FD F3 8B 07
Version: Not Specified
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided

Handle 0x0402, DMI type 4, 32 bytes
Processor Information
Socket Designation: CPU 2
Type: Central Processor
Family: Other
Manufacturer: Bochs
ID: 61 0F 00 00 FD F3 8B 07
Version: Not Specified
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided

Handle 0x0403, DMI type 4, 32 bytes
Processor Information
Socket Designation: CPU 3
Type: Central Processor
Family: Other
Manufacturer: Bochs
ID: 61 0F 00 00 FD F3 8B 07
Version: Not Specified
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided

Handle 0x0404, DMI type 4, 32 bytes
Processor Information
Socket Designation: CPU 4
Type: Central Processor
Family: Other
Manufacturer: Bochs
ID: 61 0F 00 00 FD F3 8B 07
Version: Not Specified
Voltage: Unknown
External Clock: Unknown
Max Speed: 2000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided

Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: Other
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 1

Handle 0x1100, DMI type 17, 21 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: 0x
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: None

Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x000
Ending Address: 0x000DFFF
Range Size: 3584 MB
Physical Array Handle: 0x1000
Partition Width: 1

Handle 0x1301, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x001
Ending Address: 0x0021FFF
Range Size: 4608 MB
Physical Array Handle: 0x1000
Partition Width: 1

Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x000
Ending Address: 0x000DFFF
Range Size: 3584 MB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1

Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x001
Ending Address: 0x0021FFF
Range Size: 4608 MB
Physical Device Handle: 0x1100

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Alberto Salvia Novella]

** Changed in: linux-lts-xenial (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-lts-xenial (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Dale Hamel]

Attached is lspci

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+attachment/4640782/+files/lspci

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Dale Hamel]

Attached is dmidecode

** Attachment added: "dmidecode"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+attachment/4640781/+files/dmidecode

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572630] Re: boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

[Dale Hamel]

add lshw output

** Attachment added: "lshw"
   
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1572630/+attachment/4640783/+files/lshw

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572630

Title:
  boot-time kernel panic introduced in 4.4.0-18, not present in 4.4.0-15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs