[Kernel-packages] [Bug 1840021] Re: xenial/linux: 4.4.0-160.188 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840018 (trusty/linux-aws), bug 1840020 (trusty/linux-lts-xenial) derivatives: bug 1840008 (pc-kernel), bug 1840010 (linux-aws), bug 1840012 (linux-kvm), bug 1840014 (linux-raspi2), bug 1840016 (linux-snapdragon), bug 1840017 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 20:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1840018 trusty/linux-lts-xenial: bug 1840020 xenial/linux-aws: bug 1840010 xenial/linux-fips: bug 1840017 xenial/linux-kvm: bug 1840012 xenial/linux-raspi2: bug 1840014 xenial/linux-snapdragon: bug 1840016 xenial/linux/pc-kernel: bug 1840008 variant: debs -- 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/1840021 Title: xenial/linux: 4.4.0-160.188 -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: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840018 (trusty/linux-aws), bug 1840020 (trusty/linux-lts-xenial) derivatives: bug 1840008 (pc-kernel), bug 1840010 (linux-aws), bug 1840012 (linux-kvm), bug 1840014 (linux-raspi2), bug 1840016 (linux-snapdragon), bug 1840017 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 20:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1840018 trusty/linux-lts-xenial: bug 1840020 xenial/linux-aws: bug 1840010 xenial/linux-fips: bug 1840017 xenial/linux-kvm: bug 1840012 xenial/linux-raspi2: bug 1840014 xenial/linux-snapdragon: bug 1840016 xenial/linux/pc-kernel: bug 1840008 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840021/+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 1841139] 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 1841139 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 ** Tags added: bionic -- 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/1841139 Title: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu. Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Platform: dell 5420 / 5424 with AMD GPU. D-SUB or display port hot plug won't work in bionic with bionic kernel oem 4.15 -1048 and oem-osp1 5.0 -1016. It can be work around with amdgpu.runpm=0 kernel parameter, with the price of higher power consumption. As install bios 89.7.48 + Kernel: 4.15.0-1043-oem + amdgpu: amdgpu-pro-19.10-793418 The hotplug works. However, no DP audio (unless boot with DP plugged). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841139/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -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 will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Thursday, 22. August 2019 17:11 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 23. August 2019 06:56 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs -- 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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-lrm 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Friday, 23. August 2019 06:56 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1840945] Re: Concatenated lz4 initrds don't work
I tried all the COMPRESS= methods available in /etc/initramfs- tools/initramfs.conf in both eoan and bionic. For each one, I ran: date > date.txt echo date.txt | cpio -oH newc > date.img update-initramfs -u cat initrd.lz4 date.img > initrd.img kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh The results show that: xz works in both eoan and bionic, gzip and bzip2 regressed in eoan, lzma, lzop and lz4 never worked. === EOAN === Linux kernel x86 boot executable bzImage, version 5.2.0-10-generic (buildd@lgw01-amd64-046) #11-Ubuntu SMP Tue Jul 30 19:19:46 UTC 2019, RO-rootFS, swap_dev 0x8, Normal VGA SIZE FILENAME WORKS? 9016056 vmlinuz 43335408 initrd.xz yes 43339869 initrd.lzma no date.txt 63081861 initrd.bzip2 no date.txt 68362761 initrd.lzop no date.txt 68364423 initrd.gzip no date.txt 77600825 initrd.lz4kernel panic === BIONIC === Linux kernel x86 boot executable bzImage, version 4.15.0-58-generic (buildd@lcy01-amd64-013) #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019, RO-rootFS, swap_dev 0x7, Normal VGA SIZE FILENAME WORKS? 8302232 vmlinuz 39946592 initrd.xz yes 39942761 initrd.lzma no date.txt 56997316 initrd.bzip2 yes 61043794 initrd.lzop no date.txt 61046528 initrd.gzip yes -- 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/1840945 Title: Concatenated lz4 initrds don't work Status in linux package in Ubuntu: Confirmed Bug description: Concatenating multiple initrds works fine with gzipped initrds. (microcode+gzip+gzip) => the kernel properly decompresses that With lz4, it can't decompress anything after the first lz4: (microcode+lz4+whatever) => it doesn't decompress whatever. To reproduce: Get vmlinuz and initrd.img from an eoan daily build and put them in a directory. Create an lz4 (or gzip or uncompressed cpio, it doesn't matter): # date > date.txt # echo date.txt | cpio -oH newc | lz4 > date.img Concatenate them: # cat initrd.img.original date.img > initrd.img Boot them: # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh Then inside kvm: # ls /date.txt The additional file doesn't exist. `dmesg | grep -i initramfs` reports: Trying to unpack rootfs image as initramfs... Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1841147] [NEW] linux: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841146 (bionic/linux-hwe-edge) -- swm properties -- variant: debs ** 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: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** 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 Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.08.23-1 ** 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 ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** 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 ** Tags added: kernel-release-tracking-bug-live ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + -- swm properties -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.08.23-1 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kern
[Kernel-packages] [Bug 1841148] [NEW] Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver
Public bug reported: Since linux-image-4.15.0-58-generic my ethernet connection fails to get a connection. The network connection constantly goes up and down. The issue has been reported by another user: https://bugzilla.kernel.org/show_bug.cgi?id=204591 Snippet from kern.log showing that the connection constantly goes up and down: Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134651] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134830] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134836] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134858] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134868] bridge-enp0s31f6: up Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134872] bridge-enp0s31f6: attached Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334794] userif-2: sent link down event. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334801] userif-2: sent link up event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.156471] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158580] bridge-enp0s31f6: down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158599] bridge-enp0s31f6: detached Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356790] userif-2: sent link down event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356795] userif-2: sent link up event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295365] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295729] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295741] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295785] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295804] bridge-enp0s31f6: up Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295810] bridge-enp0s31f6: attached Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495615] userif-2: sent link down event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495620] userif-2: sent link up event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316505] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316593] bridge-enp0s31f6: down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316607] bridge-enp0s31f6: detached Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516761] userif-2: sent link down event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516767] userif-2: sent link up event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.438729] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440433] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440439] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440466] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440475] bridge-enp0s31f6: up Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440479] bridge-enp0s31f6: attached Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638884] userif-2: sent link down event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638890] userif-2: sent link up event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.460451] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461881] bridge-enp0s31f6: down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461902] bridge-enp0s31f6: detached Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660746] userif-2: sent link down event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660752] userif-2: sent link up event. Aug 20 10:06:20 martijn-ThinkPad-P50 kernel: [ 2447.583182] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx inxi -i: Network: Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e lspci: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) The connection works again if I revert to an older kernel. lsb_release -rd: Description: Ubuntu 18.04.3 LTS Release: 18.04 Expected to happen: Ethernet connection is established What happened instead: Connection is constantly going up and down ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia
[Kernel-packages] [Bug 1841148] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841148 Title: Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-58-generic my ethernet connection fails to get a connection. The network connection constantly goes up and down. The issue has been reported by another user: https://bugzilla.kernel.org/show_bug.cgi?id=204591 Snippet from kern.log showing that the connection constantly goes up and down: Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134651] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134830] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134836] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134858] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134868] bridge-enp0s31f6: up Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134872] bridge-enp0s31f6: attached Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334794] userif-2: sent link down event. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334801] userif-2: sent link up event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.156471] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158580] bridge-enp0s31f6: down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158599] bridge-enp0s31f6: detached Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356790] userif-2: sent link down event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356795] userif-2: sent link up event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295365] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295729] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295741] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295785] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295804] bridge-enp0s31f6: up Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295810] bridge-enp0s31f6: attached Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495615] userif-2: sent link down event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495620] userif-2: sent link up event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316505] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316593] bridge-enp0s31f6: down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316607] bridge-enp0s31f6: detached Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516761] userif-2: sent link down event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516767] userif-2: sent link up event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.438729] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440433] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440439] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440466] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440475] bridge-enp0s31f6: up Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440479] bridge-enp0s31f6: attached Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638884] userif-2: sent link down event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638890] userif-2: sent link up event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.460451] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461881] bridge-enp0s31f6: down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461902] bridge-enp0s31f6: detached Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660746] userif-2: sent link down event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660752] userif-2: sent link up event. Aug 20 10:06:20 martijn-ThinkPad-P50 kernel: [ 2447.583182] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx inxi -i: Network: Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e lspci: 00:1f.6 Ethernet controller: Intel Corporati
[Kernel-packages] [Bug 1777779] Re: ubuntu_ltp_syscalls test will hang in the end on T/X AWS
This seems to be caused by bug 1775165, with fanotify07 blacklisted this was never occurred again. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => 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/179 Title: ubuntu_ltp_syscalls test will hang in the end on T/X AWS Status in ubuntu-kernel-tests: Fix Released Status in linux-aws package in Ubuntu: New Bug description: The ubuntu_ltp_syscalls test will hang on Trusty (and Xenial) AWS, even though all the tests have been ran. INFO: ltp-pan reported some tests FAIL LTP Version: 20180515 ### Done executing testcases. LTP Version: 20180515 ### stderr: rm: cannot remove ‘/tmp/ltp-X72GtnsMYy/Q4ynCy/mntpoint’: Device or resource busy 10:19:14 INFO | END ERROR ubuntu_ltp_syscalls.syscalls ubuntu_ltp_syscalls.syscallstimestamp=1529403554localtime=Jun 19 10:19:14 10:19:14 DEBUG| Persistent state client._record_indent now set to 1 10:19:14 DEBUG| Persistent state client.unexpected_reboot deleted 10:19:14 INFO | END GOOD timestamp=1529403554 localtime=Jun 19 10:19:14 10:19:14 DEBUG| Persistent state client._record_indent now set to 0 10:19:14 INFO | Report successfully generated at /home/ubuntu/autotest/client/results/default/job_report.html If you log onto the node, you will see a zombie process. The jenkins job will continue when you have that zombie process's parent killed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-1024-aws 4.4.0-1024.25 ProcVersionSignature: User Name 4.4.0-1024.25-aws 4.4.134 Uname: Linux 4.4.0-1024-aws x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Jun 20 05:58:27 2018 Ec2AMI: ami-221f5c5a Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: c3.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/179/+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 1841159] [NEW] eoan/linux: 5.2.0-14.15 -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- variant: debs ** 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: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Paolo Pisati (p-pisati) 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 Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.08.23-2 ** 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 ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** 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 ** Tags added: kernel-release-tracking-bug-live ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + -- swm properties -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.08.23-2 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + backports: bug 184115
[Kernel-packages] [Bug 1841147] Re: linux: -proposed tracker
*** This bug is a duplicate of bug 1841159 *** https://bugs.launchpad.net/bugs/1841159 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - backports: bug 1841146 (bionic/linux-hwe-edge) - -- swm properties -- variant: debs ** This bug has been marked a duplicate of bug 1841159 linux: -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/1841147 Title: linux: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841147/+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 1828166] Re: perf top problem on z with Ubuntu 18.04
Hello IBM, Thank you for the feedback. We will submit the patches for integration into the next SRU cycle. -- 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+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 1833387] Re: Add pointstick support on HP ZBook 17 G5
Xenial doesn't need this. ** Tags removed: verification-needed-xenial -- 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/1833387 Title: Add pointstick support on HP ZBook 17 G5 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Pointstick on HP ZBook 17 G5 doesn't work. [Fix] Let hid-multitouch know it has a pointstick, and exposes it as a mouse. [Test] With the fix applied the pointstick starts to work. [Regression Potential] Low. It's limited to one driver and limited to one specific device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1833387/+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 1756315] Re: fstrim and discard operations take too long to complete - Ubuntu 16.04
I can confirm this bug on Ubuntu 16.04.6 LTS. Apparently it is related to latest kernel update (in my case HWE). --- Affected version: Linux version 4.15.0-58-generic (buildd@lgw01-amd64-037) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)) #64~16.04.1-Ubuntu SMP Wed Aug 7 14:10:35 UTC 2019 root@lukas:~# time fstrim -v / /: 206.6 GiB (221849395200 bytes) trimmed real22m18.448s user0m0.001s sys 0m18.827s root@lukas:~# lukas@lukas:~$ collectl -s d -i 1 waiting for 1 second sample... #<--Disks---> #KBRead Reads KBWrit Writes 0 0 0 0 8 1 0 0 8 1 4344 1083 0 0 21848 1939 0 0 26420 1360 0 0 24468 1275 ... Normally I see spike in write and fstrim is done within seconds. On version 4.15.0-58-generic is taking 20 to 30 minutes to complete. During this time I see write to disk at around 25 - 30 MB/s and overall system experience is slow (UI response, load time, speed of file operations) --- Unaffected version: Linux version 4.15.0-55-generic (buildd@lgw01-amd64-038) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)) #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 root@lukas:~# time fstrim -v / /: 144.4 GiB (155019710464 bytes) trimmed real0m3.185s user0m0.006s sys 0m0.000s root@lukas:~# lukas@lukas:~$ collectl -s d -i 1 waiting for 1 second sample... #<--Disks---> #KBRead Reads KBWrit Writes 0 0 0 0 0 0 86398K 71 0 0 61439K 45 0 0 0 0 0 0 0 0 ... I rebooted my laptop to previous kernel version. e.g. Same userspace, only kernel change. Fstrim finished within few seconds. Collectl + system load indicator displayed much higher write throughput during fstrim operation. --- I see same behaviour on both my laptops. Both are configured in way SSD -> partitions -> luks -> btrfs. Primary laptop have disk "SanDisk SD7SN6S-512G-1006". Backup laptop "Micron C400 RealSSD 256GB mSATA". I don't see this problem on disks attached via iSCSI. --- ... while writing this post I noticed that there is different amount of "trimed" data reported. This may be due to snapshots being released (I was capturing data +- at time when daily snapshots are released) and not some kind of destructive problem ... -- 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/1756315 Title: fstrim and discard operations take too long to complete - Ubuntu 16.04 Status in linux-aws package in Ubuntu: Confirmed Bug description: 1-) Ubuntu Release : Ubuntu 16.04 LTS 2-) linux-image-4.4.0.1052.54-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs took around 2 hours. Running fstrim -v on the mount point mounted on top of the raid array took around 2 hours. How to reproduce the issue: - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 16.04 AMI ( ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS root volume and two 1.9T SSD drives that are presented to the instance using the nvme driver. - Compose a raid0 array with the following command : # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2 /dev/nvme0n1 /dev/nvme1n1 - When trying to format the raid0 array ( /dev/md0 ) using xfs it takes around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0 real120m45.725s user0m0.000s sys 0m18.248s - Running fstrim -v on a filesystem mounted on top of /dev/md0 can take around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. - When I try the same with any of the nvme SSD devices alone, let's say /dev/nvme0n1, the issue doesn't happen. - I tried to replicate this issue using LVM and striping, fstrim and mkfs.xfs, the tasks complete without taking hours : root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1 Physical volume "/dev/nvme0n1" successfully created root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1 Physical volume "/dev/nvme1n1" successfully created root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1 Volume group "raid0" successfully created root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE raid0
[Kernel-packages] [Bug 1775165] Re: fanotify07 in LTP syscall test generates kernel trace with T/X kernel
Test blacklisted for older kernels https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=1e99a9a95ba6e99440b46b9f0911fbd63d4dc95f ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- 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/1775165 Title: fanotify07 in LTP syscall test generates kernel trace with T/X kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1775165 [Impact] When userspace tasks which are processing fanotify permission events act incorrectly, the fsnotify_mark_srcu SRCU is held indefinitely which causes the whole notification subsystem to hang. This has been seen in production, and it can also be seen when running the Linux Test Project testsuite, specifically fanotify07. [Fix] Instead of holding the SRCU lock while waiting for userspace to respond, which may never happen, or not in the order we are expecting, we drop the fsnotify_mark_srcu SRCU lock before waiting for userspace response, and then reacquire the lock again when userspace responds. The fixes are from a series of upstream commits: 05f0e38724e8449184acd8fbf0473ee5a07adc6c (cherry-pick) 9385a84d7e1f658bb2d96ab798393e4b16268aaa (backport) abc77577a669f424c5d0c185b9994f2621c52aa4 (backport) The following are upstream commits necessary for the fixes to function: 35e481761cdc688dbee0ef552a13f49af8eba6cc (backport) 0918f1c309b86301605650c836ddd2021d311ae2 (cherry-pick) [Testcase] You can reproduce the problem pretty quickly with the Linux Test Project: Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs 9. ./runltp -f /tmp/jobs On a stock Xenial kernel, the system will hang, and the testcase will look like: <<>> tag=fanotify07 stime=1554326200 cmdline="fanotify07 " contacts="" analysis=exit <<>> tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... <<>> initiation_status="ok" duration=350 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> Looking at dmesg, we see the following call stack [ 790.772792] LTP: starting fanotify07 (fanotify07 ) [ 960.140455] INFO: task fsnotify_mark:36 blocked for more than 120 seconds. [ 960.140867] Not tainted 4.4.0-142-generic #168-Ubuntu [ 960.141185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 960.141498] fsnotify_mark D 8800b6703c98 036 2 0x [ 960.141516] 8800b6703c98 88013a558a00 8800b7797000 8800b66f8000 [ 960.141524] 8800b6704000 7fff 8800b6703de0 8800b66f8000 [ 960.141528] 8800b6703cb0 8185cb45 8800b6703de8 [ 960.141532] Call Trace: [ 960.141580] [] schedule+0x35/0x80 [ 960.141588] [] schedule_timeout+0x1b4/0x270 [ 960.141617] [] ? mod_timer+0x10c/0x240 [ 960.141621] [] ? __schedule+0x30d/0x810 [ 960.141625] [] wait_for_completion+0xb2/0x190 [ 960.141636] [] ? wake_up_q+0x70/0x70 [ 960.141641] [] __synchronize_srcu+0x100/0x1a0 [ 960.141645] [] ? trace_raw_output_rcu_utilization+0x60/0x60 [ 960.141664] [] ? fsnotify_put_mark+0x40/0x40 [ 960.141669] [] synchronize_srcu+0x24/0x30 [ 960.141672] [] fsnotify_mark_destroy+0x84/0x130 [ 960.141680] [] ? wake_atomic_t_function+0x60/0x60 [ 960.141691] [] kthread+0xe7/0x100 [ 960.141694] [] ? __schedule+0x301/0x810 [ 960.141699] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 960.141703] [] ret_from_fork+0x55/0x80 [ 960.141706] [] ? kthread_create_on_node+0x1e0/0x1e0 The vanilla 4.4 kernel also shows the same call stack. On a patched kernel, the test will pass successfully, and there will be no messages in dmesg. [Regression Potential] This makes modifications to how locking is performed in fsnotif
[Kernel-packages] [Bug 1840945] Re: Concatenated lz4 initrds don't work
`| lz4 > date.img` is incorrect One must use `lz4 -9 -l` For xz one should use `xz --check=crc32` -- 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/1840945 Title: Concatenated lz4 initrds don't work Status in linux package in Ubuntu: Confirmed Bug description: Concatenating multiple initrds works fine with gzipped initrds. (microcode+gzip+gzip) => the kernel properly decompresses that With lz4, it can't decompress anything after the first lz4: (microcode+lz4+whatever) => it doesn't decompress whatever. To reproduce: Get vmlinuz and initrd.img from an eoan daily build and put them in a directory. Create an lz4 (or gzip or uncompressed cpio, it doesn't matter): # date > date.txt # echo date.txt | cpio -oH newc | lz4 > date.img Concatenate them: # cat initrd.img.original date.img > initrd.img Boot them: # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh Then inside kvm: # ls /date.txt The additional file doesn't exist. `dmesg | grep -i initramfs` reports: Trying to unpack rootfs image as initramfs... Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1840010] Re: xenial/linux-aws: 4.4.0-1091.102 -proposed tracker
4.4.0-1091.102 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): ubuntu_kernel_selftests - cpu_hotplug (bug 1812149) on t2.small ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) vmx (bug 1821394) vmx_hlt_with_rvi_test (bug 1822308) vmx_apic_passthrough_thread (bug 1822309) debug (bug 1821906) failed on i3.metal ubuntu_ltp - should be skipped ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify07 blacklisted (bug 1775165) fanotify09 (bug 1775153) fanotify10 (bug 1802454) inotify07 (bug 1774387) inotify08 (bug 1775784) leapsec01 (bug 1839135) sync_file_range02 (bug 1819116) ubuntu_zram_smoke_test - failed on i3.metal only, passed on the rest Skipped / blacklisted: * ubuntu_ltp * ubuntu_seccomp * ubuntu_sysdig_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1840010 Title: xenial/linux-aws: 4.4.0-1091.102 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress 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: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840009 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 15. August 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1840009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840010/+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 1840010] Re: xenial/linux-aws: 4.4.0-1091.102 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840009 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 15. August 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1840009 variant: debs -- 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/1840010 Title: xenial/linux-aws: 4.4.0-1091.102 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress 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: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840009 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 15. August 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1840009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840010/+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 1756315] Re: fstrim and discard operations take too long to complete - Ubuntu 16.04
Update to my previous comment ... running fstrim on 4.15.0-58-generic result in much more reported trimmed data (206.6 GiB) vs 4.15.0-55-generic (144.4 GiB) (e.g. this was not caused by snapshot release). On 4.15.0-58-generic I see errors like this in kernel log: BTRFS warning (device dm-0): failed to trim 307 block group(s), last error -512 BTRFS warning (device dm-0): failed to trim 1 device(s), last error -512 Scrub finished with not problems so data on disk are fine (yeah!). -- 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/1756315 Title: fstrim and discard operations take too long to complete - Ubuntu 16.04 Status in linux-aws package in Ubuntu: Confirmed Bug description: 1-) Ubuntu Release : Ubuntu 16.04 LTS 2-) linux-image-4.4.0.1052.54-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs took around 2 hours. Running fstrim -v on the mount point mounted on top of the raid array took around 2 hours. How to reproduce the issue: - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 16.04 AMI ( ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS root volume and two 1.9T SSD drives that are presented to the instance using the nvme driver. - Compose a raid0 array with the following command : # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2 /dev/nvme0n1 /dev/nvme1n1 - When trying to format the raid0 array ( /dev/md0 ) using xfs it takes around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0 real120m45.725s user0m0.000s sys 0m18.248s - Running fstrim -v on a filesystem mounted on top of /dev/md0 can take around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. - When I try the same with any of the nvme SSD devices alone, let's say /dev/nvme0n1, the issue doesn't happen. - I tried to replicate this issue using LVM and striping, fstrim and mkfs.xfs, the tasks complete without taking hours : root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1 Physical volume "/dev/nvme0n1" successfully created root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1 Physical volume "/dev/nvme1n1" successfully created root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1 Volume group "raid0" successfully created root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE raid0 /dev/nvme0n1 /dev/nvme1n1 Using default stripesize 64.00 KiB. Logical volume "lvol0" created. root@ip-172-31-27-69:~# vgchange -ay 1 logical volume(s) in volume group "raid0" now active root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0 root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0 LVVGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 raid0 -wi-a- 3.46t htop root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0 meta-data=/dev/raid0/lvol0 isize=512agcount=32, agsize=28991664 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=927733248, imaxpct=5 = sunit=16 swidth=32 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=453008, version=2 = sectsz=512 sunit=16 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 real0m2.926s user0m0.180s sys 0m0.000s root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt root@ip-172-31-27-69:~# time fstrim -v /mnt /mnt: 3.5 TiB (3798138650624 bytes) trimmed real0m1.794s user0m0.000s sys 0m0.000s So the issue only happens when using nvme and md to compose the raid0 array. Bellow follows some information that may be useful: started formating the md array with mkfs.xfs. Process looks hanged. root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs root 1693 12.0 0.0 12728 968 pts/1D+ 07:54 0:03 mkfs.xfs /dev/md0 PID 1693 is in uninterruptible sleep ( D ) Looking at /proc/7965/stack root@ip-172-31-24-66:~# cat /proc/1693/stack [] blkdev_issue_discard+0x232/0x2a0 [] blkdev_ioctl+0x61d/0x7d0 [] block_ioctl+0x41/0x50 [] do_vfs_ioctl+0x2e3/0x4d0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x Looking at the stack, looks like it's hanged on a discard operation root@ip-172-31-24-66:~# ps -flp 1693 F S UID PID PPID C
[Kernel-packages] [Bug 1841084] Re: bionic/linux-aws: 4.15.0-1047.49 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Packaging - phase-changed: Thursday, 22. August 2019 21:57 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 23. August 2019 09:33 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:building trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs -- 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/1841084 Title: bionic/linux-aws: 4.15.0-1047.49 -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-lrm 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 09:33 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:building trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1840945] Re: Concatenated lz4 initrds don't work
@xnox, thank you, in #3 I was testing date.img as a plain cpio without compression, while with your updated lz4/xz commands, it appears that when date.img matches the compression of initrd.img, then it works fine. So the problem only happens when mixed compressions are used. Btw, the reason I was trying that, is that in the new version of the "ltsp" netbooting package, we send all the netbooting code as an additional initrd. So if we can't use mixed compressions, we'll need to provide a different initrd for each image/chroot/vm/live-cd that the ltsp sysadmin will want to netboot. If the plans to default to lz4 initramfs are cancelled, then ltsp will work anywhere with a single initrd, from jessie and 16.04 to buster and hopefully 20.04. :) Otherwise... where should we hunt the bug? In the kernel decompression code, or in mkinitramfs? -- 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/1840945 Title: Concatenated lz4 initrds don't work Status in linux package in Ubuntu: Confirmed Bug description: Concatenating multiple initrds works fine with gzipped initrds. (microcode+gzip+gzip) => the kernel properly decompresses that With lz4, it can't decompress anything after the first lz4: (microcode+lz4+whatever) => it doesn't decompress whatever. To reproduce: Get vmlinuz and initrd.img from an eoan daily build and put them in a directory. Create an lz4 (or gzip or uncompressed cpio, it doesn't matter): # date > date.txt # echo date.txt | cpio -oH newc | lz4 > date.img Concatenate them: # cat initrd.img.original date.img > initrd.img Boot them: # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh Then inside kvm: # ls /date.txt The additional file doesn't exist. `dmesg | grep -i initramfs` reports: Trying to unpack rootfs image as initramfs... Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1841139] Re: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu.
try to run apport-collect 1841139, however "amixer -c1 info" hang, kill it with -9 won't work. Taipei office have access to the machine. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1841139 Title: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu. Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Bug description: Platform: dell 5420 / 5424 with AMD GPU. D-SUB or display port hot plug won't work in bionic with bionic kernel oem 4.15 -1048 and oem-osp1 5.0 -1016. It can be work around with amdgpu.runpm=0 kernel parameter, with the price of higher power consumption. As install bios 89.7.48 + Kernel: 4.15.0-1043-oem + amdgpu: amdgpu-pro-19.10-793418 The hotplug works. However, no DP audio (unless boot with DP plugged). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841139/+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 1841139] 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 1841139 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/1841139 Title: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu. Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Platform: dell 5420 / 5424 with AMD GPU. D-SUB or display port hot plug won't work in bionic with bionic kernel oem 4.15 -1048 and oem-osp1 5.0 -1016. It can be work around with amdgpu.runpm=0 kernel parameter, with the price of higher power consumption. As install bios 89.7.48 + Kernel: 4.15.0-1043-oem + amdgpu: amdgpu-pro-19.10-793418 The hotplug works. However, no DP audio (unless boot with DP plugged). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841139/+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 1841148] Re: Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver
"The connection works again if I revert to an older kernel." Can you please specify the version? -- 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/1841148 Title: Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-58-generic my ethernet connection fails to get a connection. The network connection constantly goes up and down. The issue has been reported by another user: https://bugzilla.kernel.org/show_bug.cgi?id=204591 Snippet from kern.log showing that the connection constantly goes up and down: Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134651] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134830] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134836] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134858] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134868] bridge-enp0s31f6: up Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134872] bridge-enp0s31f6: attached Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334794] userif-2: sent link down event. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334801] userif-2: sent link up event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.156471] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158580] bridge-enp0s31f6: down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158599] bridge-enp0s31f6: detached Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356790] userif-2: sent link down event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356795] userif-2: sent link up event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295365] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295729] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295741] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295785] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295804] bridge-enp0s31f6: up Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295810] bridge-enp0s31f6: attached Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495615] userif-2: sent link down event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495620] userif-2: sent link up event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316505] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316593] bridge-enp0s31f6: down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316607] bridge-enp0s31f6: detached Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516761] userif-2: sent link down event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516767] userif-2: sent link up event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.438729] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440433] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440439] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440466] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440475] bridge-enp0s31f6: up Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440479] bridge-enp0s31f6: attached Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638884] userif-2: sent link down event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638890] userif-2: sent link up event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.460451] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461881] bridge-enp0s31f6: down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461902] bridge-enp0s31f6: detached Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660746] userif-2: sent link down event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660752] userif-2: sent link up event. Aug 20 10:06:20 martijn-ThinkPad-P50 kernel: [ 2447.583182] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx inxi -i: Network: Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e lspci: 00:1f.6 Ethernet controller: Intel Corpor
[Kernel-packages] [Bug 1841139] Re: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu.
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc5/ -- 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/1841139 Title: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu. Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Platform: dell 5420 / 5424 with AMD GPU. D-SUB or display port hot plug won't work in bionic with bionic kernel oem 4.15 -1048 and oem-osp1 5.0 -1016. It can be work around with amdgpu.runpm=0 kernel parameter, with the price of higher power consumption. As install bios 89.7.48 + Kernel: 4.15.0-1043-oem + amdgpu: amdgpu-pro-19.10-793418 The hotplug works. However, no DP audio (unless boot with DP plugged). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841139/+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 1841148] Re: Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver
If I revert back to kernel 4.15.0-55-generic, the connection works again. -- 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/1841148 Title: Kernel 4.15.0-58 breaks Intel Ethernet Connection for I219-V and 82579V using e1000e driver Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-58-generic my ethernet connection fails to get a connection. The network connection constantly goes up and down. The issue has been reported by another user: https://bugzilla.kernel.org/show_bug.cgi?id=204591 Snippet from kern.log showing that the connection constantly goes up and down: Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134651] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134830] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134836] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134858] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134868] bridge-enp0s31f6: up Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.134872] bridge-enp0s31f6: attached Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334794] userif-2: sent link down event. Aug 20 10:06:00 martijn-ThinkPad-P50 kernel: [ 2427.334801] userif-2: sent link up event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.156471] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158580] bridge-enp0s31f6: down Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.158599] bridge-enp0s31f6: detached Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356790] userif-2: sent link down event. Aug 20 10:06:01 martijn-ThinkPad-P50 kernel: [ 2428.356795] userif-2: sent link up event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295365] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295729] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295741] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295785] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295804] bridge-enp0s31f6: up Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.295810] bridge-enp0s31f6: attached Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495615] userif-2: sent link down event. Aug 20 10:06:08 martijn-ThinkPad-P50 kernel: [ 2435.495620] userif-2: sent link up event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316505] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316593] bridge-enp0s31f6: down Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.316607] bridge-enp0s31f6: detached Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516761] userif-2: sent link down event. Aug 20 10:06:09 martijn-ThinkPad-P50 kernel: [ 2436.516767] userif-2: sent link up event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.438729] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440433] /dev/vmnet: open called by PID 5847 (vmnet-bridge) Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440439] /dev/vmnet: hub 0 does not exist, allocating memory. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440466] /dev/vmnet: port on hub 0 successfully opened Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440475] bridge-enp0s31f6: up Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.440479] bridge-enp0s31f6: attached Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638884] userif-2: sent link down event. Aug 20 10:06:14 martijn-ThinkPad-P50 kernel: [ 2441.638890] userif-2: sent link up event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.460451] bridge-enp0s31f6: disabling the bridge on dev down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461881] bridge-enp0s31f6: down Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.461902] bridge-enp0s31f6: detached Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660746] userif-2: sent link down event. Aug 20 10:06:15 martijn-ThinkPad-P50 kernel: [ 2442.660752] userif-2: sent link up event. Aug 20 10:06:20 martijn-ThinkPad-P50 kernel: [ 2447.583182] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx inxi -i: Network: Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e lspci: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connecti
[Kernel-packages] [Bug 1841139] Re: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu.
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Committed => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- 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/1841139 Title: monitor hotplug not working as external d-sub or display port connect amd gpu and internal lcd connect to intel gpu. Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Platform: dell 5420 / 5424 with AMD GPU. D-SUB or display port hot plug won't work in bionic with bionic kernel oem 4.15 -1048 and oem-osp1 5.0 -1016. It can be work around with amdgpu.runpm=0 kernel parameter, with the price of higher power consumption. As install bios 89.7.48 + Kernel: 4.15.0-1043-oem + amdgpu: amdgpu-pro-19.10-793418 The hotplug works. However, no DP audio (unless boot with DP plugged). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841139/+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 1828166] Re: perf top problem on z with Ubuntu 18.04
** Description changed: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" + + Disco needs also as prereq: + + * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix s390 + missing module symbol and warning for non-root users + [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. -- 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" Disco needs also as prereq: * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix s390 missing module symbol and warning for non-root users [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) a
[Kernel-packages] [Bug 1840934] Re: Change kernel compression method to improve boot speed
Should we match these defaults for initramfs too? At the moment I have switched to lz4 across the board, but maybe it does make sense to use lzo on s390x and gzip on armhf, etc. Should I escalate to IBM supporting lz4 on ppc64le? -- 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/1840934 Title: Change kernel compression method to improve boot speed Status in linux package in Ubuntu: Fix Committed Bug description: Colin King has done some analysis of kernel boot speed using different kernel compression methods. Results for x86 are at: https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/kernel-compression-method.txt https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/boot-speed-compression-5.3-rc4.ods Testing of s390 gave the following: GZIP31528972 LZ4 192348049 LZO 85990145 From Colin: "I used the monotonic TOD timer using the stckf opcode to fetch a 64 bit time value. Not sure how this maps to 'real time' in seconds." Conclusion: We should switch x86 to LZ4 and s390 to LZO. PPC and ARM do not support LZO or LZ4, so we will stick with gzip there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840934/+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 1828166] Re: perf top problem on z with Ubuntu 18.04
These patches have already been committed to Eoan (LP: #1841110). ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" Disco needs also as prereq: * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix s390 missing module symbol and warning for non-root users [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+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 1840906] Re: Firefox could not hear streaming Radiko
I post to Mozilla Forums, forum member answered ubuntu-restricted-extras need to Radiko streaming. thank you everyone. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840906 Title: Firefox could not hear streaming Radiko Status in firefox package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: dear everyone. this is not a bug, but may bug. I use ubuntu-18.04.3, and Firefox 68.0.2. In Japan radio streaming site named Radiko (http://radiko.jp), Firefox could not hear this. 1 or 2 years old, Firefox + Adobe Flash use could hear Radiko. But now Firefox do not support adobe Flash. Radiko site change to use adobe flash to HTML5, I expected to hear Radiko to use Firefox. but could not. few days ago, I install chrome(proprietory version), chrome could hear radiko streaming. what change to need my firefox to hear radkio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840906/+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 1840906] Re: Firefox could not hear streaming Radiko
Are you saying that you need to install ubuntu-restricted-extras in order to hear audio from Radiko or that additional codecs needs to be added to ubuntu-restricted-extras? -- 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/1840906 Title: Firefox could not hear streaming Radiko Status in firefox package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: dear everyone. this is not a bug, but may bug. I use ubuntu-18.04.3, and Firefox 68.0.2. In Japan radio streaming site named Radiko (http://radiko.jp), Firefox could not hear this. 1 or 2 years old, Firefox + Adobe Flash use could hear Radiko. But now Firefox do not support adobe Flash. Radiko site change to use adobe flash to HTML5, I expected to hear Radiko to use Firefox. but could not. few days ago, I install chrome(proprietory version), chrome could hear radiko streaming. what change to need my firefox to hear radkio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840906/+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 1840934] Re: Change kernel compression method to improve boot speed
I don't think Colin collected any data on initramfs compression, but I subscribed Colin to the bug so he can comment. -- 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/1840934 Title: Change kernel compression method to improve boot speed Status in linux package in Ubuntu: Fix Committed Bug description: Colin King has done some analysis of kernel boot speed using different kernel compression methods. Results for x86 are at: https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/kernel-compression-method.txt https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/boot-speed-compression-5.3-rc4.ods Testing of s390 gave the following: GZIP31528972 LZ4 192348049 LZO 85990145 From Colin: "I used the monotonic TOD timer using the stckf opcode to fetch a 64 bit time value. Not sure how this maps to 'real time' in seconds." Conclusion: We should switch x86 to LZ4 and s390 to LZO. PPC and ARM do not support LZO or LZ4, so we will stick with gzip there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840934/+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 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
--- Comment From hbath...@in.ibm.com 2019-08-23 07:42 EDT--- The issue is not seen anymore with 4.15.0-59.66~16.04.1 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0]
[Kernel-packages] [Bug 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 21. August 2019 11:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs -- 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/1840816 Title: disco/linux: 5.0.0-27.28 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 21. August 2019 11:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Thursday, 22. August 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Thursday, 22. August 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1828166] Re: perf top problem on z with Ubuntu 18.04
SRU request: https://lists.ubuntu.com/archives/kernel-team/2019-August/103323.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" Disco needs also as prereq: * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix s390 missing module symbol and warning for non-root users [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+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 1841065] Re: Updated to 5.0.0-25 and headphone still inverted
I assume you are asking me if I upgraded BIOS and answer is no. BIOS from Dmesg DMI: Insignia NS-P11W7100/Cherry Trail CR, BIOS BI-11.6-S116CJR100-CC34A-029-S 05/19/2017 Purchase History after BIOS date In Store Order Number xxx x x Aug 29, 2017 $179.99 Insignia™ - 11.6" - Tablet - 32GB - With Keyboard - Black Initial Ubuntu 18.04 install works. Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841065/+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 1841065] Re: Updated to 5.0.0-25 and headphone still inverted
apport information ** Tags added: apport-collected bionic ** Description changed: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: leetdavy 2579 F pulseaudio + /dev/snd/controlC0: leetdavy 2579 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-05-18 (96 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + MachineType: Insignia NS-P11W7100 + 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-15-generic N/A + linux-backports-modules-4.18.0-15-generic N/A + linux-firmware 1.173.6 + Tags: bionic + Uname: Linux 4.18.0-15-generic x86_
[Kernel-packages] [Bug 1841065] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284184/+files/ProcCpuinfo.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc96
[Kernel-packages] [Bug 1841065] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284187/+files/ProcModules.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc96
[Kernel-packages] [Bug 1841065] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284179/+files/CRDA.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c ro quiet s
[Kernel-packages] [Bug 1841065] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284186/+files/ProcInterrupts.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d
[Kernel-packages] [Bug 1841065] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284189/+files/RfKill.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c ro qui
[Kernel-packages] [Bug 1841065] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284182/+files/Lspci.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c ro quiet
[Kernel-packages] [Bug 1841065] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284188/+files/PulseList.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c
[Kernel-packages] [Bug 1841065] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284185/+files/ProcCpuinfoMinimal.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7
[Kernel-packages] [Bug 1841065] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284181/+files/IwConfig.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c r
[Kernel-packages] [Bug 1841065] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284191/+files/WifiSyslog.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e
[Kernel-packages] [Bug 1841065] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284183/+files/Lsusb.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c ro quiet
[Kernel-packages] [Bug 1841065] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284190/+files/UdevDb.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc968e0c ro qui
[Kernel-packages] [Bug 1841065] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1841065/+attachment/5284180/+files/CurrentDmesg.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 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=/boot/vmlinuz-4.18.0-15-generic root=UUID=a772ab3c-6930-43b7-9507-9d53dc
[Kernel-packages] [Bug 1841065] Re: Updated to 5.0.0-25 and headphone still inverted
End of Apport files from previous working version tested today to confirm using Rythmbox with Pulse ogg audio and both internal and headphone worked simultaneously so assume the automatic switch introduced the current error. Rebooting back to Ubuntu 19.04 and 5.0.0-25 kernel with headphone error unresolved. -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= L
[Kernel-packages] [Bug 1841065] Re: Updated to 5.0.0-25 and headphone still inverted
I am sensing the issue is recognizing the DMI to be able to switch headphone when needed. So here is the DMIDecode output while running 18.04 kernel 4.18.0-15 I also have it captured while running 19.04 kernel 5.0.0-25 if needed ** Attachment added: "DMIDecode from 18.04 kernel 4.18.0-15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841065/+attachment/5284193/+files/DMIdecode_18.04.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 Package: linux (not inst
[Kernel-packages] [Bug 1841065] Re: Updated to 5.0.0-25 and headphone still inverted
I am sensing the issue is recognizing the DMI to be able to switch headphone when needed. So here is the DMIDecode output while running 18.04 kernel 4.18.0-15 I also have it captured while running 19.04 kernel 5.0.0-25 if needed ** Attachment added: "DMIDecode from 18.04 kernel 4.18.0-15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841065/+attachment/5284194/+files/DMIdecode_18.04.txt -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 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 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leetdavy 2579 F pulseaudio /dev/snd/controlC0: leetdavy 2579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-18 (96 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Insignia NS-P11W7100 Package: linux (not inst
[Kernel-packages] [Bug 1840934] Re: Change kernel compression method to improve boot speed
@Dimitri, so you set the defaults w/o any benchmarking stats? I'll see if I can get some time to check what the sane options are per- arch. Colin -- 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/1840934 Title: Change kernel compression method to improve boot speed Status in linux package in Ubuntu: Fix Committed Bug description: Colin King has done some analysis of kernel boot speed using different kernel compression methods. Results for x86 are at: https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/kernel-compression-method.txt https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/boot-speed-compression-5.3-rc4.ods Testing of s390 gave the following: GZIP31528972 LZ4 192348049 LZO 85990145 From Colin: "I used the monotonic TOD timer using the stckf opcode to fetch a 64 bit time value. Not sure how this maps to 'real time' in seconds." Conclusion: We should switch x86 to LZ4 and s390 to LZO. PPC and ARM do not support LZO or LZ4, so we will stick with gzip there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840934/+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 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840802 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Thursday, 22. August 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840802 variant: debs -- 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/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -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: 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: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840802 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Thursday, 22. August 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Thursday, 22. August 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1840808 Title: disco/linux-gcp: 5.0.0-1015.15 -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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Thursday, 22. August 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- 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/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83] (EE) 9: /usr/lib/xorg/Xorg (0x55a9687bf000+0x581a6) [0x55a9688171a6] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fe8160e1830] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55a968801329] (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
Overnight testing of the revised deployment configuration has no errors, 200 runs completed. -- 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: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ 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 successfu
[Kernel-packages] [Bug 1841159] Re: eoan/linux: 5.2.0-14.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- + packages: + lrm: linux-restricted-modules + main: linux + meta: linux-meta + signed: linux-signed + phase: Packaging + phase-changed: Friday, 23. August 2019 14:34 UTC + reason: + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded + trackers: + bionic/linux-hwe-edge: bug 1841158 variant: debs -- 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/1841159 Title: eoan/linux: 5.2.0-14.15 -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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Friday, 23. August 2019 14:34 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1841084] Re: bionic/linux-aws: 4.15.0-1047.49 -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 will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Holding before Promote to Proposed - phase-changed: Friday, 23. August 2019 09:33 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 23. August 2019 14:31 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:building + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs -- 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/1841084 Title: bionic/linux-aws: 4.15.0-1047.49 -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-lrm 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Ready for Promote to Proposed phase-changed: Friday, 23. August 2019 14:31 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1841147] Re: eoan/linux: -proposed tracker
*** This bug is a duplicate of bug 1841159 *** https://bugs.launchpad.net/bugs/1841159 ** Summary changed: - linux: -proposed tracker + eoan/linux: -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/1841147 Title: eoan/linux: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841147/+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 1840800] Re: disco/linux-aws: 5.0.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws - phase: Packaging - phase-changed: Thursday, 22. August 2019 17:22 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 23. August 2019 14:41 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-aws-edge: bug 1840820 variant: debs -- 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/1840800 Title: disco/linux-aws: 5.0.0-1014.16 -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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 14:41 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-aws-edge: bug 1840820 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840800/+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 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 15:15 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs -- 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/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -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-lrm 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 15:15 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1841159] Re: eoan/linux: 5.2.0-14.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Friday, 23. August 2019 14:34 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 23. August 2019 15:43 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:depwait,signed:depwait trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs -- 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/1841159 Title: eoan/linux: 5.2.0-14.15 -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: 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-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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:depwait,signed:depwait trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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
I'm having the same bug in Kubuntu 19.04.03 Kernel 5.0.0-25-generic This bug must be opened again -- 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: New 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.produ
[Kernel-packages] [Bug 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 15:15 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs -- 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/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -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-lrm 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 15:15 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1840806] Re: bionic/linux-gcp: 5.0.0-1015.15~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 13:26 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- packages are in the wrong component + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1840806 Title: bionic/linux-gcp: 5.0.0-1015.15~18.04.1 -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-lrm 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: Incomplete 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 13:26 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840806/+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 1833617] Re: [amdgpu] screen freeze after suspend
The problem still persists. The attached in the latest copy of the Journal thanks On Friday, August 16, 2019, 6:20:43 AM PDT, Kai-Heng Feng wrote: Please test latest mainline kernel again: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc4/ And attach `journalctl -b -1 -k` once the issue happens. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions ** Attachment added: "=?UTF-8?b?Sm91cm5hbF8yM0F1ZzE5?=" https://bugs.launchpad.net/bugs/1833617/+attachment/5284230/+files/%3D%3FUTF-8%3Fb%3FSm91cm5hbF8yM0F1ZzE5%3F%3D -- 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/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.prod
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Ok, can confirm that disabling upower (via the commands in comment #44) does not help. I suffered another disconnection when the uptime was close to 4 hours. -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
** Also affects: linux-kernel-headers (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-kernel-headers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux-kernel-headers package in Ubuntu: Confirmed 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.
[Kernel-packages] [Bug 1840934] Re: Change kernel compression method to improve boot speed
@Dimitri, Seems that for initramfs lz4 makes a lot of sense, see: https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/boot-speed- initramfs-decompression-eoan.ods The load times for LZ4 is slower than the previous default, however, the decompression time makes up for this unless one is booting off really slow media sub-5400 RPM HDD such as slow flash. So, the LZ4 default looks sane to me, lets see how it works out for Eaon. -- 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/1840934 Title: Change kernel compression method to improve boot speed Status in linux package in Ubuntu: Fix Committed Bug description: Colin King has done some analysis of kernel boot speed using different kernel compression methods. Results for x86 are at: https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/kernel-compression-method.txt https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/boot-speed-compression-5.3-rc4.ods Testing of s390 gave the following: GZIP31528972 LZ4 192348049 LZO 85990145 From Colin: "I used the monotonic TOD timer using the stckf opcode to fetch a 64 bit time value. Not sure how this maps to 'real time' in seconds." Conclusion: We should switch x86 to LZ4 and s390 to LZO. PPC and ARM do not support LZO or LZ4, so we will stick with gzip there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840934/+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 1841244] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
Public bug reported: I just got this error right after I booted up my laptop, but I can still access the stuff normally. Main reason why I reported it is because I don't want someone less tech- inclined to see this and panic. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Aug 13 22:27:57 2019 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-08-14 (9 days ago) InstallationMedia: Unity 19.10 2019.04.26 amd64 "Custom Eoan EANIMAL" (20190426) Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu1 apt 1.9.3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1841244 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: I just got this error right after I booted up my laptop, but I can still access the stuff normally. Main reason why I reported it is because I don't want someone less tech-inclined to see this and panic. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Aug 13 22:27:57 2019 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-08-14 (9 days ago) InstallationMedia: Unity 19.10 2019.04.26 amd64 "Custom Eoan EANIMAL" (20190426) Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu1 apt 1.9.3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1841244/+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 1841256] [NEW] package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384
Public bug reported: obtained after running sudo apt-get install -f ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-384 384.130-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri Aug 23 10:14:30 2019 DuplicateSignature: package:nvidia-384:384.130-0ubuntu0.14.04.2:conflicting packages - not installing nvidia-384 ErrorMessage: conflicting packages - not installing nvidia-384 InstallationDate: Installed on 2015-01-26 (1670 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: nvidia-graphics-drivers-384 Title: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1841256 Title: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384 Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: obtained after running sudo apt-get install -f ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-384 384.130-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri Aug 23 10:14:30 2019 DuplicateSignature: package:nvidia-384:384.130-0ubuntu0.14.04.2:conflicting packages - not installing nvidia-384 ErrorMessage: conflicting packages - not installing nvidia-384 InstallationDate: Installed on 2015-01-26 (1670 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: nvidia-graphics-drivers-384 Title: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384 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-384/+bug/1841256/+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 1841256] Re: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1841256 Title: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384 Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: obtained after running sudo apt-get install -f ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-384 384.130-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri Aug 23 10:14:30 2019 DuplicateSignature: package:nvidia-384:384.130-0ubuntu0.14.04.2:conflicting packages - not installing nvidia-384 ErrorMessage: conflicting packages - not installing nvidia-384 InstallationDate: Installed on 2015-01-26 (1670 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: nvidia-graphics-drivers-384 Title: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384 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-384/+bug/1841256/+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 1840800] Re: disco/linux-aws: 5.0.0-1014.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 14:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: bionic/linux-aws-edge: bug 1840820 variant: debs -- 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/1840800 Title: disco/linux-aws: 5.0.0-1014.16 -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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 14:41 UTC reason: promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: bionic/linux-aws-edge: bug 1840820 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840800/+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 1841264] [NEW] crypto/testmgr.o fails to build due to struct cipher_testvec not having data members: ctext, ptext, len
Public bug reported: [Impact] Ubuntu commit aae817ffb114 "crypto: testmgr - add AES-CFB tests" added new test cases to the crypto self-tests. This patch is referring to structure members that don't exist in Bionic because the large mainline clean up patch 92a4c9fef34c crypto: "testmgr - eliminate redundant decryption test vectors" has not been backported. As a result, Bionic will fail to build if the crypto self tests are enabled in the kernel config. This build failure was noticed when building a derivative kernel. This mainline patch is a massive refactoring, complete with the updated structure definitions that will resolve the build failure: 92a4c9fef34c "crypto: testmgr - eliminate redundant decryption test vectors" Furthermore, once the pre-requisite patch is backported, the CFB module also needs to be backported as the new tests added by Ubuntu commit aae817ffb114 "crypto: testmgr - add AES-CFB tests" will attempt to load that module at runtime to execute its tests. The primary argument for the inclusion of this backport would be that we would not have to amend future crypto test case additions as they come in via stable update sync to use the "older" code structure. [Test Case] On a Bionic kernel, ensure "CONFIG_CRYPTO_MANAGER_DISABLE_TESTS" is NOT set and ensure you have the patch in your tree (master-next should have it as of this writing it has not been reverted). To disable that config option, edit debian.master/config/config.common.ubuntu and delete the line that reads "CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y" then update the configs with "fakeroot debian/rules updateconfigs" Build the kernel. Expected result: crypto/testmgr.o is built successfully and so is the rest of the kernel for your build. Actual result: crypto/testmgr.o fails to build with several errors related to data members of a structure that don't exist yet. Like this: /tmp/kernel-connork-cb14cb8-q7j8/build/crypto/testmgr.h:16148:4: error: 'const struct cipher_testvec' has no member named 'ptext' .ptext = "\x6b\xc1\xbe\xe2\x2e\x40\x9f\x96" ^ /tmp/kernel-connork-cb14cb8-q7j8/build/crypto/testmgr.h:16156:4: error: 'const struct cipher_testvec' has no member named 'ctext' .ctext = "\x3b\x3f\xd9\x2e\xb7\x2d\xad\x20" ^ /tmp/kernel-connork-cb14cb8-q7j8/build/crypto/testmgr.h:16164:4: error: 'const struct cipher_testvec' has no member named 'len'; did you mean 'klen'? .len = 64, [Testing] After backporting the pre-requisite refactor patch and the CFB module that the new tests depend on, I compiled and booted into the kernel and ran the Crypto test suite by loading the "tcrypt" module. I compared the test suite results with a Bionic kernel that does NOT have this backport and confirmed they both emitted the same test results from the crypto self tests: [ 15.536400] alg: hash: Failed to load transform for hmac(crc32): -2 [ 15.552214] alg: cprng: Failed to load transform for ansi_cprng: -2 [ 15.590773] tcrypt: one or more tests failed! No new test failures have been added as a result of this backport. [Regression Potential] There is a chance for breakage within the test suite because the primary patch that resolves this build failure, 92a4c9fef34c "crypto: testmgr - eliminate redundant decryption test vectors" is not practical to review. However, this backport was accomplished with the very same awk script supplied by the original patch author and the results between one kernel and a modified kernel are consistent. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Connor Kuehl (connork) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Connor Kuehl (connork) -- 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/1841264 Title: crypto/testmgr.o fails to build due to struct cipher_testvec not having data members: ctext, ptext, len Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] Ubuntu commit aae817ffb114 "crypto: testmgr - add AES-CFB tests" added new test cases to the crypto self-tests. This patch is referring to structure members that don't exist in Bionic because the large mainline clean up patch 92a4c9fef34c crypto: "testmgr - eliminate redundant decryption test vectors" has not been backported. As a result, Bionic will fail to build if the crypto self tests are enabled in the kernel config. This build failure was noticed when building a derivative
[Kernel-packages] [Bug 1841264] Re: crypto/testmgr.o fails to build due to struct cipher_testvec not having data members: ctext, ptext, len
** Description changed: [Impact] Ubuntu commit aae817ffb114 "crypto: testmgr - add AES-CFB tests" added new test cases to the crypto self-tests. This patch is referring to structure members that don't exist in Bionic because the large mainline clean up patch 92a4c9fef34c crypto: "testmgr - eliminate redundant decryption test vectors" has not been backported. As a result, Bionic will fail to build if the crypto self tests are enabled in the kernel config. This build failure was noticed when building a derivative kernel. This mainline patch is a massive refactoring, complete with the updated structure definitions that will resolve the build failure: 92a4c9fef34c "crypto: testmgr - eliminate redundant decryption test vectors" Furthermore, once the pre-requisite patch is backported, the CFB module also needs to be backported as the new tests added by Ubuntu commit aae817ffb114 "crypto: testmgr - add AES-CFB tests" will attempt to load that module at runtime to execute its tests. + The primary argument for the inclusion of this backport would be that we + would not have to amend future crypto test case additions as they come + in via stable update sync to use the "older" code structure. + [Test Case] On a Bionic kernel, ensure "CONFIG_CRYPTO_MANAGER_DISABLE_TESTS" is NOT set and ensure you have the patch in your tree (master-next should have it as of this writing it has not been reverted). To disable that config option, edit debian.master/config/config.common.ubuntu and delete the line that reads "CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y" then update the configs with "fakeroot debian/rules updateconfigs" Build the kernel. Expected result: crypto/testmgr.o is built successfully and so is the rest of the kernel for your build. Actual result: crypto/testmgr.o fails to build with several errors related to data members of a structure that don't exist yet. Like this: /tmp/kernel-connork-cb14cb8-q7j8/build/crypto/testmgr.h:16148:4: error: 'const struct cipher_testvec' has no member named 'ptext' -.ptext = "\x6b\xc1\xbe\xe2\x2e\x40\x9f\x96" - ^ + .ptext = "\x6b\xc1\xbe\xe2\x2e\x40\x9f\x96" + ^ /tmp/kernel-connork-cb14cb8-q7j8/build/crypto/testmgr.h:16156:4: error: 'const struct cipher_testvec' has no member named 'ctext' -.ctext = "\x3b\x3f\xd9\x2e\xb7\x2d\xad\x20" - ^ + .ctext = "\x3b\x3f\xd9\x2e\xb7\x2d\xad\x20" + ^ /tmp/kernel-connork-cb14cb8-q7j8/build/crypto/testmgr.h:16164:4: error: 'const struct cipher_testvec' has no member named 'len'; did you mean 'klen'? -.len = 64, + .len = 64, [Testing] After backporting the pre-requisite refactor patch and the CFB module that the new tests depend on, I compiled and booted into the kernel and ran the Crypto test suite by loading the "tcrypt" module. I compared the test suite results with a Bionic kernel that does NOT have this backport and confirmed they both emitted the same test results from the crypto self tests: [ 15.536400] alg: hash: Failed to load transform for hmac(crc32): -2 [ 15.552214] alg: cprng: Failed to load transform for ansi_cprng: -2 [ 15.590773] tcrypt: one or more tests failed! No new test failures have been added as a result of this backport. [Regression Potential] There is a chance for breakage within the test suite because the primary patch that resolves this build failure, 92a4c9fef34c "crypto: testmgr - eliminate redundant decryption test vectors" is not practical to review. However, this backport was accomplished with the very same awk script supplied by the original patch author and the results between one kernel and a modified kernel are consistent. -- 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/1841264 Title: crypto/testmgr.o fails to build due to struct cipher_testvec not having data members: ctext, ptext, len Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] Ubuntu commit aae817ffb114 "crypto: testmgr - add AES-CFB tests" added new test cases to the crypto self-tests. This patch is referring to structure members that don't exist in Bionic because the large mainline clean up patch 92a4c9fef34c crypto: "testmgr - eliminate redundant decryption test vectors" has not been backported. As a result, Bionic will fail to build if the crypto self tests are enabled in the kernel config. This build failure was noticed when building a derivative kernel. This mainline patch is a massive refactoring, complete with the updated structure definitions that will resolve the build failure: 92a4c9fef34c "crypto: testmgr - eliminate redundant decryption test vectors" Furthermore, once the pre-requisite patch is backported, th
[Kernel-packages] [Bug 1840806] Re: bionic/linux-gcp: 5.0.0-1015.15~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Thursday, 22. August 2019 13:26 UTC + phase: Testing + phase-changed: Friday, 23. August 2019 18:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1840806 Title: bionic/linux-gcp: 5.0.0-1015.15~18.04.1 -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-lrm 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: 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 23. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840806/+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 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -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/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Thursday, 22. August 2019 15:15 UTC + phase: Testing + phase-changed: Friday, 23. August 2019 18:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs -- 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/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: 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: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 23. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
This is not a kernel bug. $ lspci lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory It's because the the correct address is 1:00:03.0 instead of :00:03.0: $ ls /sys/bus/pci/devices/1\:00\:03.0/resource /sys/bus/pci/devices/1:00:03.0/resource So we need userspace libraries to support 32 bit domain to support the hardware. ** Bug watch added: freedesktop.org Bugzilla #101744 https://bugs.freedesktop.org/show_bug.cgi?id=101744 -- 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/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: New Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: New Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpc
[Kernel-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
For pciutils (lspci), we need this commit: commit ab61451d47514c473953a24aa4f4f816b77ade56 Author: Keith Busch Date: Thu Mar 17 13:19:17 2016 -0600 pciutils: Add support for 32-bit PCI domains This adds support for new host bridges that may create PCI domain number values requiring more than 16 bits. The new domain 32-bit integer is signed to allow -1 for "any", and is sufficient as the domain number will never require the full 32-bits. The domain field is appended at the end of struct pci_dev, and the current location of the 16-bit domain remains for compatibility. The domain number is truncated and copied into the legacy domain location so existing applications linking to the library will continue to work without modification. We accept that these applications may not work correctly on machines with host bridges exporting 32-bit domains. In order to force new programs to link to the new ABI, the pci_init function call is versioned in this commit. Signed-off-by: Keith Busch For libpciaccess (which is used by Xorg), we need this commit: commit a167bd6474522a709ff3cbb00476c0e4309cb66f Author: Stephen Hemminger Date: Mon Sep 18 13:17:23 2017 -0400 linux: support 32 bit PCI domains (v3) The PCI domain may be larger than 16 bits on Microsoft Azure and other virtual environments. PCI busses reported by ACPI are limited to 16 bits, but in Azure the domain value for pass through devices is intentionally larger than 16 bits to avoid clashing with local devices. This is needed to support pass through of GPU devices. v3: (ajax) Update FreeBSD and Solaris backends to preserve the full 32-bit domain number, since on those OSes it stands a chance of working already. Update NetBSD and OpenBSD backends to initialize domain_16 compatibly with older libpciaccess; neither backend appears to support more than a handful of domains to begin with though. Trivially update the generic x86 backend for source compatibility, though it still only supports one domain and will never be better. Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=101744 Signed-off-by: Stephen Hemminger Reviewed-by: Eric Anholt -- 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/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: New Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: New Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVI
[Kernel-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
However, for both libraries the new commits introduce ABI change, so all packages linked against libpciaccess and libpci need to be rebuilt. So I am not sure how feasible it is. I'll just let the package maintainer decide. ** Also affects: pciutils (Ubuntu) Importance: Undecided Status: New ** Also affects: libpciaccess (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: libpciaccess (Ubuntu) Status: New => Invalid ** Changed in: libpciaccess (Ubuntu) Status: Invalid => New ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Also affects: pciutils (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libpciaccess (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: nvidia-graphics-drivers (Ubuntu Xenial) Status: New => Invalid ** Changed in: pciutils (Ubuntu) Status: New => Fix Released ** Changed in: libpciaccess (Ubuntu) Status: New => 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/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: New Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: New Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporti
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
Ricci, I guess yours is LP: #1841040? Let's discuss the issue on LP: #1841040 instead. -- 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: New Status in linux package in Ubuntu: Fix Released Status in linux-kernel-headers package in Ubuntu: Confirmed 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:cvnToBeFi
[Kernel-packages] [Bug 1841086] Re: bionic/linux: 4.15.0-60.67 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Friday, 23. August 2019 06:56 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs -- 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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-lrm 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Friday, 23. August 2019 06:56 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1841028] Re: R8169 speed decreases
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc5/ Mainline kernel disables r8169's ASPM, so it may help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841028 Title: R8169 speed decreases Status in linux package in Ubuntu: Invalid Bug description: uname -a Linux linux 4.15.0-59-generic 04:00.0 Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10) 06:00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Speed (esp upstream) decreases after short time. Temporary solved simply by ifdown eth0 & ifup eth0 Kernel driver currently in use 18.04.3 LTS is currenty not offering newer 4.17+ Any other suggestions ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841028/+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 1841159] Re: eoan/linux: 5.2.0-14.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:failed,signed:depwait trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs -- 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/1841159 Title: eoan/linux: 5.2.0-14.15 -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: 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-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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:failed,signed:depwait trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
Is it possible to disable secure boot and git mainline kernel a try? -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 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.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-12
[Kernel-packages] [Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
Affects me to. Also HP Spectre x360. Kernel 5.2.9-050209. -- 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/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) [Fix] Let HID core allow longer input report length. [Test] User confirmed the fix works. [Regression Potential] Low. Longer input report length is now considered valid, shorter input report length doesn't get touched. === Original Bug Report === Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker
** Summary changed: - eoan/linux: 5.2.0-14.15 -proposed tracker + eoan/linux: 5.2.0-15.16 -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/1841159 Title: eoan/linux: 5.2.0-15.16 -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: 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-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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1840906] Re: Firefox could not hear streaming Radiko
Dear Paul. I do not install ubuntu-restricted-extras. forums.MozillaZine.jp member answered that ubuntu-restricted-extras installed, resolved Radiko streaming hear. I think it is patent issue, and could not resovle easy for Firefox in ubuntu package. But proprietary version Firefox for Linux include ubuntu, video/mp4 example codecs="mp4a.40.5" include Firefox package. it is as same as Chrome. == 2019-08-23 (金) の 11:37 + に Paul White さんは書きました: > Are you saying that you need to install ubuntu-restricted-extras in > order to hear audio from Radiko or that additional codecs needs to be > added to ubuntu-restricted-extras? > -- 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/1840906 Title: Firefox could not hear streaming Radiko Status in firefox package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: dear everyone. this is not a bug, but may bug. I use ubuntu-18.04.3, and Firefox 68.0.2. In Japan radio streaming site named Radiko (http://radiko.jp), Firefox could not hear this. 1 or 2 years old, Firefox + Adobe Flash use could hear Radiko. But now Firefox do not support adobe Flash. Radiko site change to use adobe flash to HTML5, I expected to hear Radiko to use Firefox. but could not. few days ago, I install chrome(proprietory version), chrome could hear radiko streaming. what change to need my firefox to hear radkio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840906/+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 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC - reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:failed,meta:failed,signed:depwait trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs -- 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/1841159 Title: eoan/linux: 5.2.0-15.16 -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: 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-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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1841256] Re: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: inaccessible-archive ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1841256 Title: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384 Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Bug description: obtained after running sudo apt-get install -f ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-384 384.130-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri Aug 23 10:14:30 2019 DuplicateSignature: package:nvidia-384:384.130-0ubuntu0.14.04.2:conflicting packages - not installing nvidia-384 ErrorMessage: conflicting packages - not installing nvidia-384 InstallationDate: Installed on 2015-01-26 (1670 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: nvidia-graphics-drivers-384 Title: package nvidia-384 384.130-0ubuntu0.14.04.2 failed to install/upgrade: conflicting packages - not installing nvidia-384 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-384/+bug/1841256/+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 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
** Tags added: sts -- 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/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+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 1841159] Re: eoan/linux: 5.2.0-15.16 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC + reason: + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs -- 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/1841159 Title: eoan/linux: 5.2.0-15.16 -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: 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-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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 23. August 2019 15:43 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait trackers: bionic/linux-hwe-edge: bug 1841158 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841159/+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 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
Spent some time debugging this and I found some interesting bits. I was able to reproduce this by deploying a xenial-queens environment with VXLAN and the OVS firewall. Investigating this, here is what I found: 1) This module is first loaded on the compute nodes when libvirt-bin is installed. This package's postinst script creates the default libvirt network, so when libvirt service is enabled it will create some rules on iptables for this network, which will load the nf_conntrack_ipv4 module. 2) At some point during the configuration of the environment, this default network is destroyed (I'm still investigating who is doing this, but makes sense since nova/neutron won't use the default libvirt network), so those iptables rules won't be added anymore on libvirt service startup, so what was previously loading the module, won't do it. 3) Neutron relies on conntrack for the OVS firewall to work. It's on the documentation: https://docs.openstack.org/newton/networking-guide /config-ovsfwdriver.html 4) As pointed on the bug description, OVS complains whenever the module is not loaded, so we can assume that it's not its responsibility to load it. In my opinion this is something that neutron-ovs-agent should be loading, since the OVS firewall requires conntrack to work and OVS complains that it is not loaded. It would be interesting to see how (if) this works on different openstack deployments. -- 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/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
I confirm that the problem persists with kernel 5.2.9 on HP Spectre x360. I am using kernel 5.1.9, which has no problem. In addition, kernel 5.1.9 with linux-firmware-20190815.07b925b-1 has a problem with iwlwifi, so I had also to downgrade it to linux- firmware-20190618.acb56f2-1 -- 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/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) [Fix] Let HID core allow longer input report length. [Test] User confirmed the fix works. [Regression Potential] Low. Longer input report length is now considered valid, shorter input report length doesn't get touched. === Original Bug Report === Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -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) => Andy Whitcroft (apw) -- 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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-lrm 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Friday, 23. August 2019 06:56 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1841084] Re: bionic/linux-aws: 4.15.0-1047.49 -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) => Andy Whitcroft (apw) -- 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/1841084 Title: bionic/linux-aws: 4.15.0-1047.49 -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-lrm 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Friday, 23. August 2019 21:24 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Promote to Proposed - phase-changed: Friday, 23. August 2019 06:56 UTC + phase: Promote to Proposed + phase-changed: Friday, 23. August 2019 21:21 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs -- 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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-lrm 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Friday, 23. August 2019 21:21 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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
