[Kernel-packages] [Bug 1787159] Re: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1787159 Title: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787159] Re: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1022.22~16.04.1
---
linux-azure (4.15.0-1022.22~16.04.1) xenial; urgency=medium
* linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker (LP: #1787159)
* linux-azure: 4.15.0-1022.22 -proposed tracker (LP: #1787155)
* linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
(LP: #1785822)
- [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390
* HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix
sockets
* Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process
* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes
* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook
* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5
* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode
* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
* Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound
* Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
* CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
sockfs_setattr()
* CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree
* change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION
* Cephfs + fscache: unable to handle kernel NULL pointer dereference at
IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info
* Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52
* xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started
* CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation
* CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
* CVE-2018-11412
- ext4: do not allow external inodes for inline data
* CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data
* CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size
* CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions
* Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT
* CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp
* other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directori
[Kernel-packages] [Bug 1787155] Re: linux-azure: 4.15.0-1022.23 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1022.22~16.04.1
---
linux-azure (4.15.0-1022.22~16.04.1) xenial; urgency=medium
* linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker (LP: #1787159)
* linux-azure: 4.15.0-1022.22 -proposed tracker (LP: #1787155)
* linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
(LP: #1785822)
- [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390
* HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix
sockets
* Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process
* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes
* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook
* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5
* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode
* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
* Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound
* Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
* CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
sockfs_setattr()
* CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree
* change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION
* Cephfs + fscache: unable to handle kernel NULL pointer dereference at
IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info
* Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52
* xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started
* CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation
* CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
* CVE-2018-11412
- ext4: do not allow external inodes for inline data
* CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data
* CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size
* CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions
* Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT
* CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp
* other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directori
[Kernel-packages] [Bug 1785822] Re: linux-azure: make sure CONFIG_MLX{4, 5}_INFINIBAND stays as "y"
This bug was fixed in the package linux-azure - 4.15.0-1022.22~16.04.1
---
linux-azure (4.15.0-1022.22~16.04.1) xenial; urgency=medium
* linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker (LP: #1787159)
* linux-azure: 4.15.0-1022.22 -proposed tracker (LP: #1787155)
* linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
(LP: #1785822)
- [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390
* HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix
sockets
* Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process
* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes
* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook
* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5
* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode
* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
* Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound
* Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
* CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
sockfs_setattr()
* CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree
* change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION
* Cephfs + fscache: unable to handle kernel NULL pointer dereference at
IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info
* Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52
* xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started
* CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation
* CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
* CVE-2018-11412
- ext4: do not allow external inodes for inline data
* CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data
* CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size
* CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions
* Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT
* CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp
* other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directori
[Kernel-packages] [Bug 1787155] Re: linux-azure: 4.15.0-1022.23 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1022.23
---
linux-azure (4.15.0-1022.23) bionic; urgency=medium
* linux-azure: 4.15.0-1022.23 -proposed tracker (LP: #1787155)
* linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
(LP: #1785822)
- [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390
* HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix
sockets
* Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process
* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes
* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook
* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5
* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode
* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
* Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound
* Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
* CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
sockfs_setattr()
* CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree
* change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION
* Cephfs + fscache: unable to handle kernel NULL pointer dereference at
IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info
* Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52
* xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started
* CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation
* CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
* CVE-2018-11412
- ext4: do not allow external inodes for inline data
* CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data
* CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size
* CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions
* Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT
* CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp
* other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directories
* Invoking obsolete 'firmware_install' target breaks snap build (LP: #1782166)
-
[Kernel-packages] [Bug 1787155] Re: linux-azure: 4.15.0-1022.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1787155 Title: linux-azure: 4.15.0-1022.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785822] Re: linux-azure: make sure CONFIG_MLX{4, 5}_INFINIBAND stays as "y"
This bug was fixed in the package linux-azure - 4.15.0-1022.23
---
linux-azure (4.15.0-1022.23) bionic; urgency=medium
* linux-azure: 4.15.0-1022.23 -proposed tracker (LP: #1787155)
* linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
(LP: #1785822)
- [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390
* HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix
sockets
* Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process
* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes
* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook
* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5
* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode
* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
* Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound
* Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
* CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
sockfs_setattr()
* CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree
* change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION
* Cephfs + fscache: unable to handle kernel NULL pointer dereference at
IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info
* Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52
* xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started
* CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation
* CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
* CVE-2018-11412
- ext4: do not allow external inodes for inline data
* CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data
* CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size
* CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions
* Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT
* CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp
* other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directories
* Invoking obsolete 'firmware_install' target breaks snap build (LP: #1782166)
-
[Kernel-packages] [Bug 1785822] Re: linux-azure: make sure CONFIG_MLX{4, 5}_INFINIBAND stays as "y"
This bug was fixed in the package linux-azure - 4.15.0-1022.22~16.04.1
---
linux-azure (4.15.0-1022.22~16.04.1) xenial; urgency=medium
* linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker (LP: #1787159)
* linux-azure: 4.15.0-1022.22 -proposed tracker (LP: #1787155)
* linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
(LP: #1785822)
- [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390
* HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix
sockets
* Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process
* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes
* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook
* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5
* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode
* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
* Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound
* Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
* CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
sockfs_setattr()
* CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree
* change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION
* Cephfs + fscache: unable to handle kernel NULL pointer dereference at
IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info
* Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52
* xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started
* CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation
* CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
* CVE-2018-11412
- ext4: do not allow external inodes for inline data
* CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data
* CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size
* CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions
* Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT
* CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp
* other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directori
[Kernel-packages] [Bug 1785822] Re: linux-azure: make sure CONFIG_MLX{4, 5}_INFINIBAND stays as "y"
This bug was fixed in the package linux-azure - 4.15.0-1022.23
---
linux-azure (4.15.0-1022.23) bionic; urgency=medium
* linux-azure: 4.15.0-1022.23 -proposed tracker (LP: #1787155)
* linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
(LP: #1785822)
- [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock to protect addrs list updates
- SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
* ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
- test_bpf: flag tests that cannot be jited on s390
* HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
- drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
- drm/radeon: fix radeon_atpx_get_client_id()'s return type
- drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
- platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
- ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
- vga_switcheroo: set audio client id according to bound GPU id
* locking sockets broken due to missing AppArmor socket mediation patches
(LP: #1780227)
- UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix
sockets
* Update2 for ocxl driver (LP: #1781436)
- ocxl: Fix page fault handler in case of fault on dying process
* netns: unable to follow an interface that moves to another netns
(LP: #1774225)
- net: core: Expose number of link up/down transitions
- dev: always advertise the new nsid when the netns iface changes
- dev: advertise the new ifindex when the netns iface changes
* [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
- block, bfq: fix occurrences of request finish method's old name
- block, bfq: remove batches of confusing ifdefs
- block, bfq: add requeue-request hook
* HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
- ALSA: hda: add mute led support for HP ProBook 455 G5
* [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
(LP: #1781476)
- i2c: xlp9xx: Fix issue seen when updating receive length
- i2c: xlp9xx: Make sure the transfer size is not more than
I2C_SMBUS_BLOCK_SIZE
* x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
- x86/kvm: fix LAPIC timer drift when guest uses periodic mode
* Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
- [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
* Nvidia fails after switching its mode (LP: #1778658)
- PCI: Restore config space on runtime resume despite being unbound
* Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
- SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
* CVE-2018-12232
- PATCH 1/1] socket: close race condition between sock_close() and
sockfs_setattr()
* CVE-2018-10323
- xfs: set format back to extents if xfs_bmap_extents_to_btree
* change front mic location for more lenovo m7/8/9xx machines (LP: #1781316)
- ALSA: hda/realtek - Fix the problem of two front mics on more machines
- ALSA: hda/realtek - two more lenovo models need fixup of MIC_LOCATION
* Cephfs + fscache: unable to handle kernel NULL pointer dereference at
IP: jbd2__journal_start+0x22/0x1f0 (LP: #1783246)
- ceph: track read contexts in ceph_file_info
* Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
(LP: #1779802)
- Input: elantech - fix V4 report decoding for module with middle key
- Input: elantech - enable middle button of touchpads on ThinkPad P52
* xhci_hcd :00:14.0: Root hub is not suspended (LP: #1779823)
- usb: xhci: dbc: Fix lockdep warning
- usb: xhci: dbc: Don't decrement runtime PM counter if DBC is not started
* CVE-2018-13406
- video: uvesafb: Fix integer overflow in allocation
* CVE-2018-10840
- ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
* CVE-2018-11412
- ext4: do not allow external inodes for inline data
* CVE-2018-10881
- ext4: clear i_data in ext4_inode_info when removing inline data
* CVE-2018-12233
- jfs: Fix inconsistency between memory allocation and ea_buf->max_size
* CVE-2018-12904
- kvm: nVMX: Enforce cpl=0 for VMX instructions
* Error parsing PCC subspaces from PCCT (LP: #1528684)
- mailbox: PCC: erroneous error message when parsing ACPI PCCT
* CVE-2018-13094
- xfs: don't call xfs_da_shrink_inode with NULL bp
* other users' coredumps can be read via setgid directory and killpriv bypass
(LP: #1779923) // CVE-2018-13405
- Fix up non-directory creation in SGID directories
* Invoking obsolete 'firmware_install' target breaks snap build (LP: #1782166)
-
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
v4.13 Final is GOOD v4.14-rc1 is also GOOD (a little screen flickering, but that is acceptable) v4.15, however, doesn't work. -- 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/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787155] Re: linux-azure: 4.15.0-1022.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Tuesday, 28. August 2018 07:01 UTC + kernel-stable-phase:Promoted to updates ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 - phase: Promoted to proposed + phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Tuesday, 28. August 2018 07:01 UTC - kernel-stable-phase:Promoted to updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1787155 Title: linux-azure: 4.15.0-1022.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788766] Re: linux: 4.4.0-135.161 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- 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/1788766 Title: linux: 4.4.0-135.161 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1788767 (linux-aws), bug 1788768 (linux-lts-xenial) derivatives: bug 1788769 (linux-aws), bug 1788770 (linux-euclid), bug 1788771 (linux-kvm), bug 1788772 (linux-raspi2), bug 1788773 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 27. August 2018 11:02 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789358] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1789358 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1789358 Title: Support Power Management for Thunderbolt Controller Status in linux package in Ubuntu: Incomplete Bug description: ===SRU Justification=== [Impact] New TBT controllers may use Native PCIe Enumeration (i.e. just like other normal PCIe device listed under lspci) instead of ACPI hotplug. Since TBT controller stops getting unplugged from PCIe bus, it draws additional power. [Fix] Support runtime power management for TBT controllers, so it can be put to D3 to save powers. [Test] I tested and verified this patch series can make Lenovo T480's TBT controller enters PCI D3 at runtime. [Regression Potential] Low. Almost all TBT controllers in the wild still uses ACPI hotplug, this series won't affect those users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787159] Re: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Tuesday, 28. August 2018 07:02 UTC + kernel-stable-phase:Promoted to updates ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 - phase: Promoted to proposed + phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Tuesday, 28. August 2018 07:02 UTC - kernel-stable-phase:Promoted to updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1787159 Title: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788766] Re: linux: 4.4.0-135.161 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1788766 Title: linux: 4.4.0-135.161 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1788767 (linux-aws), bug 1788768 (linux-lts-xenial) derivatives: bug 1788769 (linux-aws), bug 1788770 (linux-euclid), bug 1788771 (linux-kvm), bug 1788772 (linux-raspi2), bug 1788773 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Monday, 27. August 2018 11:02 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784998] Re: After a while touchpad doesn't work
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc1 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.19-rc1/ -- 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/1784998 Title: After a while touchpad doesn't work Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: By default, touchpad doesn't work, but USB mouse works. WORKAROUND: Install the NVIDIA proprietary drivers, and use non-default kernel parameters: nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 10:23:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-04-29 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=48228a8f-bbca-4be4-a07a-96a383809e68 ro quiet splash nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788765] Re: linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker
** Summary changed: - linux-lts-trusty: 3.13.0-158.208~precise1 -proposed tracker + linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1788765 Title: linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788764 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788769] Re: linux-aws: 4.4.0-1067.77 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788769 Title: linux-aws: 4.4.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789358] Re: Support Power Management for Thunderbolt Controller
** Tags added: originate-from-1781335 somerville -- 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/1789358 Title: Support Power Management for Thunderbolt Controller Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: ===SRU Justification=== [Impact] New TBT controllers may use Native PCIe Enumeration (i.e. just like other normal PCIe device listed under lspci) instead of ACPI hotplug. Since TBT controller stops getting unplugged from PCIe bus, it draws additional power. [Fix] Support runtime power management for TBT controllers, so it can be put to D3 to save powers. [Test] I tested and verified this patch series can make Lenovo T480's TBT controller enters PCI D3 at runtime. [Regression Potential] Low. Almost all TBT controllers in the wild still uses ACPI hotplug, this series won't affect those users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1789358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787155] Re: linux-azure: 4.15.0-1022.23 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Released + kernel-stable-phase-changed:Tuesday, 28. August 2018 07:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 - phase: Promoted to updates + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Released - kernel-stable-phase-changed:Tuesday, 28. August 2018 07:31 UTC ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1787155 Title: linux-azure: 4.15.0-1022.23 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788767] Re: linux-aws: 4.4.0-1029.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788767 Title: linux-aws: 4.4.0-1029.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787159] Re: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Released + kernel-stable-phase-changed:Tuesday, 28. August 2018 07:32 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 - phase: Promoted to updates + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Released - kernel-stable-phase-changed:Tuesday, 28. August 2018 07:32 UTC ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1787159 Title: linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc1 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.19-rc1/ -- 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/1781049 Title: WiFI hard blocked after resuming laptop (RTL 8723BE) Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythreya 1281 F pulseaudio /dev/snd/controlC1: mythreya 1281 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-26 (16 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion Notebook NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.87 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-30T14:39:45.608645 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2018-06-28T16:23:51.596655 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR71 1a9d81bf-e7f5-4f8a-956f-96180dc493e1 wifi 1531450229 Thu 12 Jul 2018 09:50:29 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlo1activated /org/f
[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display
This should be fixed by next stable kernel update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788308 Title: [Regression] Colour banding appears on Lenovo B50-80 integrated display Status in linux package in Ubuntu: Confirmed Bug description: The problem affects the integrated display on a Lenovo B50-80 notebook. Colour banding is visible everywhere on the system, as dithering seems not to be enabled on this 6bpp display. This issue was not present on non-HWE Ubuntu 16.04, and it showed up after I upgraded to Ubuntu 18.04. There was already a very similar bug #1749420 that had a fix released, however, because the make and model of an LCD screen in that case was different, the quirk added to the kernel did not address the problem that affects my machine. The cause of this issue is probably the same, since I have checked that pre-4.8.0-rc2 kernels handled dithering correctly, and 4.8.0-rc2 and later kernels already had the bug described. I believe that adding quirk for an another type of display may fix the problem. I attached the results of running sudo get-edid | parse-edid in a file named edid.txt and sudo get-edid | edid-decode in a file named edid-decoded.txt. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1245 F pulseaudio /dev/snd/controlC1: me 1245 F pulseaudio Date: Wed Aug 22 00:26:15 2018 HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e InstallationDate: Installed on 2018-08-21 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80EW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN54WW(V3.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo B50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B50-80 dmi.modalias: dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80: dmi.product.family: IDEAPAD dmi.product.name: 80EW dmi.product.version: Lenovo B50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf
Found the relevant commit that needs to get ported. https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/zesty/commit/?id=4f86b396b67c633d6f17fb8911ac51f6d93129a5 -- 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/1396654 Title: C++ demangling support missing from perf Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-meta-hwe source package in Xenial: Confirmed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Bug description: Hi, It appears that C++ demangling support is missing from linux-tools-3.16.0-24, on Utopic on arm64. Could the following please be added to the build dependencies for that package: libiberty-dev binutils-dev Installing the above and rebuilding the package fixed the problem for me. Cheers, -- Steve --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-24-generic aarch64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788767] Re: linux-aws: 4.4.0-1029.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788767 Title: linux-aws: 4.4.0-1029.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788765] Re: linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788764 phase: Packaging + kernel-stable-phase-changed:Tuesday, 28. August 2018 08:02 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788764 - phase: Packaging - kernel-stable-phase-changed:Tuesday, 28. August 2018 08:02 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1788765 Title: linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788764 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788771 Title: linux-kvm: 4.4.0-1033.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785780] Re: TB 16 issue on Dell Lattitude 7490 with large amount of data
** Description changed: + ===SRU Justification=== + [Impact] + Packets are silently corrupted on Dell TB16's ethernet. + + [Fix] + Disable RX aggregation on new Dell TB16 dock. + + [Test] + User confirms the patch fixes the issue. + + [Regression Potential] + Low. The workaround already works, we just add a new USB serial to let + new TB16 dock also uses this workaround. + + ===Original Bug Report=== Hi. Large amount of data gets corrupted when using the TB16 ethernet port. (rsync synchronization, etc... ) We can confirm this issue on this kernel. Creating new issue as stated in this bug (#1729674) Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On my Fedora is this still an issue even with announced bugfix (link copied from this discussion #78. Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It's fixed by turning the checksum offload off (tested on the Fedora . sudo ethtool --offload enp11s0u1u2 rx off https://bugs.launchpad.net/dell-sputnik/+bug/1729674 related in bugzilla: - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1955 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1955 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: - linux-restricted-modules-4.15.0-29-generic N/A - linux-backports-modules-4.15.0-29-generic N/A - linux-firmware 1.173.1 + linux-restricted-modules-4.15.0-29-generic N/A + linux-backports-modules-4.15.0-29-generic N/A + linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd06/07/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. -- 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/1785780 Title: TB 16 issue on Dell Lattitude 7490 with large amount of data Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: ===SRU Justification=== [Impact] Packets are silently corrupted on Dell TB16's ethernet. [Fix] Disable RX aggregation on new Dell TB16 dock. [Test] User confirms the patch fixes the issue. [Regression Potential] Low. The workaround already works, we just add a new USB serial to let new TB16 dock also uses this workaround. ===Original Bug Report=== Hi. Large amount of data gets corrupted when using the TB16 ethernet port. (rsync synchronization, etc... ) We can confirm this issue on this kernel. Creating new issue as stated in this bug (#1729674) Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On my Fedora is this still an issue even with announced bugfix (link copied from this discussion #78. Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It's fixed by turning the checksum offload off (tested on the Fedora . sudo ethtool --offload enp11s0u1u2 rx off https://bugs.launchpad.net/dell-sputnik/+bug/1729674 related in bugzilla: --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1955 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnvir
[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788771 Title: linux-kvm: 4.4.0-1033.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766823] Re: zram module not found in 4.4/4.15 KVM kernel
** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1766823 Title: zram module not found in 4.4/4.15 KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-kvm source package in Xenial: Fix Committed Status in linux-kvm source package in Bionic: Fix Committed Bug description: == Justification == In the Xenial / Bionic KVM kernel, the CONFIG_ZRAM was not set, it's impossible for users to use zram module on it. And the ubuntu_zram_smoke_test regression test is failing due to the missing module. == Test == Before enabling CONFIG_ZRAM and the related configs, the zram module cannot be found. After that, the zram module can be inserted and pass the ubuntu_zram_smoke_test. Test kernels could be found here: http://people.canonical.com/~phlin/kernel/lp-1766823-zram/ == Fix == [bionic/linux-kvm][xenial/linux-kvm][SRU][PATCH] UBUNTU: [Config]: enable CONFIG_ZRAM == Regression Potential == Minimal. No code changes, just a config changes without disabling any other configs. -- The ubuntu_zram_smoke_test will fail due to the lack of the zram module. 07:32:19 DEBUG| Running '/home/ubuntu/autotest/client/tests/ubuntu_zram_smoke_test/ubuntu_zram_smoke_test.sh' 07:32:19 ERROR| [stderr] modprobe: FATAL: Module zram not found in directory /lib/modules/4.15.0-1008-kvm 07:32:19 DEBUG| [stdout] FAILED: cannot load zram module 07:32:19 ERROR| Exception escaping from test: There is no zram config in the Bionic KVM kernel config file. $ grep -i zram debian.kvm/config/config.common.ubuntu $ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 07:32:47 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hello Lucas, thank you for response. Yes, badly setted kernel parameters can cause very serious problems. Additionally, I can comfirm, that problem is not bounded only on Samsung NVME SSD, but It occurs on Intel SSD-6 series as well. It looks like, that problem is in ASPM SSD Driver - kernel parameters. There are a few errors, which came in one time. The easiest way, how to simulate initframfs error during startup/restart is to install Thunderbird and download thousands emails from cloud e.q. google mail to generate traffic on SSD. Than install and startup Firefox, add plugins for video (Player) and stertup video. Firefox for Linux (last version was something about 57-61) is unstable on Linux (generally, not only Ubuntu), than Firefox begin crash, and issues - "Would you like to restart and recover Firefox?". It streses the SSD and after a few restores (about 10) probably begin crash Thunderbird. It is the time for restart system. Probably - there will be issue, that it is not possible to start Ubuntu and initframfs error occured. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long
[Kernel-packages] [Bug 1776416] Re: Sound stopped working after update 11/06/18 7pm GMT
> Sound working again thanks to an engineer Could you explain how was this fixed? Ain't the drivers supposed to update automatically with the system update? I went off on holiday and hoped the bug got fixed in the meantime but apparently not. :( -- 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/1776416 Title: Sound stopped working after update 11/06/18 7pm GMT Status in Linux: New Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Sound was working fine until the update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2094 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 12 08:30:09 2018 InstallationDate: Installed on 2017-05-26 (381 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2094 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.05 02/23/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67HSHP dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.0502/23/2017:bd02/23/2017:svnPCSpecialistLimited:pnP65_67HSHP:pvrNotApplicable:rvnCLEVO:rnP65_67HSHP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65_67HSHP dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1776416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788769] Re: linux-aws: 4.4.0-1067.77 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded + kernel-stable-phase-changed:Tuesday, 28. August 2018 10:06 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 - phase: Uploaded - kernel-stable-phase-changed:Tuesday, 28. August 2018 10:06 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788769 Title: linux-aws: 4.4.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788767] Re: linux-aws: 4.4.0-1029.32 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded + kernel-stable-phase-changed:Tuesday, 28. August 2018 10:05 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 - phase: Uploaded - kernel-stable-phase-changed:Tuesday, 28. August 2018 10:05 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788767 Title: linux-aws: 4.4.0-1029.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786902] Re: [18.10 FEAT] SMC-Direct
** 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/1786902 Title: [18.10 FEAT] SMC-Direct Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Provide support for next generation HiperSockets. SMC-local (Shared Memory Communications -- local) provides a new architecture for high performance networking within a CEC. Buffers in the HSA can be shared between LPARs and will be used for communication. A new socket family will be used to eliminate TCP overhead. Integration with existing tooling through TCP handshaking. A preload library can be used to enable applications to use the new socket family transparently Backport from kernel 4.19 will be attached. For SMC enabling following kernel config has to be set CONFIG_HAVE_PNETID. With this setting an additoiponal modul need to be build : pnet.ko @canonical kernel team: please cherrypick: Here you go - sorry for the delay! In sequence, from oldest to latest: ddb457c6993babbcdd41fca638b870d2a2fc3941 be6a3f38ff2a2bfd2e591fdc566940a0d4d9428c 0afff91c6f5ecef27715ea71e34dc2baacba1060 c6ba7c9ba43de1b57e9a53946e7ff988554c84ed 1619f770589a183af56f248de261534b255122de c758dfddc1b5b1c9b8c64e5e4bb9bf24b74f4a59 be244f28d22f77d939ba2b973c102ad2b49d3496 413498440e30bfe381ac99dfc31628a3d8d4382a 4b1b7d3b30a6d32ac1a1dcede284e76ef8a8542d c601171d7a60b5b09d7c2fe0579953323a80744e bac6de7b637018f4caacfdf2b4ad8c8749de7420 00e5fb263f9f5f2af60754b79b7dcec0d5e88154 144ce4b9b5a788953b5373162a1921267497fb38 48bf5231771c7e3961c8326353b6027b1bed6eb5 12c36dcfd6f48ece2fce4dc8e6ce68224d005d37 2e3bbe46b4a18d16314dab0c0efdba0c079a5ed0 947541f36c561b5e0ca639ffc450a8c5221de467 7005ada68d1774d7c1109deaba0c2cd8e46f5091 603cc1498455cf57f5ca4483b600efb37ea2c56c 0d18a0cb4b1585d9e5a3b300d5df9ed866561ffb dd979b4df817e9976f18fb6f9d134d6bc4a3c317 0d86caff06363151df21603eb1f4e3207ea91bd2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1786902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763774] Re: nvidia-driver-390 GDM black screen / hang after login
Have you tried running GDM with X instead of Wayland ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1763774
Title:
nvidia-driver-390 GDM black screen / hang after login
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Confirmed
Bug description:
Ubuntu 18.04 x64 / gdm
AMD 1800x
Aorus Gaming K7 (x370 chipset) motherboard
NVidia GTX 1080Ti w/ DisplayPort attached 4k monitor
USB keyboard / mouse
I've recently upgraded from Ubuntu 17.10 x64 to 18.04 x64 via
`do-release-upgrade -d` and uninstalled / purged / reinstalled my NVidia
native drivers using the `ubuntu-drivers autoinstall` approach.
I am able to boot the system and it displays the X login shell at native
resolution with a functioning keyboard and mouse, but I cannot
ctrl+alt+F{1,2,3,4,...} to a non-graphical terminal.
When I click "Sign in" using gnome 3, gnome classic, or Unity, I get a
black screen and my input devices hang (keyboard caps lock key no longer
functions.) If I unplug and replug my input devices, they remain
hanging, with a stuck-on capslock indicator. The mouse is also
illuminated.
I am able to SSH into the machine, and it is still usable. systemctl
status gdm.service indicates that gdm is "running" and does not show an
error, but it shows that the login session opened and closed very quickly.
I rebooted and SSH'd into the machine before the hang, halted GDM via
`systemctl stop gdm.service` and was able to ctrl+alt+F1 into another
shell on the attached keyboard. I then executed `systemctl restart
gdm.service` and got the expected X login shell. I was then able to log
into the desktop environment normally.
My Xorg.0.log is here for the successful login:
https://paste.ubuntu.com/p/SNqJPxV938/
I'll reproduce the behavior and attach an xorg log for the unexpected
behavior.
Bodie
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-driver-390 390.48-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Fri Apr 13 12:43:48 2018
InstallationDate: Installed on 2017-10-30 (165 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: nvidia-graphics-drivers-390
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1763774/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1776416] Re: Sound stopped working after update 11/06/18 7pm GMT
Well, if the drivers were being updated automatically with a system update they weren't for me. The engineer didn't explain exactly what he did, sorry. The repair wasn't expensive, so maybe you should get an engineer to look at? On 28/08/18 10:43, Augustin Riedinger wrote: >> Sound working again thanks to an engineer > Could you explain how was this fixed? Ain't the drivers supposed to > update automatically with the system update? > > I went off on holiday and hoped the bug got fixed in the meantime but > apparently not. :( > -- 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/1776416 Title: Sound stopped working after update 11/06/18 7pm GMT Status in Linux: New Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Sound was working fine until the update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2094 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 12 08:30:09 2018 InstallationDate: Installed on 2017-05-26 (381 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2094 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.05 02/23/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67HSHP dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.0502/23/2017:bd02/23/2017:svnPCSpecialistLimited:pnP65_67HSHP:pvrNotApplicable:rvnCLEVO:rnP65_67HSHP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65_67HSHP dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1776416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788769] Re: linux-aws: 4.4.0-1067.77 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788769 Title: linux-aws: 4.4.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Uploaded + kernel-stable-phase-changed:Tuesday, 28. August 2018 10:37 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 - phase: Uploaded - kernel-stable-phase-changed:Tuesday, 28. August 2018 10:37 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788771 Title: linux-kvm: 4.4.0-1033.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780103] Re: Network namespaces support for non-IP suddenly missing
That was too soon: correction: 18.04 does not yet fix this bug. -- 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/1780103 Title: Network namespaces support for non-IP suddenly missing Status in linux package in Ubuntu: Incomplete Bug description: I run 16.04, and I keep daily track of all dist-upgrades. Yesterday (3 july 2018) there was an upgrade, and it must have been a kernel upgrade, because my machine had rebooted (which I make it do automatically if needed). From today, the system tests on my project have stopped working (C development). These system tests do the following: using the 'ip' command, they set up several network namespaces, in which I run several executables concurrently, that exchange network messages with each other. The namespaces that use IP have kept on working, while the ones that don't (I'm implementing an ethernet network packet structure of my own) have stopped working. I've done the same tests on my laptop, which is also a 16.04, on which I haven't done the upgrade (and I'm very hesitant to do so now, because this is my bread and butter), and there they work still. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kees 1919 F pulseaudio /dev/snd/seq:timidity 1084 F timidity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3ed19ff5-7945-42ac-a22a-9136402798d8 InstallationDate: Installed on 2018-02-06 (148 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=43c7f0dc-00d1-4bb5-86c0-9ac982fbe227 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.19 RfKill: Tags: xenial Uname: Linux 4.4.0-128-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H110M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/16/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kees 1920 F pulseaudio /dev/snd/seq:timidity 1065 F timidity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3ed19ff5-7945-42ac-a22a-9136402798d8 InstallationDate: Installed on 2018-02-06 (148 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=43c7f0dc-00d1-4bb5-86c0-9ac982fbe227 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackag
[Kernel-packages] [Bug 1788750] Re: linux-aws: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 28. August 2018 11:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 28. August 2018 11:31 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788750 Title: linux-aws: 4.15.0-1021.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
I think this is a race in ccw_io_helper(). The stress-ng sysfs stressor is running multiple threaded reads of /sys/devices/css0/0.0./0.0./virtio0/block/vda/cache_type which results in reads via virtio_cread8() and ultimately reads using virtio_ccw_get_config() I added debug into virtio_cread8 and it returns 1 99% of the time, and sometimes in a threaded read we get it returning garbage, such as 200 in the following trace: [ 39.76] virtio_cread8 32 -> 1 [ 39.767933] virtio_cread8 32 -> 1 [ 39.787712] virtio_cread8 32 -> 200 [ 39.787810] kernel BUG at drivers/block/virtio_blk.c:576! -- 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/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear vir
[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788771 Title: linux-kvm: 4.4.0-1033.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788744] Re: linux: 4.15.0-34.37 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 (linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 1788761 (linux-hwe-edge) derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 (linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 (linux-kvm) kernel-stable-phase-changed:Monday, 27. August 2018 15:30 UTC kernel-stable-phase:Uploaded -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1788744 Title: linux: 4.15.0-34.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 (linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 1788761 (linux-hwe-edge) derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 (linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 (linux-kvm) kernel-stable-phase-changed:Monday, 27. August 2018 15:30 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Same story here with HP 17-y009ng, 16.04 worked like a charm, with ant_sel=2 ( after having had a hard time to find out that this option was a must). Kernel 4.15.0.32 worked as well after upgrade to 18.04-1. No more wifi signal after update to kernel 4.1.5.0-33. Tried all other module options but had no success. Currently booting with kernel 4.15.0-32 -- 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788753] Re: linux-kvm: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 28. August 2018 12:03 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1788744 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 28. August 2018 12:03 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788753 Title: linux-kvm: 4.15.0-1021.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788750] Re: linux-aws: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788750 Title: linux-aws: 4.15.0-1021.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9
32-bit kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18 /linux-image-4.15.18-041518-generic_4.15.18-041518.201804190330_i386.deb does not boot, in fact it crashes immediately without producing any console output at all (so doesn't get as far as the currently-packaged linux-image-generic). The 64-bit package http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.15.18/linux- image-4.15.18-041518-generic_4.15.18-041518.201804190330_amd64.deb boots and seems to behave as expected. Would it help if I went back through package versions of linux-image- generic until I find one that does boot? I know for certain that one of them does because this was encountered only after an update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789118 Title: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: After the most recent 18.04 32-bit upgrade of linux-image-generic, it now refuses to boot under Xen PV mode: . . . [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes) [0.114423] pinctrl core: initialized pinctrl subsystem [0.134326] RTC time: 165:165:165, date: 165/165/65 [0.134442] NET: Registered protocol family 16 [0.134457] xen:grant_table: Grant tables using version 1 layout [0.134502] Grant table initialized [0.134544] audit: initializing netlink subsys (disabled) [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized audit_enabled=0 res=1 [0.134678] EISA bus registered [0.136019] PCI: setting up Xen PCI frontend stub [0.136073] BUG: unable to handle kernel paging request at edc21fd9 [0.136084] IP: eisa_bus_probe+0x19/0x36 [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = [0.136100] Oops: [#1] SMP [0.136105] Modules linked in: [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic #36-Ubuntu [0.136120] EIP: eisa_bus_probe+0x19/0x36 [0.136125] EFLAGS: 00010246 CPU: 0 [0.136130] EAX: edc21fd9 EBX: ECX: 01e0d000 EDX: 0200 [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24 [0.136145] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021 [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660 [0.136166] Call Trace: [0.136173] do_one_initcall+0x49/0x174 [0.136179] ? parse_args+0x143/0x390 [0.136187] ? set_debug_rodata+0x14/0x14 [0.136193] kernel_init_freeable+0x149/0x1c5 [0.136201] ? rest_init+0xa0/0xa0 [0.136207] kernel_init+0xd/0xf0 [0.136213] ret_from_fork+0x2e/0x38 [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8 [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24 [0.14] CR2: edc21fd9 [0.14] ---[ end trace 8c00b3cb7d4f06ba ]--- [0.140013] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 This is: [0.00] Linux version 4.15.0-33-generic (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu 4.15.0-33.36-generic 4.15.18) Switching to a 64-bit kernel allows boot to proceed. I cannot include output of the commands you request (uname, version_signature, dmesg, lspci) because the guest doesn't boot. The above kernel output is from a just-installed clean guest however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
** Description changed: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic + + Steps to reproduce this bug: + + git clone git://kernel.ubuntu.com/cking/stress-ng + cd stress-ng + make clean + make + + And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! - [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP + [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) - [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 - [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 - [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 - [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 - [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 - [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 + [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 + [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 + [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 + [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 + [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 + [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] - [ 119.446283] + [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- - For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! - [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP + [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net virtio_blk crc32_vx_s390 [ 25.170835] CPU: 0 PID: 5590 Comm: stress-ng-sysfs Tainted: P OE 4.17.0-8-generic #9-Ubuntu [ 25.170837] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 25.170839] Krnl PSW : 05f0c968 26542d57 (virtblk_cache_type_show+0x7c/0x80 [virtio_blk])
[Kernel-packages] [Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) ** Tags added: reverse-proxy-bugzilla s390x -- 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/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net virtio_blk crc32_vx_s390 [ 25.170835] CPU: 0 PID: 5590 Comm: stress-ng-sysfs Tainted: P OE 4.17.0-8-generic #9-Ubuntu [ 25.170837] Hardware
[Kernel-packages] [Bug 1782880] Re: KDE applications can not select anymore fstab or cifs mounted NTFS partions
Unfortunately after system update the bug appeared again! Kubuntu applications hide mounted NTFS folders so that the the data can not be accessed by Kubuntu applications. GTK Applications do work as expected. Test fstab: # # # / was on /dev/sda8 during installation UUID=ac1d18ac-8ad5-4565-997e-59c90bd00e71 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/sda2 during installation UUID=C4DD-77E3 /boot/efi vfatumask=0077 0 1 # /home was on /dev/sda7 during installation UUID=21b47237-4d1b-4eac-8f72-a96e8d323c91 /home ext4defaults 0 2 # --> mount instructions ignored and modified, see below mount -l UUID=BA702B4E702B10A5 /home/a1/DatenAllg ntfsdefaults,umask=007,gid=46 0 0 # --> mount instructions ignored and modified, see below mount -l UUID=802A9A512A9A43D6 /home/a1/SSD-SYS ntfsdefaults,umask=007,gid=46 0 0 # --> mount instructions ignored and modified, see below mount -l #UUID=272007F45F29DEA2 /ntfs/Video ntfsrw,auto,gid=1000,uid=1000,nls=utf8 0 0 # swap was on /dev/sda6 during installation UUID=8ad70c4f-10d1-4ce5-ab5b-828bfd4a2f56 noneswapsw 0 0 # mount instructions correct taken UUID=b8c34934-ab20-479a-9861-18fdd1211bf6 /home/a1/Video ext4 defaults0 2 Lines starting with # - - > are mounted but can not seen and not accessed by kubuntu applications. The last fstab line, ext4, does a correct mounting. It looks like that ntfs mount instructions are ignored and replaced by somewhat else. ~$ mount -l sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=16408676k,nr_inodes=4102169,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3295220k,mode=755) /dev/sda8 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,no
[Kernel-packages] [Bug 1788750] Re: linux-aws: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788750 Title: linux-aws: 4.15.0-1021.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775672] Re: virtualbox-dkms installation hangs in 18.04 (with secure boot)
I've struggled through this several times now. I don't have a definitive solution but the general routine was something like this. When you asked to enroll the machine owner key to sign the kernel module there is an interface that popups up and waits for user input. I tried this in in a shell-only session and in a gnome session several times. In both cases the process that spawns the window gets stuck in a child process and I think it was sent to a different tty altogether. One time I accidentally recover the interface by killing all the login window session processes while I was in a trying something else in a shell session. When i jumped back everything redrew and there was a new window that asked me to enroll the MOK key password. I was not able to reproduce that the next time I got stuck in this spot, but what worked for me was disabling my machines nvidia video card proprietary drivers, and then switching from wayland to gnome (or gnome to wayland) after I did that then the processes worked as it was supposed to. This issue is very frustrating, but you should be able to keep secure boot enabled. I saved the logs from those times I was able to get it to work. I'll see if I can find anything to back up what I'm saying here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1775672 Title: virtualbox-dkms installation hangs in 18.04 (with secure boot) Status in DKMS: New Status in dkms package in Ubuntu: Confirmed Bug description: apt install virtualbox hangs during virtualbox-dkms installation: # apt install virtualbox Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1 virtualbox-dkms virtualbox-qt Suggested packages: menu vde2 virtualbox-guest-additions-iso The following NEW packages will be installed: dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1 virtualbox virtualbox-dkms virtualbox-qt 0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/27.0 MB of archives. After this operation, 117 MB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package dkms. (Reading database ... 185903 files and directories currently installed.) Preparing to unpack .../0-dkms_2.3-3ubuntu9.1_all.deb ... Unpacking dkms (2.3-3ubuntu9.1) ... Selecting previously unselected package libgsoap-2.8.60:amd64. Preparing to unpack .../1-libgsoap-2.8.60_2.8.60-2build1_amd64.deb ... Unpacking libgsoap-2.8.60:amd64 (2.8.60-2build1) ... Selecting previously unselected package libqt5opengl5:amd64. Preparing to unpack .../2-libqt5opengl5_5.9.5+dfsg-0ubuntu1_amd64.deb ... Unpacking libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ... Selecting previously unselected package libqt5printsupport5:amd64. Preparing to unpack .../3-libqt5printsupport5_5.9.5+dfsg-0ubuntu1_amd64.deb ... Unpacking libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ... Selecting previously unselected package libvncserver1:amd64. Preparing to unpack .../4-libvncserver1_0.9.11+dfsg-1ubuntu1_amd64.deb ... Unpacking libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ... Selecting previously unselected package virtualbox-dkms. Preparing to unpack .../5-virtualbox-dkms_5.2.10-dfsg-6_all.deb ... Unpacking virtualbox-dkms (5.2.10-dfsg-6) ... Selecting previously unselected package virtualbox. Preparing to unpack .../6-virtualbox_5.2.10-dfsg-6_amd64.deb ... Unpacking virtualbox (5.2.10-dfsg-6) ... Selecting previously unselected package virtualbox-qt. Preparing to unpack .../7-virtualbox-qt_5.2.10-dfsg-6_amd64.deb ... Unpacking virtualbox-qt (5.2.10-dfsg-6) ... Setting up libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Setting up libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ... Setting up libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ... Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Setting up libgsoap-2.8.60:amd64 (2.8.60-2build1) ... Setting up dkms (2.3-3ubuntu9.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for man-db (2.8.3-2) ... Processing triggers for shared-mime-info (1.9-2) ... Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Setting up virtualbox-dkms (5.2.10-dfsg-6) ... Loading new virtualbox-5.2.10 DKMS files... Building for 4.15.0-22-generic Progress: [ 85%] [##
[Kernel-packages] [Bug 1788765] Re: linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-precise ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1788764 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1788765 Title: linux-lts-trusty: 3.13.0-158.208~precise2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788764 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788744] Re: linux: 4.15.0-34.37 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- 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/1788744 Title: linux: 4.15.0-34.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 (linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 1788761 (linux-hwe-edge) derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 (linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 (linux-kvm) kernel-stable-phase-changed:Monday, 27. August 2018 15:30 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
4.15.0-33-generic description: Ordinateur portable produit: VORKE V2 (System SKUNumber) fabriquant: Intel Corporation version: 0.1 numéro de série: System Serial Number bits: 64 bits fonctionnalités: smbios-3.0 dmi-3.0 smp vsyscall32 configuration: boot=normal chassis=laptop family=Kabylake System sku=System SKUNumber uuid=00020003-0004-0005-0006-000700080009 *-core description: Carte mère produit: V2 Plus fabriquant: Intel Corp. identifiant matériel: 0 version: RVP7 numéro de série: 1 emplacement: Part Component *-firmware description: BIOS fabriquant: American Megatrends Inc. identifiant matériel: 0 version: 5.12 date: 12/08/2017 taille: 64KiB capacité: 15MiB fonctionnalités: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-network description: Ethernet interface produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller fabriquant: Realtek Semiconductor Co., Ltd. identifiant matériel: 0 information bus: pci@:03:00.0 nom logique: enp3s0 version: 07 numéro de série: 00:e0:4c:d6:1d:e0 taille: 1Gbit/s capacité: 1Gbit/s bits: 64 bits horloge: 33MHz fonctionnalités: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 ip=192.168.3.101 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s ressources: irq:17 portE/S:e000(taille=256) mémoire:df00-df000fff mémoire:d000-d0003fff And I am affected by this bug. modprobe does not work here. -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Same problem for me. Upgrade to 18.04.1 from 16.04.x. Dell Precision M3800 Nvidia drivers 340 and 390 (both tested). But I'm always on the Intel Graphics. Temp regularly above 70°C. Never had this problem before. -- 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/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LT
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
$ uname -r 4.15.0-33-generic $ sudo lshw -C network *-network Beschreibung: Ethernet interface Produkt: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Hersteller: Realtek Semiconductor Co., Ltd. Physische ID: 0 Bus-Informationen: pci@:02:00.0 Logischer Name: enp2s0 Version: 03 Seriennummer: e0:cb:4e:eb:9e:54 Größe: 1Gbit/s Kapazität: 1Gbit/s Breite: 64 bits Takt: 33MHz Fähigkeiten: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation Konfiguration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8168d-2.fw ip=192.168.2.50 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s Ressourcen: irq:18 ioport:e800(Größe=256) memory:fafff000-faff memory:faff8000-faffbfff memory:fbef-fbef LAN disappears when wake up from hibernation. Script in /lib/systemd/system-sleep/ with #!/bin/bash PROGNAME=$(basename "$0") state=$1 action=$2 if [[ $state == post ]]; then modprobe -r r8169 \ && modprobe -i r8169 \ fi seems to be a workaround (tested twice). greetings andreas -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: l
[Kernel-packages] [Bug 1788748] Re: linux-oem: 4.15.0-1018.21 -proposed tracker
** Summary changed: - linux-oem: -proposed tracker + linux-oem: 4.15.0-1018.21 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1788748 Title: linux-oem: 4.15.0-1018.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
[edit #102] just tested again: set to hibernation -> wake up again -> LAN is gone... So, modprobe... doesn't work! -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.fami
[Kernel-packages] [Bug 1789431] [NEW] ip rule show has unexpected space in destination prefix
Public bug reported: Introduced by upstream iproute2 v4.17.0: 0dd4ccc5 "iprule: add json support" This commit changes the output of "ip rule show" to support json output but also accidentally inserts a space character between ipv4 address and "/". This breaks for example the route_with_policy test of netplan.io. Testcase: ip rule add from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 ip rule show Expected: *: from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 Actual output: *: from 0.1.0.0/24 to 10.2.0.0 /24 lookup 99 ** Affects: iproute2 (Ubuntu) Importance: High Assignee: Stefan Bader (smb) Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1789431 Title: ip rule show has unexpected space in destination prefix Status in iproute2 package in Ubuntu: Triaged Bug description: Introduced by upstream iproute2 v4.17.0: 0dd4ccc5 "iprule: add json support" This commit changes the output of "ip rule show" to support json output but also accidentally inserts a space character between ipv4 address and "/". This breaks for example the route_with_policy test of netplan.io. Testcase: ip rule add from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 ip rule show Expected: *: from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 Actual output: *: from 0.1.0.0/24 to 10.2.0.0 /24 lookup 99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1789431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789435] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1789435
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1789435
Title:
kernel 3.13.0-157+158: ext4: wrong error message »invalid block
bitmap«
Status in linux package in Ubuntu:
Incomplete
Bug description:
W're getting the »invalid block bitmap« error since kernel 3.13.0-157
see
https://github.com/torvalds/linux/commit/22be37acce25d66ecf6403fc8f44df9c5ded2372
and in this diff the error is within
»if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||«
Kind regards, J. Barth
*** linux_3.13.0-155.205.diff 2018-08-28 14:56:04.357521118 +0200
--- linux_3.13.0-157.207.diff 2018-08-28 14:48:27.168863046 +0200
***
*** 31,37
}
/* Return the number of free blocks in a block group. It is used when
! @@ -419,11 +420,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
--- 31,102
}
/* Return the number of free blocks in a block group. It is used when
! @@ -307,6 +308,7 @@
! ext4_group_t block_group,
! struct buffer_head *bh)
! {
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! ext4_grpblk_t offset;
! ext4_grpblk_t next_zero_bit;
! ext4_fsblk_t blk;
! @@ -326,24 +328,30 @@
! /* check whether block bitmap block number is set */
! blk = ext4_block_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode bitmap block number is set */
! blk = ext4_inode_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode table block number is set */
! blk = ext4_inode_table(sb, desc);
! offset = blk - group_first_block;
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + EXT4_B2C(sbi, offset + sbi->s_itb_per_group) >= sb->s_blocksize)
! + return blk;
! next_zero_bit = ext4_find_next_zero_bit(bh->b_data,
! - offset + EXT4_SB(sb)->s_itb_per_group,
! - offset);
! - if (next_zero_bit < offset + EXT4_SB(sb)->s_itb_per_group)
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group),
! + EXT4_B2C(sbi, offset));
! + if (next_zero_bit <
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group))
! /* bad bitmap for inode tables */
! return blk;
! return 0;
! @@ -394,6 +402,7 @@
! ext4_read_block_bitmap_nowait(struct super_block *sb, ext4_group_t
block_group)
! {
! struct ext4_group_desc *desc;
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! struct buffer_head *bh;
! ext4_fsblk_t bitmap_blk;
!
! @@ -401,6 +410,12 @@
! if (!desc)
! return NULL;
! bitmap_blk = ext4_block_bitmap(sb, desc);
! + if ((bitmap_blk <= le32_to_cpu(sbi->s_es->s_first_data_block)) ||
! + (bitmap_blk >= ext4_blocks_count(sbi->s_es))) {
! + ext4_error(sb, "Invalid block bitmap block %llu in "
! + "block_group %u", bitmap_blk, block_group);
! + return ERR_PTR(-EIO);
! + }
! bh = sb_getblk(sb, bitmap_blk);
! if (unlikely(!bh)) {
! ext4_error(sb, "Cannot get buffer for block bitmap - "
! @@ -419,11 +434,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789435/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : htt
[Kernel-packages] [Bug 1789435] [NEW] kernel 3.13.0-157+158: ext4: wrong error message »invalid block bitmap«
Public bug reported:
W're getting the »invalid block bitmap« error since kernel 3.13.0-157
see
https://github.com/torvalds/linux/commit/22be37acce25d66ecf6403fc8f44df9c5ded2372
and in this diff the error is within
»if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||«
Kind regards, J. Barth
*** linux_3.13.0-155.205.diff 2018-08-28 14:56:04.357521118 +0200
--- linux_3.13.0-157.207.diff 2018-08-28 14:48:27.168863046 +0200
***
*** 31,37
}
/* Return the number of free blocks in a block group. It is used when
! @@ -419,11 +420,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
--- 31,102
}
/* Return the number of free blocks in a block group. It is used when
! @@ -307,6 +308,7 @@
! ext4_group_t block_group,
! struct buffer_head *bh)
! {
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! ext4_grpblk_t offset;
! ext4_grpblk_t next_zero_bit;
! ext4_fsblk_t blk;
! @@ -326,24 +328,30 @@
! /* check whether block bitmap block number is set */
! blk = ext4_block_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode bitmap block number is set */
! blk = ext4_inode_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode table block number is set */
! blk = ext4_inode_table(sb, desc);
! offset = blk - group_first_block;
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + EXT4_B2C(sbi, offset + sbi->s_itb_per_group) >= sb->s_blocksize)
! + return blk;
! next_zero_bit = ext4_find_next_zero_bit(bh->b_data,
! - offset + EXT4_SB(sb)->s_itb_per_group,
! - offset);
! - if (next_zero_bit < offset + EXT4_SB(sb)->s_itb_per_group)
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group),
! + EXT4_B2C(sbi, offset));
! + if (next_zero_bit <
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group))
! /* bad bitmap for inode tables */
! return blk;
! return 0;
! @@ -394,6 +402,7 @@
! ext4_read_block_bitmap_nowait(struct super_block *sb, ext4_group_t
block_group)
! {
! struct ext4_group_desc *desc;
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! struct buffer_head *bh;
! ext4_fsblk_t bitmap_blk;
!
! @@ -401,6 +410,12 @@
! if (!desc)
! return NULL;
! bitmap_blk = ext4_block_bitmap(sb, desc);
! + if ((bitmap_blk <= le32_to_cpu(sbi->s_es->s_first_data_block)) ||
! + (bitmap_blk >= ext4_blocks_count(sbi->s_es))) {
! + ext4_error(sb, "Invalid block bitmap block %llu in "
! +"block_group %u", bitmap_blk, block_group);
! + return ERR_PTR(-EIO);
! + }
! bh = sb_getblk(sb, bitmap_blk);
! if (unlikely(!bh)) {
! ext4_error(sb, "Cannot get buffer for block bitmap - "
! @@ -419,11 +434,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
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/1789435
Title:
kernel 3.13.0-157+158: ext4: wrong error message »invalid block
bitmap«
Status in linux package in Ubuntu:
Incomplete
Bug description:
W're getting the »invalid block bitmap« error since kernel 3.13.0-157
see
https://github.com/torvalds/linux/commit/22be37acce25d66ecf6403fc8f44df9c5ded2372
and in this diff the error is within
»if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||«
Kind regards, J. Barth
*** linux_3.13.0-155.205.diff 2018-08-28 14:56:04.357521118 +0200
--- linux_3.13.0-157.207.diff 2018-08-28 14:48:27.168863046 +0200
***
*** 31,37
}
/* Return the number of free blocks in a block group. It is used when
! @@ -419,11 +420,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
--- 31,102
}
/* Return the number of free blocks in a block group. It is used
[Kernel-packages] [Bug 1789436] [NEW] pmtu.sh fails on 4.18 kernel
Public bug reported: pmtu.sh is a network selftest that was introduced on 4.17. It is currently failing on 4.18. After revert of ccd740cbc6 "vti6: Add pmtu handling to vti6_xmit.", it passes. The fail is in the nature of holding netdevices refcounts, so some network operations start hanging, including the loading and removal of network modules. [ 159.936543] unregister_netdevice: waiting for veth_b to become free. Usage count = 1 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Triaged ** Affects: linux (Ubuntu Cosmic) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Triaged ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged -- 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/1789436 Title: pmtu.sh fails on 4.18 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: pmtu.sh is a network selftest that was introduced on 4.17. It is currently failing on 4.18. After revert of ccd740cbc6 "vti6: Add pmtu handling to vti6_xmit.", it passes. The fail is in the nature of holding netdevices refcounts, so some network operations start hanging, including the loading and removal of network modules. [ 159.936543] unregister_netdevice: waiting for veth_b to become free. Usage count = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788767] Re: linux-aws: 4.4.0-1029.32 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788767 Title: linux-aws: 4.4.0-1029.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788748] Re: linux-oem: 4.15.0-1018.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 28. August 2018 14:30 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 28. August 2018 14:30 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1788748 Title: linux-oem: 4.15.0-1018.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional
> Do you have "blacklist i2c_i801" in /etc/modprobe.d/blacklist.conf? Yes it was there. I commented it out, rebooted, and tried the test again. Afterwards there were no issues \o/ I repeated the test again and it continued to work as expected. > Please try kernel parameter "psmouse.synaptics_intertouch=0". I re-blacklisted the i2c_i801 module above, added the parameter to /etc/default/grub, and regenerated my grub. After reboot I ran the test again and there were no issues. I again repeated the test and it continued to work as expected. -- 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/1788928 Title: psmouse: after sleep/suspend thinkpad touchpad not functional Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Summary: The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly. Expected Behavior: After sleep/suspend scroll works correctly. Actual Behavior: Unable to scroll or correctly click on a window and move it without reloading the driver Steps to reproduce: 1. Install Bionic on Thinkpad X1 (4.15.0-32-generic) 2. Open something to scroll (e.g. browser, terminal, etc.) 3. Close lid 4. Re-open lid once sleeping/suspended 5. Try to scroll and note that it does not work Workaround: Run the following after re-opening the lid $ sudo modprobe psmouse -r; sudo modprobe psmouse dmesg on reload: [12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2506 F pulseaudio /dev/snd/controlC0: powersj2506 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (185 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/+subscriptio
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
I built the next test kernel, up to the following commit: 87eba0716011e528f7841026f2cc65683219d0ad The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1784665 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Tue Jul 31 15:53:56 2018 IwConfig: Error: [Errno 2] No such file or directory
[Kernel-packages] [Bug 1788744] Re: linux: 4.15.0-34.37 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1788744 Title: linux: 4.15.0-34.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 (linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 1788761 (linux-hwe-edge) derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 (linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 (linux-kvm) kernel-stable-phase-changed:Monday, 27. August 2018 15:30 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789435] Re: kernel 3.13.0-157+158: ext4: wrong error message »invalid block bitmap«
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1789435
Title:
kernel 3.13.0-157+158: ext4: wrong error message »invalid block
bitmap«
Status in linux package in Ubuntu:
Incomplete
Bug description:
W're getting the »invalid block bitmap« error since kernel 3.13.0-157
see
https://github.com/torvalds/linux/commit/22be37acce25d66ecf6403fc8f44df9c5ded2372
and in this diff the error is within
»if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||«
Kind regards, J. Barth
*** linux_3.13.0-155.205.diff 2018-08-28 14:56:04.357521118 +0200
--- linux_3.13.0-157.207.diff 2018-08-28 14:48:27.168863046 +0200
***
*** 31,37
}
/* Return the number of free blocks in a block group. It is used when
! @@ -419,11 +420,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
--- 31,102
}
/* Return the number of free blocks in a block group. It is used when
! @@ -307,6 +308,7 @@
! ext4_group_t block_group,
! struct buffer_head *bh)
! {
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! ext4_grpblk_t offset;
! ext4_grpblk_t next_zero_bit;
! ext4_fsblk_t blk;
! @@ -326,24 +328,30 @@
! /* check whether block bitmap block number is set */
! blk = ext4_block_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode bitmap block number is set */
! blk = ext4_inode_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode table block number is set */
! blk = ext4_inode_table(sb, desc);
! offset = blk - group_first_block;
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + EXT4_B2C(sbi, offset + sbi->s_itb_per_group) >= sb->s_blocksize)
! + return blk;
! next_zero_bit = ext4_find_next_zero_bit(bh->b_data,
! - offset + EXT4_SB(sb)->s_itb_per_group,
! - offset);
! - if (next_zero_bit < offset + EXT4_SB(sb)->s_itb_per_group)
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group),
! + EXT4_B2C(sbi, offset));
! + if (next_zero_bit <
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group))
! /* bad bitmap for inode tables */
! return blk;
! return 0;
! @@ -394,6 +402,7 @@
! ext4_read_block_bitmap_nowait(struct super_block *sb, ext4_group_t
block_group)
! {
! struct ext4_group_desc *desc;
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! struct buffer_head *bh;
! ext4_fsblk_t bitmap_blk;
!
! @@ -401,6 +410,12 @@
! if (!desc)
! return NULL;
! bitmap_blk = ext4_block_bitmap(sb, desc);
! + if ((bitmap_blk <= le32_to_cpu(sbi->s_es->s_first_data_block)) ||
! + (bitmap_blk >= ext4_blocks_count(sbi->s_es))) {
! + ext4_error(sb, "Invalid block bitmap block %llu in "
! + "block_group %u", bitmap_blk, block_group);
! + return ERR_PTR(-EIO);
! + }
! bh = sb_getblk(sb, bitmap_blk);
! if (unlikely(!bh)) {
! ext4_error(sb, "Cannot get buffer for block bitmap - "
! @@ -419,11 +434,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789435/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789431] Re: ip rule show has unexpected space in destination prefix
Fix proposal submitted upstream: https://marc.info/?l=linux- netdev&m=153546645305223&w=2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1789431 Title: ip rule show has unexpected space in destination prefix Status in iproute2 package in Ubuntu: Triaged Bug description: Introduced by upstream iproute2 v4.17.0: 0dd4ccc5 "iprule: add json support" This commit changes the output of "ip rule show" to support json output but also accidentally inserts a space character between ipv4 address and "/". This breaks for example the route_with_policy test of netplan.io. Testcase: ip rule add from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 ip rule show Expected: *: from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 Actual output: *: from 0.1.0.0/24 to 10.2.0.0 /24 lookup 99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1789431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789431] Re: ip rule show has unexpected space in destination prefix
** Merge proposal linked: https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/353879 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1789431 Title: ip rule show has unexpected space in destination prefix Status in iproute2 package in Ubuntu: Triaged Bug description: Introduced by upstream iproute2 v4.17.0: 0dd4ccc5 "iprule: add json support" This commit changes the output of "ip rule show" to support json output but also accidentally inserts a space character between ipv4 address and "/". This breaks for example the route_with_policy test of netplan.io. Testcase: ip rule add from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 ip rule show Expected: *: from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 Actual output: *: from 0.1.0.0/24 to 10.2.0.0 /24 lookup 99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1789431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional
*** This bug is a duplicate of bug 1786574 *** https://bugs.launchpad.net/bugs/1786574 Thanks for the testing! We have another bug to remove i2c_i801 from blacklist.conf, so I will set this bug as a duplicate. ** This bug has been marked a duplicate of bug 1786574 remove i2c-i801 from blacklist -- 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/1788928 Title: psmouse: after sleep/suspend thinkpad touchpad not functional Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Summary: The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly. Expected Behavior: After sleep/suspend scroll works correctly. Actual Behavior: Unable to scroll or correctly click on a window and move it without reloading the driver Steps to reproduce: 1. Install Bionic on Thinkpad X1 (4.15.0-32-generic) 2. Open something to scroll (e.g. browser, terminal, etc.) 3. Close lid 4. Re-open lid once sleeping/suspended 5. Try to scroll and note that it does not work Workaround: Run the following after re-opening the lid $ sudo modprobe psmouse -r; sudo modprobe psmouse dmesg on reload: [12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2506 F pulseaudio /dev/snd/controlC0: powersj2506 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (185 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789352] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1789352 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1789352 Title: GUI hang when installation with nvidia/intel hybrid mode Status in linux package in Ubuntu: Triaged Bug description: On ThinkPad models with nvidia DGPU. kernel 4.15 will hang when using NOUVEAU to probe nvidia DGP. GUI hang, and installation can NOT proceed. Add nomodeset or blacklist nouveau will be a workaround for hang issue, and continue install Ubuntu bionic and install nvidia driver. After nvidia driver is installed, DGPU works well. Add these workarounds always confuses users. Could Ubuntu add a troubleshooting menu in grub menu when boot to installation media? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789352] [NEW] GUI hang when installation with nvidia/intel hybrid mode
You have been subscribed to a public bug: On ThinkPad models with nvidia DGPU. kernel 4.15 will hang when using NOUVEAU to probe nvidia DGP. GUI hang, and installation can NOT proceed. Add nomodeset or blacklist nouveau will be a workaround for hang issue, and continue install Ubuntu bionic and install nvidia driver. After nvidia driver is installed, DGPU works well. Add these workarounds always confuses users. Could Ubuntu add a troubleshooting menu in grub menu when boot to installation media? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- GUI hang when installation with nvidia/intel hybrid mode https://bugs.launchpad.net/bugs/1789352 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
Can you give v4.15-rc1 a try and see if it has the bug: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ -- 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/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788748] Re: linux-oem: 4.15.0-1018.21 -proposed tracker
Note: there was a conflict while rebasing the oem-next branch on top of Ubuntu-4.15.0-34.37. I skipped the following commit UBUNTU: SAUCE: rsi: fix for incorrect data pointer alignment in 64-bit Since the fix has been implemented by commit 578d1a90b42d21751ffd5653efe6e7373cf140cc Author: Amitkumar Karwar Date: Tue Mar 20 19:10:41 2018 +0530 rsi: fix kernel panic observed on 64bit machine BugLink: http://bugs.launchpad.net/bugs/1786352 [ Upstream commit 864db4d5085349fcfa1f260b5bcd2adde3d7f2ed ] which was pulled in as part of the stable update for 4.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1788748 Title: linux-oem: 4.15.0-1018.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1788744 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789352] Re: GUI hang when installation with nvidia/intel hybrid mode
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** 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/1789352 Title: GUI hang when installation with nvidia/intel hybrid mode Status in linux package in Ubuntu: Triaged Bug description: On ThinkPad models with nvidia DGPU. kernel 4.15 will hang when using NOUVEAU to probe nvidia DGP. GUI hang, and installation can NOT proceed. Add nomodeset or blacklist nouveau will be a workaround for hang issue, and continue install Ubuntu bionic and install nvidia driver. After nvidia driver is installed, DGPU works well. Add these workarounds always confuses users. Could Ubuntu add a troubleshooting menu in grub menu when boot to installation media? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789333] Re: linux-image-4.15.0-33-generic breaks WiFi
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.15 stable 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'.
If you are unable to test the mainline kernel, for example it will not boot,
please add the tag: 'kernel-unable-to-test-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.15.18/
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: needs-bisect
--
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/1789333
Title:
linux-image-4.15.0-33-generic breaks WiFi
Status in linux package in Ubuntu:
Confirmed
Bug description:
Since the upgrade from linux-image-4.15.0-32-generic to linux-
image-4.15.0-33-generic my Dell XPS 13 L322X laptop is unable to
connect to my home WiFi network. It is unable to obtain an IP through
DHCP but more in general it seems unable to receive packets. If I set
up an IP address manually I still cannot ping my router. There are no
noteworthy messages coming through dmesg though. The laptop uses an
AR9462 Wireless Network Adapter and not all WiFi networks fail to work
(but my home network fails to connect in a reproducible manner). The
following step were used to diagnose the problem:
$ uname -a
Linux apol1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ sudo /etc/init.d/network-manager stop
$ echo -e "network={\nssid=\"HT_B23514\"\npsk=\"\"\n}"
> /tmp/wpa_supplicant.conf
$ sudo wpa_supplicant -B -iwlp1s0 -c/tmp/wpa_supplicant.conf -Dwext
$ iwconfig wlp1s0
wlp1s0IEEE 802.11 ESSID:"HT_B23514"
Mode:Managed Frequency:2.412 GHz Access Point: 00:16:FB:B2:35:14
Bit Rate=60 Mb/s Tx-Power=19 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-33 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:48 Missed beacon:0
$ ifconfig wlp1s0
wlp1s0: flags=4163 mtu 1500
inet6 fe80::be85:56ff:fe8f:45f5 prefixlen 64 scopeid 0x20
ether bc:85:56:8f:45:f5 txqueuelen 1000 (Ethernet)
RX packets 49 bytes 9692 (9.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 68 bytes 15466 (15.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$ sudo dhclient -v wlp1s0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on Socket/fallback
DHCPREQUEST of 10.10.10.2 on wlp1s0 to 255.255.255.255 port 67
(xid=0x247b5867)
DHCPREQUEST of 10.10.10.2 on wlp1s0 to 255.255.255.255 port 67
(xid=0x247b5867)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 3 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 4 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 7 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 18 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 20 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 17 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 15 (xid=0x16dac52f)
...
The dhclient command never succeeds. If I revert to kernel linux-
image-4.15.0-32-generic everything works fine instead:
$ uname -a
Linux apol1 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ sudo /etc/init.d/network-manager stop
$ echo -e "network={\nssid=\"HT_B23514\"\npsk=\"\"\n}"
> /tmp/wpa_supplicant.conf
$ sudo wpa_supplicant -B -iwlp1s0 -c/tmp/wpa_supplicant.conf -Dwext
$ iwconfig wlp1s0
wlp1s0IEEE 802.11 ESSID:"HT_B23514"
Mode:Managed Frequency:2.412 GHz Access Point: 00:16:FB:B2:35:14
Bit Rate=144.4 Mb/s Tx-Power=19 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-24 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:12 Missed beacon:0
$ ifconfig wlp1s0
wlp1s0: flags=4163 mtu 1500
inet6 fe80::be85
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
Please refer to LP: #1779817 for regression that caused by this issue's fix. -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.produ
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
Thanks for testing. We need to narrow down the specific version of 4.18
that has the fix. Can you test the following kernels:
v4.18-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1/
v4.18-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc4/
--
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1064086] Re: Cypress trackpad: Occasional taps leak through as clicks even with tap-to-click disabled.
** Branch unlinked: lp:ubuntu/precise-proposed/linux-lts-quantal -- 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/1064086 Title: Cypress trackpad: Occasional taps leak through as clicks even with tap-to-click disabled. Status in Dell Sputnik: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Bug description: I am a Sputnik beta participant, and have the high-end XPS 13. With tap-to-click disabled, occasionally a tap (not hard enough to depress the clickpad) still gets turned into a click. Note that this does not happen constantly, but to reproduce, run this: $ xev | grep Button Place your mouse cursor over the xev window, and begin tapping the trackpad (again, not hard enough to cause a hardware click). The only place I can get it to occur is on the bottom edge or the bottom corners of the trackpad. Unfortunately this happens to be where my thumb sits most of the time, which means this issue bites me. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1064086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1065622] Re: CVE-2012-0957
** Branch unlinked: lp:ubuntu/precise-proposed/linux-lts-quantal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1065622 Title: CVE-2012-0957 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-
[Kernel-packages] [Bug 1678665] Re: mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND
On a Lenovo W520, kernel 4.15.0-33, changing the UEFI Settings for the Security Chip to "disabled" from "ignore" eliminated both this mei-me error, and the tpm error , both of which were appearing on the black screen which appeared briefly after a resume.BIOS revision 8BET62WW (1.42 ), Firmware revision 1.36, SMBIOS 2.6. -- 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/1678665 Title: mei_me :00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [ 2089.236192] mei_me :00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND [ 2089.236196] mei_me :00:16.0: mei_irq_read_handler ret = -71. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2083 F...m pulseaudio /dev/snd/controlC0: caravena 2083 F pulseaudio CurrentDesktop: GNOME Date: Sun Apr 2 16:59:22 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (616 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1678665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789352] Re: GUI hang when installation with nvidia/intel hybrid mode
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789352 Title: GUI hang when installation with nvidia/intel hybrid mode Status in linux package in Ubuntu: New Bug description: On ThinkPad models with nvidia DGPU. kernel 4.15 will hang when using NOUVEAU to probe nvidia DGP. GUI hang, and installation can NOT proceed. Add nomodeset or blacklist nouveau will be a workaround for hang issue, and continue install Ubuntu bionic and install nvidia driver. After nvidia driver is installed, DGPU works well. Add these workarounds always confuses users. Could Ubuntu add a troubleshooting menu in grub menu when boot to installation media? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9
Sorry, I requested testing of the 4.15.0-33 kernel, but should have requested 4.15.0-32. Yes, it would be great if you could identify the last 4.15 kernel that booted and the first that did not. Once we know this, we can perform a bisect to identify the commit that introduced the regression. All of the 4.15 kernels can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Tags removed: kernel-key ** 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/1789118 Title: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: After the most recent 18.04 32-bit upgrade of linux-image-generic, it now refuses to boot under Xen PV mode: . . . [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes) [0.114423] pinctrl core: initialized pinctrl subsystem [0.134326] RTC time: 165:165:165, date: 165/165/65 [0.134442] NET: Registered protocol family 16 [0.134457] xen:grant_table: Grant tables using version 1 layout [0.134502] Grant table initialized [0.134544] audit: initializing netlink subsys (disabled) [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized audit_enabled=0 res=1 [0.134678] EISA bus registered [0.136019] PCI: setting up Xen PCI frontend stub [0.136073] BUG: unable to handle kernel paging request at edc21fd9 [0.136084] IP: eisa_bus_probe+0x19/0x36 [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = [0.136100] Oops: [#1] SMP [0.136105] Modules linked in: [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic #36-Ubuntu [0.136120] EIP: eisa_bus_probe+0x19/0x36 [0.136125] EFLAGS: 00010246 CPU: 0 [0.136130] EAX: edc21fd9 EBX: ECX: 01e0d000 EDX: 0200 [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24 [0.136145] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021 [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660 [0.136166] Call Trace: [0.136173] do_one_initcall+0x49/0x174 [0.136179] ? parse_args+0x143/0x390 [0.136187] ? set_debug_rodata+0x14/0x14 [0.136193] kernel_init_freeable+0x149/0x1c5 [0.136201] ? rest_init+0xa0/0xa0 [0.136207] kernel_init+0xd/0xf0 [0.136213] ret_from_fork+0x2e/0x38 [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8 [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24 [0.14] CR2: edc21fd9 [0.14] ---[ end trace 8c00b3cb7d4f06ba ]--- [0.140013] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 This is: [0.00] Linux version 4.15.0-33-generic (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu 4.15.0-33.36-generic 4.15.18) Switching to a 64-bit kernel allows boot to proceed. I cannot include output of the commands you request (uname, version_signature, dmesg, lspci) because the guest doesn't boot. The above kernel output is from a just-installed clean guest however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789018] Re: /sys/power/state miss "disk"
Thx for information from Kai-Heng Feng. After disable secure boot, kernel lockdown is inactive. And then “disk” appear in /sys/power/state, and hibernation function normal. -- 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/1789018 Title: /sys/power/state miss "disk" Status in linux package in Ubuntu: Incomplete Bug description: cat /sys/power/state freeze mem As a result, hibernate-disk is failed to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ming 1501 F pulseaudio CurrentDesktop: XFCE Date: Sat Aug 25 22:42:04 2018 HibernationDevice: RESUME=UUID=6c3eb510-861e-4d9a-9009-0c5b62d57105 InstallationDate: Installed on 2018-08-11 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0570 LighTuning Technology Inc. Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-54 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=8e486299-4bbf-4041-8cae-502b7f7e6c5c ro splash resume=UUID=6c3eb510-861e-4d9a-9009-0c5b62d57105 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd05/25/2018:svnAcer:pnSwiftSF314-54:pvrV1.07:rvnKBL:rnStrongbow_KL:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788753] Re: linux-kvm: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788753 Title: linux-kvm: 4.15.0-1021.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787988] Re: linux: 4.17.0-9.10 -proposed tracker
** Tags added: regression-testing-passed -- 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/1787988 Title: linux: 4.17.0-9.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.17.0-9.10 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
What about calling it like this: $ sudo systemd-run ./testcases/bin/msgstress03 Does that make it pass correctly? Which resource in particular is exhausted? and can it be toggled somehow using any of https://www.freedesktop.org/software/systemd/man/systemd.directives.html ? ** Changed in: systemd (Ubuntu Cosmic) Status: New => Incomplete -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in systemd source package in Cosmic: Incomplete Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789333] Re: linux-image-4.15.0-33-generic breaks WiFi
Okay, I will test this when I get back at home later this evening (EST
time). The WiFi at my workplace works fine. Not sure why it selectively
fails to work with my home WiFi. If you want to gather any additional
info about what differences could be involved please let me know.
--
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/1789333
Title:
linux-image-4.15.0-33-generic breaks WiFi
Status in linux package in Ubuntu:
Confirmed
Bug description:
Since the upgrade from linux-image-4.15.0-32-generic to linux-
image-4.15.0-33-generic my Dell XPS 13 L322X laptop is unable to
connect to my home WiFi network. It is unable to obtain an IP through
DHCP but more in general it seems unable to receive packets. If I set
up an IP address manually I still cannot ping my router. There are no
noteworthy messages coming through dmesg though. The laptop uses an
AR9462 Wireless Network Adapter and not all WiFi networks fail to work
(but my home network fails to connect in a reproducible manner). The
following step were used to diagnose the problem:
$ uname -a
Linux apol1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ sudo /etc/init.d/network-manager stop
$ echo -e "network={\nssid=\"HT_B23514\"\npsk=\"\"\n}"
> /tmp/wpa_supplicant.conf
$ sudo wpa_supplicant -B -iwlp1s0 -c/tmp/wpa_supplicant.conf -Dwext
$ iwconfig wlp1s0
wlp1s0IEEE 802.11 ESSID:"HT_B23514"
Mode:Managed Frequency:2.412 GHz Access Point: 00:16:FB:B2:35:14
Bit Rate=60 Mb/s Tx-Power=19 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-33 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:48 Missed beacon:0
$ ifconfig wlp1s0
wlp1s0: flags=4163 mtu 1500
inet6 fe80::be85:56ff:fe8f:45f5 prefixlen 64 scopeid 0x20
ether bc:85:56:8f:45:f5 txqueuelen 1000 (Ethernet)
RX packets 49 bytes 9692 (9.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 68 bytes 15466 (15.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$ sudo dhclient -v wlp1s0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on Socket/fallback
DHCPREQUEST of 10.10.10.2 on wlp1s0 to 255.255.255.255 port 67
(xid=0x247b5867)
DHCPREQUEST of 10.10.10.2 on wlp1s0 to 255.255.255.255 port 67
(xid=0x247b5867)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 3 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 4 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 7 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 18 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 20 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 17 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 15 (xid=0x16dac52f)
...
The dhclient command never succeeds. If I revert to kernel linux-
image-4.15.0-32-generic everything works fine instead:
$ uname -a
Linux apol1 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ sudo /etc/init.d/network-manager stop
$ echo -e "network={\nssid=\"HT_B23514\"\npsk=\"\"\n}"
> /tmp/wpa_supplicant.conf
$ sudo wpa_supplicant -B -iwlp1s0 -c/tmp/wpa_supplicant.conf -Dwext
$ iwconfig wlp1s0
wlp1s0IEEE 802.11 ESSID:"HT_B23514"
Mode:Managed Frequency:2.412 GHz Access Point: 00:16:FB:B2:35:14
Bit Rate=144.4 Mb/s Tx-Power=19 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-24 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:12 Missed beacon:0
$ ifconfig wlp1s0
wlp1s0: flags=4163 mtu 1500
inet6 fe80::be85:56ff:fe8f:45f5 prefixlen 64 scopeid 0x20
ether bc:85:56:8f:45:f5 txqueuelen 1000 (Ethernet)
RX packets 586 bytes 364645 (364.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 684 bytes 191764 (191.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$ sudo dhclient -v wlp1s0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For in
[Kernel-packages] [Bug 1787988] Re: linux: 4.17.0-9.10 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed -- 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/1787988 Title: linux: 4.17.0-9.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.17.0-9.10 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776654] Re: systemd upstream sysusers tests fails
Does this still fail with v239 which has now landed? ** Changed in: systemd (Ubuntu Cosmic) Status: New => Incomplete -- 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/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in systemd source package in Cosmic: Incomplete Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789435] Re: kernel 3.13.0-157+158: ext4: wrong error message »invalid block bitmap«
*** This bug is a duplicate of bug 1789131 ***
https://bugs.launchpad.net/bugs/1789131
** This bug has been marked a duplicate of bug 1789131
Probable regression with EXT3 file systems and CVE-2018-1093 patches
--
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/1789435
Title:
kernel 3.13.0-157+158: ext4: wrong error message »invalid block
bitmap«
Status in linux package in Ubuntu:
Incomplete
Bug description:
W're getting the »invalid block bitmap« error since kernel 3.13.0-157
see
https://github.com/torvalds/linux/commit/22be37acce25d66ecf6403fc8f44df9c5ded2372
and in this diff the error is within
»if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||«
Kind regards, J. Barth
*** linux_3.13.0-155.205.diff 2018-08-28 14:56:04.357521118 +0200
--- linux_3.13.0-157.207.diff 2018-08-28 14:48:27.168863046 +0200
***
*** 31,37
}
/* Return the number of free blocks in a block group. It is used when
! @@ -419,11 +420,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
--- 31,102
}
/* Return the number of free blocks in a block group. It is used when
! @@ -307,6 +308,7 @@
! ext4_group_t block_group,
! struct buffer_head *bh)
! {
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! ext4_grpblk_t offset;
! ext4_grpblk_t next_zero_bit;
! ext4_fsblk_t blk;
! @@ -326,24 +328,30 @@
! /* check whether block bitmap block number is set */
! blk = ext4_block_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode bitmap block number is set */
! blk = ext4_inode_bitmap(sb, desc);
! offset = blk - group_first_block;
! - if (!ext4_test_bit(offset, bh->b_data))
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
! /* bad block bitmap */
! return blk;
!
! /* check whether the inode table block number is set */
! blk = ext4_inode_table(sb, desc);
! offset = blk - group_first_block;
! + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
! + EXT4_B2C(sbi, offset + sbi->s_itb_per_group) >= sb->s_blocksize)
! + return blk;
! next_zero_bit = ext4_find_next_zero_bit(bh->b_data,
! - offset + EXT4_SB(sb)->s_itb_per_group,
! - offset);
! - if (next_zero_bit < offset + EXT4_SB(sb)->s_itb_per_group)
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group),
! + EXT4_B2C(sbi, offset));
! + if (next_zero_bit <
! + EXT4_B2C(sbi, offset + EXT4_SB(sb)->s_itb_per_group))
! /* bad bitmap for inode tables */
! return blk;
! return 0;
! @@ -394,6 +402,7 @@
! ext4_read_block_bitmap_nowait(struct super_block *sb, ext4_group_t
block_group)
! {
! struct ext4_group_desc *desc;
! + struct ext4_sb_info *sbi = EXT4_SB(sb);
! struct buffer_head *bh;
! ext4_fsblk_t bitmap_blk;
!
! @@ -401,6 +410,12 @@
! if (!desc)
! return NULL;
! bitmap_blk = ext4_block_bitmap(sb, desc);
! + if ((bitmap_blk <= le32_to_cpu(sbi->s_es->s_first_data_block)) ||
! + (bitmap_blk >= ext4_blocks_count(sbi->s_es))) {
! + ext4_error(sb, "Invalid block bitmap block %llu in "
! + "block_group %u", bitmap_blk, block_group);
! + return ERR_PTR(-EIO);
! + }
! bh = sb_getblk(sb, bitmap_blk);
! if (unlikely(!bh)) {
! ext4_error(sb, "Cannot get buffer for block bitmap - "
! @@ -419,11 +434,15 @@
}
ext4_lock_group(sb, block_group);
if (desc->bg_flags & cpu_to_le16(EXT4_BG_BLOCK_UNINIT)) {
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789435/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789459] [NEW] linux: 4.18.0-7.8 -proposed tracker
Public bug reported: This bug is for tracking the 4.18.0-7.8 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Cosmic) Importance: Medium Status: Confirmed ** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2018.08.28-1 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: cosmic ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags added: kernel-sru-cycle-d2018.08.28-1 ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) ** Changed in: kernel-sr
[Kernel-packages] [Bug 1789227] Re: nvme devices namespace assigned to the wrong controller
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- 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/1789227 Title: nvme devices namespace assigned to the wrong controller Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == Impact == During device discovery, when multipath is disabled, nvme multipath module will very likely think that the name space on one nvme controller belongs to the other controller. == Fix == Commit a785dbccd95c37606c720580714f5a7a8b3255f1 upstream From: Keith Busch When CONFIG_NVME_MULTIPATH is set, but we're not using nvme to multipath, namespaces with multiple paths were not creating unique names due to reusing the same instance number from the namespace's head. This patch fixes this by falling back to the non-multipath naming method when the parameter disabled using multipath. Reported-by: Mike Snitzer Signed-off-by: Keith Busch Reviewed-by: Christoph Hellwig Signed-off-by: Jens Axboe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Importance: High => Critical ** Changed in: linux (Ubuntu Trusty) Importance: High => Critical -- 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/1789131 Title: Probable regression with EXT3 file systems and CVE-2018-1093 patches Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: A customer reported on all of their ext3 and none of their ext4 systems that the file system was in read-only mode, I believe after rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output of tune2fs -l for one of the file systems: tune2fs 1.42.12 (29-Aug-2014) Last mounted on: / Filesystem UUID: 748f503a-443d-4769-8dd2-45ff46b48555 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 1966080 Block count: 7863296 Reserved block count: 393164 Free blocks: 4568472 Free inodes: 1440187 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 1022 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:512 Filesystem created: Thu Feb 25 21:54:24 2016 Last mount time: Fri Aug 24 07:40:51 2018 Last write time: Fri Aug 24 07:40:51 2018 Mount count: 1 Maximum mount count: 25 Last checked: Fri Aug 24 07:38:54 2018 Check interval: 15552000 (6 months) Next check after: Wed Feb 20 07:38:54 2019 Lifetime writes: 7381 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 Default directory hash: half_md4 Directory Hash Seed: d6564a54-cd2a-4804-ad94-1e4e0e47933a Journal backup: inode blocks FS Error count: 210 First error time: Fri Aug 24 07:40:51 2018 First error function: ext4_validate_block_bitmap First error line #: 376 First error inode #: 0 First error block #: 0 Last error time: Sun Aug 26 19:35:16 2018 Last error function: ext4_remount Last error line #:4833 Last error inode #: 0 Last error block #: 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
PASS: Kernel 4.15-rc1 (bisect6) up to 87eba0716011e528f7841026f2cc65683219d0ad -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Tue Jul 31 15:53:56 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.
[Kernel-packages] [Bug 1788881] Re: linux: 4.18.0-6.7 -proposed tracker
*** This bug is a duplicate of bug 1789459 *** https://bugs.launchpad.net/bugs/1789459 ** This bug has been marked a duplicate of bug 1789459 linux: 4.18.0-7.8 -proposed tracker -- 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/171 Title: linux: 4.18.0-6.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
