[Kernel-packages] [Bug 1834942] Re: linux-oracle: 4.15.0-1018.20~16.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 -- swm properties -- kernel-stable-master-bug: 1834943 phase: Holding before Promote to Proposed phase-changed: Thursday, 04. July 2019 04:10 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,meta:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834942 Title: linux-oracle: 4.15.0-1018.20~16.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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New 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: 1834943 phase: Holding before Promote to Proposed phase-changed: Thursday, 04. July 2019 04:10 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834942/+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 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan
See the attached log showing a successful build of glibc from bionic on the launchpad staging build farm running the proposed kernel (4.4.0-155). ** Attachment added: "buildlog_ubuntu-bionic-i386.glibc_2.27-3ubuntu1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+attachment/5275017/+files/buildlog_ubuntu-bionic-i386.glibc_2.27-3ubuntu1_BUILDING.txt.gz ** 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/1834315 Title: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] As reported in #1833067 and https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some glibc testcases are still regressing on i386 after applying both the following commits: commit 379d98ddf41344273d9718556f761420f4dc80b3 Author: Alistair Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+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 1834894] Re: linux-snapdragon: 5.0.0-1017.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** 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: 1834902 - phase: Packaging - phase-changed: Thursday, 04. July 2019 04:04 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 04. July 2019 05:04 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 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834894 Title: linux-snapdragon: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New 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: 1834902 phase: Holding before Promote to Proposed phase-changed: Thursday, 04. July 2019 05:04 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+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 1835357] 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 1835357
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
** Changed in: linux (Ubuntu Bionic)
Status: New => Incomplete
--
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/1835357
Title:
Backport ACPI module-level code functionality
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-oem source package in Bionic:
New
Bug description:
[Impact]
After S3, DVD-ROM on HP ZBook 17 G5 stops working.
[Fix]
In the past we use dmi_match to set acpi_gbl_parse_table_as_term_list,
so the ACPI core can parse an entire ACPI table as a method.
Unfotunately this workaround doesn't work for the system in question.
So fully backport commit 5a8361f7ecce ("ACPICA: Integrate package
handling with module-level code") and subsequent fix commits, to solve
the issue.
[Test]
After applying the fix, DVD-ROM keeps working after S3.
[Regression Potential]
Medium. I've test several systems and I don't see anything break.
But if we want to be safe, we can merge this into Bionic after we are
sure there's no regression on OEM-B.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1835357/+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 1835357] Re: Backport ACPI module-level code functionality
** Tags added: oem-priority originate-from-1834574 stella
--
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/1835357
Title:
Backport ACPI module-level code functionality
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-oem source package in Bionic:
New
Bug description:
[Impact]
After S3, DVD-ROM on HP ZBook 17 G5 stops working.
[Fix]
In the past we use dmi_match to set acpi_gbl_parse_table_as_term_list,
so the ACPI core can parse an entire ACPI table as a method.
Unfotunately this workaround doesn't work for the system in question.
So fully backport commit 5a8361f7ecce ("ACPICA: Integrate package
handling with module-level code") and subsequent fix commits, to solve
the issue.
[Test]
After applying the fix, DVD-ROM keeps working after S3.
[Regression Potential]
Medium. I've test several systems and I don't see anything break.
But if we want to be safe, we can merge this into Bionic after we are
sure there's no regression on OEM-B.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1835357/+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 1835357] [NEW] Backport ACPI module-level code functionality
Public bug reported:
[Impact]
After S3, DVD-ROM on HP ZBook 17 G5 stops working.
[Fix]
In the past we use dmi_match to set acpi_gbl_parse_table_as_term_list,
so the ACPI core can parse an entire ACPI table as a method.
Unfotunately this workaround doesn't work for the system in question.
So fully backport commit 5a8361f7ecce ("ACPICA: Integrate package
handling with module-level code") and subsequent fix commits, to solve
the issue.
[Test]
After applying the fix, DVD-ROM keeps working after S3.
[Regression Potential]
Medium. I've test several systems and I don't see anything break.
But if we want to be safe, we can merge this into Bionic after we are
sure there's no regression on OEM-B.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: linux-oem (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Bionic)
Importance: Undecided
Status: 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/1835357
Title:
Backport ACPI module-level code functionality
Status in linux package in Ubuntu:
New
Status in linux-oem package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in linux-oem source package in Bionic:
New
Bug description:
[Impact]
After S3, DVD-ROM on HP ZBook 17 G5 stops working.
[Fix]
In the past we use dmi_match to set acpi_gbl_parse_table_as_term_list,
so the ACPI core can parse an entire ACPI table as a method.
Unfotunately this workaround doesn't work for the system in question.
So fully backport commit 5a8361f7ecce ("ACPICA: Integrate package
handling with module-level code") and subsequent fix commits, to solve
the issue.
[Test]
After applying the fix, DVD-ROM keeps working after S3.
[Regression Potential]
Medium. I've test several systems and I don't see anything break.
But if we want to be safe, we can merge this into Bionic after we are
sure there's no regression on OEM-B.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835357/+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 1834942] Re: linux-oracle: 4.15.0-1018.20~16.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 -- swm properties -- kernel-stable-master-bug: 1834943 phase: Holding before Promote to Proposed phase-changed: Thursday, 04. July 2019 04:10 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,meta:building,main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834942 Title: linux-oracle: 4.15.0-1018.20~16.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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New 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: 1834943 phase: Holding before Promote to Proposed phase-changed: Thursday, 04. July 2019 04:10 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,meta:building,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834942/+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 1776563]
cc suravee.suthikulpa...@amd.com, who works on the amd iommu driver. Maybe he can provide some help for this issue. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1829992] Re: zram02 from kernel_misc test suite in LTP failed
This is probably caused by the unsuccessful zram01 test, which will create 4 devices. ** No longer affects: linux (Ubuntu Cosmic) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829992 Title: zram02 from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: startup='Wed May 22 07:02:20 2019' zram02 1 TINFO: create '1' zram device(s) zram02 1 TFAIL: unexpected num of devices: 4 zram02 2 TINFO: zram cleanup tag=zram02 stime=1558508540 dur=0 exit=exited stat=1 core=no cu=1 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 06:28 seq crw-rw 1 root audio 116, 33 May 22 06:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 07:52:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829992/+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 1833319] Re: Performance degradation when copying from LVM snapshot backed by NVMe disk
I enabled enabled -proposed and installed 4.4.0-155.182, and went through the test case on a c5.large instance on aws. Note, I used the -generic kernel since -aws doesn't seem to be ready yet. The problem is solved and performance is the same as non-snapshot mounted disks. We can see that merging has been enabled by looking at the flag: $ cat /sys/block/nvme1n1/queue/nomerges 0 The problem is fixed. Changing tag to verified. ** 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/1833319 Title: Performance degradation when copying from LVM snapshot backed by NVMe disk Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1833319 [Impact] When copying files from a mounted LVM snapshot which resides on NVMe storage devices, there is a massive performance degradation in the rate sectors are read from the disk. The kernel is not merging sector requests and is instead issuing many small sector requests to the NVMe storage controller instead of one larger request. Experiments have shown a 14x-25x performance degradation in reads, where copies used to take seconds, now take minutes, and copies which took thirty minutes now take many hours. The following was found with btrace, running alongside cat (see Testing): A = IO remapped to different device Q = IO handled by request queue G = Get request U = Unplug request I = IO inserted onto request queue D = IO issued to driver C = IO completion When reading from the LVM snapshot, we see: 259,01 113 0.001117160 1606 A R 837872 + 8 <- (252,0) 835824 259,01 114 0.001117276 1606 Q R 837872 + 8 [cat] 259,01 115 0.001117451 1606 G R 837872 + 8 [cat] 259,01 116 0.001117979 1606 A R 837880 + 8 <- (252,0) 835832 259,01 117 0.001118119 1606 Q R 837880 + 8 [cat] 259,01 118 0.001118285 1606 G R 837880 + 8 [cat] 259,01 122 0.001121613 1606 I RS 837640 + 8 [cat] 259,01 123 0.001121687 1606 I RS 837648 + 8 [cat] 259,01 124 0.001121758 1606 I RS 837656 + 8 [cat] ... 259,01 154 0.001126118 377 D RS 837648 + 8 [kworker/1:1H] 259,01 155 0.001126445 377 D RS 837656 + 8 [kworker/1:1H] 259,01 156 0.001126871 377 D RS 837664 + 8 [kworker/1:1H] ... 259,01 183 0.001848512 0 C RS 837632 + 8 [0] Now what is happening here, is that a request for 8 sector read is placed onto the IO request queue, and is then inserted one at a time to the driver request queue and then fetched by the driver. Comparing this behaviour to reading data from a LVM snapshot on 4.6+ mainline or the Ubuntu 4.15 HWE kernel: M = IO back merged with request on queue 259,00 194 0.000532515 1897 A R 7358960 + 8 <- (253,0) 7356912 259,00 195 0.000532634 1897 Q R 7358960 + 8 [cat] 259,00 196 0.000532810 1897 M R 7358960 + 8 [cat] 259,00 197 0.000533864 1897 A R 7358968 + 8 <- (253,0) 7356920 259,00 198 0.000533991 1897 Q R 7358968 + 8 [cat] 259,00 199 0.000534177 1897 M R 7358968 + 8 [cat] 259,00 200 0.000534474 1897 UT N [cat] 1 259,00 201 0.000534586 1897 I R 7358464 + 512 [cat] 259,00 202 0.000537055 1897 D R 7358464 + 512 [cat] 259,00 203 0.002242539 0 C R 7358464 + 512 [0] This shows us a 8 sector read is added to the request queue, and is then subsequently [M]erged backward with other requests on the queue until the sum of all of those merged requests becomes 512 sectors. From there, the 512 sector read is placed onto the IO queue, where it is fetched by the device driver, and completes. [Fix] The problem is that the NVMe driver on 4.4 xenial kernel is not merging 8 sector requests. Merging is controlled per device by this sysfs entry: /sys/block/nvme1n1/queue/nomerges On 4.4 xenial, reading from this yields 2, or (QUEUE_FLAG_NOMERGES). On 4.6+ and 4.15 HWE kernel, reading from this yields 0, or allowing merge. Setting this to 0 on the 4.4 kernel with: # echo "0" > /sys/block/nvme1n1/queue/nomerges and testing again, we find performance is restored and the problem is fixed. Performing a btrace, we see 8 sector reads get backmerged into a 512 sector read which is done in one go. The problem was fixed in 4.5 upstream with the below commit: commit ef2d4615c59efb312e531a5e949970f37ca1c841 Author: Keith Busch Date: Thu Feb 11 13:05:40 2016 -0700 Subject: NVMe: Allow request
[Kernel-packages] [Bug 1825665] Re: Cannot set 3440x1440 resolution for HP 34C external monitor (HDMI) on ubuntu-wayland
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1825665 Title: Cannot set 3440x1440 resolution for HP 34C external monitor (HDMI) on ubuntu-wayland Status in linux package in Ubuntu: Expired Bug description: On the regular Ubuntu desktop I use an .xprofile with xrandr commands that add the monitors native resolution as follows: xrandr --newmode "3440x1440" 196.25 3440 3600 3952 4464 1440 1443 1453 1468 -hsync +vsync xrandr --addmode HDMI-1 "3440x1440" Unfortunately this doesn't work under wayland and I have not yet found a solution. I have tried several ideas including a custom edid bin file without success. I'm reporting against the gnome-control-center since this corresponds to the end user experience. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 18:21:23 2019 InstallationDate: Installed on 2018-08-25 (238 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825665/+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 1810200] Re: Can't install Ubuntu from live cd when nomodeset is added
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1810200 Title: Can't install Ubuntu from live cd when nomodeset is added Status in linux package in Ubuntu: Expired Bug description: I'm having issue with nouveau. (Overheat. See Bug #1768976). To disable nouveau when using live cd I found, that I need to run the live Ubuntu with nomodeset. The live Ubuntu starts fine, no overheat, able to use every program on livecd, except the installation itself. No matter how many times I click on it, nothing happens. Same as with starting the just install option, installation app not starts. I tried with 18.04.1 and 18.10 live cds. Can I make this work with nomodeset? Maybe by adding an other option? Do you know other way to run livecd with disabled nouveau? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810200/+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 1834913] Re: linux-snapdragon: 4.4.0-1119.125 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** 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 1834912 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834918 - phase: Packaging - phase-changed: Thursday, 04. July 2019 02:35 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 04. July 2019 04:06 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 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834913 Title: linux-snapdragon: 4.4.0-1119.125 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New 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 1834912 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834918 phase: Holding before Promote to Proposed phase-changed: Thursday, 04. July 2019 04:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834913/+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 1834942] Re: linux-oracle: 4.15.0-1018.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug 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: 1834943 - phase: Packaging - phase-changed: Thursday, 04. July 2019 02:10 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 04. July 2019 04:10 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: Ongoing -- builds not complete in ppa meta:building,signed:building,main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834942 Title: linux-oracle: 4.15.0-1018.20~16.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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New 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: 1834943 phase: Holding before Promote to Proposed phase-changed: Thursday, 04. July 2019 04:10 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834942/+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 1835348] 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 1835348
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/1835348
Title:
mm/huge_memory: fix vmf_insert_pfn_{pmd, pud}() crash, handle
unaligned addresses
Status in intel:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Description
Starting with c6f3c5ee40c1 ("mm/huge_memory.c: fix modifying of page
protection by insert_pfn_pmd()") vmf_insert_pfn_pmd() internally calls
pmdp_set_access_flags(). That helper enforces a pmd aligned @address
argument via VM_BUG_ON() assertion.
Update the implementation to take a 'struct vm_fault' argument directly
and apply the address alignment fixup internally to fix crash signatures
like:
kernel BUG at arch/x86/mm/pgtable.c:515!
invalid opcode: 1 SMP NOPTI
CPU: 51 PID: 43713 Comm: java Tainted: G OE 4.19.35 #1
[..]
RIP: 0010:pmdp_set_access_flags+0x48/0x50
[..]
Call Trace:
vmf_insert_pfn_pmd+0x198/0x350
dax_iomap_fault+0xe82/0x1190
ext4_dax_huge_fault+0x103/0x1f0
? __switch_to_asm+0x40/0x70
__handle_mm_fault+0x3f6/0x1370
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
handle_mm_fault+0xda/0x200
__do_page_fault+0x249/0x4f0
do_page_fault+0x32/0x110
? page_fault+0x8/0x30
page_fault+0x1e/0x30
Commits:
fce86ff5802b
Target Release:19.10
Target Kernel: 5.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1835348/+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 1831840] Re: Support new ums-realtek device
** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-bionic verification-done-cosmic verification-done-disco -- 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/1831840 Title: Support new ums-realtek device Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] Realtek storage device uses usb-storage by default. It works but we should use ums-realtek to bring more functionality, e.g. enabling/disabling MMC card detection. [Fix] Add its device ID to the driver. [Test] After this patch applied, we can use enable_mmc module option to control MMC detection. [Regression Potential] Low. The scope is limited to one device, and the driver is quite stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831840/+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
** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-bionic verification-done-cosmic verification-done-disco -- 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 Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed 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 Committed Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix 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 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)
Does touchpad work with HWE kernel? -- 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/1831710 Title: Touchpad not working (Lenevo Ideapad 330 series) Status in linux package in Ubuntu: Confirmed Bug description: The touch pad has not been used since the purchase of the product. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 5 13:41:22 2019 InstallationDate: Installed on 2019-06-05 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: athena 1232 F pulseaudio /dev/snd/pcmC1D0p: athena 1232 F...m pulseaudio /dev/snd/controlC0: athena 1232 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-05 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-21-generic N/A linux-backports-modules-4.18.0-21-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.18.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+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 1757218] Re: QCA9377 isn't being recognized sometimes
** Tags removed: verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-cosmic verification-done-disco -- 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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed
[Kernel-packages] [Bug 1835349] 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 1835349 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: eoan -- 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/1835349 Title: Fix devm_memremap_pages shutdown handling Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: > 1) Some p2pdma user calls pci_alloc_p2pmem() to get some memory to DMA > to taking a reference to the pgmap. > 2) Another process unbinds the underlying p2pdma driver and the devm > chain starts to unwind. > 3) devm_memremap_pages_release() is called and it kills the reference > and drop's it's last reference. Oh! Yes, nice find. We need to wait for the percpu-ref to be dead and all outstanding references dropped before we can proceed to arch_remove_memory(), and I think this problem has been there since day one because the final exit was always after devm_memremap_pages() release which means arch_remove_memory() was always racing any final put_page(). I'll take a look, it seems the arch_remove_pages() call needs to be moved out-of-line to its own context and wait for the final exit of the percpu-ref. Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835349/+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 1834894] Re: linux-snapdragon: 5.0.0-1017.18 -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 -- kernel-stable-master-bug: 1834902 - phase: Ready for Packaging - phase-changed: Tuesday, 02. July 2019 14:03 UTC + phase: Packaging + phase-changed: Thursday, 04. July 2019 04:04 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834894 Title: linux-snapdragon: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New 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: 1834902 phase: Packaging phase-changed: Thursday, 04. July 2019 04:04 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+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 1835350] 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 1835350 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: eoan -- 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/1835350 Title: Hang / zombie process from Xarray page-fault conversion Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: We're seeing a case where RocksDB hangs and becomes defunct when trying to kill the process. v4.19 succeeds and v4.20 fails. Robert was able to bisect this to commit b15cd800682f "dax: Convert page fault handlers to XArray". Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835350/+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 1835347] 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 1835347 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: eoan -- 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/1835347 Title: device_dax - export a 'resource' attribute for dax devices Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: device_dax devices need to export a resource attribute so that libdaxctl can use it to find the address range for the device. This is required for onlining/offlining memory associated with a device in the system-ram mode (i.e. kmem). Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835347/+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 1835351] 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 1835351 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: eoan -- 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/1835351 Title: Performance regression with AEP NVDIMM Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: The recent changes to use memcpy_mcsafe() in the dax read path to handle media errors regresses performance: http://bugzilla.novell.com/show_bug.cgi?id=1114829 Investigate an SSE implementation of memcpy_mcsafe(). Target Release: 19.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835351/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
When the power save is not disabled then the noise comes from speaker port, I don't have the headphone port connected anywhere so I can't right now check that. Once https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1833880 happens again I'll have to reboot and I can power down the machine and attach a jack to it to check. -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1835351] [NEW] Performance regression with AEP NVDIMM
Public bug reported: Description: The recent changes to use memcpy_mcsafe() in the dax read path to handle media errors regresses performance: http://bugzilla.novell.com/show_bug.cgi?id=1114829 Investigate an SSE implementation of memcpy_mcsafe(). Target Release: 19.10 Target Kernel: TBD ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/1835351 Title: Performance regression with AEP NVDIMM Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: The recent changes to use memcpy_mcsafe() in the dax read path to handle media errors regresses performance: http://bugzilla.novell.com/show_bug.cgi?id=1114829 Investigate an SSE implementation of memcpy_mcsafe(). Target Release: 19.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835351/+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 1835349] [NEW] Fix devm_memremap_pages shutdown handling
Public bug reported: Description: > 1) Some p2pdma user calls pci_alloc_p2pmem() to get some memory to DMA > to taking a reference to the pgmap. > 2) Another process unbinds the underlying p2pdma driver and the devm > chain starts to unwind. > 3) devm_memremap_pages_release() is called and it kills the reference > and drop's it's last reference. Oh! Yes, nice find. We need to wait for the percpu-ref to be dead and all outstanding references dropped before we can proceed to arch_remove_memory(), and I think this problem has been there since day one because the final exit was always after devm_memremap_pages() release which means arch_remove_memory() was always racing any final put_page(). I'll take a look, it seems the arch_remove_pages() call needs to be moved out-of-line to its own context and wait for the final exit of the percpu-ref. Target Release: 19.10 Target Kernel: 5.3 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/1835349 Title: Fix devm_memremap_pages shutdown handling Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: > 1) Some p2pdma user calls pci_alloc_p2pmem() to get some memory to DMA > to taking a reference to the pgmap. > 2) Another process unbinds the underlying p2pdma driver and the devm > chain starts to unwind. > 3) devm_memremap_pages_release() is called and it kills the reference > and drop's it's last reference. Oh! Yes, nice find. We need to wait for the percpu-ref to be dead and all outstanding references dropped before we can proceed to arch_remove_memory(), and I think this problem has been there since day one because the final exit was always after devm_memremap_pages() release which means arch_remove_memory() was always racing any final put_page(). I'll take a look, it seems the arch_remove_pages() call needs to be moved out-of-line to its own context and wait for the final exit of the percpu-ref. Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835349/+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 1835348] [NEW] mm/huge_memory: fix vmf_insert_pfn_{pmd, pud}() crash, handle unaligned addresses
Public bug reported:
Description
Starting with c6f3c5ee40c1 ("mm/huge_memory.c: fix modifying of page
protection by insert_pfn_pmd()") vmf_insert_pfn_pmd() internally calls
pmdp_set_access_flags(). That helper enforces a pmd aligned @address
argument via VM_BUG_ON() assertion.
Update the implementation to take a 'struct vm_fault' argument directly
and apply the address alignment fixup internally to fix crash signatures
like:
kernel BUG at arch/x86/mm/pgtable.c:515!
invalid opcode: 1 SMP NOPTI
CPU: 51 PID: 43713 Comm: java Tainted: G OE 4.19.35 #1
[..]
RIP: 0010:pmdp_set_access_flags+0x48/0x50
[..]
Call Trace:
vmf_insert_pfn_pmd+0x198/0x350
dax_iomap_fault+0xe82/0x1190
ext4_dax_huge_fault+0x103/0x1f0
? __switch_to_asm+0x40/0x70
__handle_mm_fault+0x3f6/0x1370
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
handle_mm_fault+0xda/0x200
__do_page_fault+0x249/0x4f0
do_page_fault+0x32/0x110
? page_fault+0x8/0x30
page_fault+0x1e/0x30
Commits:
fce86ff5802b
Target Release:19.10
Target Kernel: 5.2
** Affects: intel
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: intel-kernel-19.10
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: 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/1835348
Title:
mm/huge_memory: fix vmf_insert_pfn_{pmd, pud}() crash, handle
unaligned addresses
Status in intel:
New
Status in linux package in Ubuntu:
New
Bug description:
Description
Starting with c6f3c5ee40c1 ("mm/huge_memory.c: fix modifying of page
protection by insert_pfn_pmd()") vmf_insert_pfn_pmd() internally calls
pmdp_set_access_flags(). That helper enforces a pmd aligned @address
argument via VM_BUG_ON() assertion.
Update the implementation to take a 'struct vm_fault' argument directly
and apply the address alignment fixup internally to fix crash signatures
like:
kernel BUG at arch/x86/mm/pgtable.c:515!
invalid opcode: 1 SMP NOPTI
CPU: 51 PID: 43713 Comm: java Tainted: G OE 4.19.35 #1
[..]
RIP: 0010:pmdp_set_access_flags+0x48/0x50
[..]
Call Trace:
vmf_insert_pfn_pmd+0x198/0x350
dax_iomap_fault+0xe82/0x1190
ext4_dax_huge_fault+0x103/0x1f0
? __switch_to_asm+0x40/0x70
__handle_mm_fault+0x3f6/0x1370
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
handle_mm_fault+0xda/0x200
__do_page_fault+0x249/0x4f0
do_page_fault+0x32/0x110
? page_fault+0x8/0x30
page_fault+0x1e/0x30
Commits:
fce86ff5802b
Target Release:19.10
Target Kernel: 5.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1835348/+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 1834894] Re: linux-snapdragon: 5.0.0-1017.18 -proposed tracker
** Summary changed: - linux-snapdragon: -proposed tracker + linux-snapdragon: 5.0.0-1017.18 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834894 Title: linux-snapdragon: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New 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: 1834902 phase: Ready for Packaging phase-changed: Tuesday, 02. July 2019 14:03 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
So when don't set the power_save=0, does the noise come from speaker or headphone or both of them? -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux-firmware (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Bionic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Description changed: [Impact] BT fails to enable again after disabled it by hotkey with the following message -Bus 001 Device 004: ID 8087:0029 Intel Corp. + Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. + + [Misc] + The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. ** Changed in: linux-firmware (Ubuntu Disco) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: In Progress Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. [Misc] The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1835345/+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 1834464] Re: Missing bluetooth firmware for Intel Wireless-AC 9462/9560
Fixes committed to Bionic/Cosmic/Disco. Eoan to be rebased onto upstream master branch. ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1834464 Title: Missing bluetooth firmware for Intel Wireless-AC 9462/9560 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: In Progress Bug description: [Impact] Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to be enabled. [Fix] Backport newly released firmware blobs from linux-firmware. This will also requires minor change to the WHENCE file to resolve cherry-pick conflicts. B/C/D would requires this explicitly and Eoan should be rebased onto linux-firmware master branch HEAD as usual. [Test Case] Verified with hardware platforms with corresponding devices. Completely power off and power on to trigger firmware reload, check from dmesg to see if Bluetooth firmware has been correctly loaded. [Regression Risk] Low. This adds new binary firmware blobs that are only loaded by targeting hardware. == original bug description == On systems with Intel Wireless-AC 9462/9560 cards, following failed- to-load-firmware kernel messages found: bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi failed with error -2 See also Bug #1833065 for wireless firmware & driver fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834464/+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 1835350] [NEW] Hang / zombie process from Xarray page-fault conversion
Public bug reported: Description: We're seeing a case where RocksDB hangs and becomes defunct when trying to kill the process. v4.19 succeeds and v4.20 fails. Robert was able to bisect this to commit b15cd800682f "dax: Convert page fault handlers to XArray". Target Release: 19.10 Target Kernel: 5.3 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/1835350 Title: Hang / zombie process from Xarray page-fault conversion Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: We're seeing a case where RocksDB hangs and becomes defunct when trying to kill the process. v4.19 succeeds and v4.20 fails. Robert was able to bisect this to commit b15cd800682f "dax: Convert page fault handlers to XArray". Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835350/+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 1730883] Re: [HMEM] Allow persistent memory to be used like normal RAM
duplicate with LP#1730872 ** Changed in: intel Status: Fix Committed => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1730883 Title: [HMEM] Allow persistent memory to be used like normal RAM Status in intel: Invalid Status in linux package in Ubuntu: Invalid Bug description: Description Persistent memory is cool. But, currently, you have to rewrite your applications to use it. Wouldn't it be cool if you could just have it show up in your system like normal RAM and get to it like a slow blob of memory? Well... have I got the patch series for you! This series adds a new "driver" to which pmem devices can be attached. Once attached, the memory "owned" by the device is hot-added to the kernel and managed like any other memory. On systems with an HMAT (a new ACPI table), each socket (roughly) will have a separate NUMA node for its persistent memory so this newly-added memory can be selected by its unique NUMA node. Target Kernel: 5.1 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730883/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
I have also tested the updated kernel from bionic-proposed using the VM in which the original problem was first experienced. 'uname -a' after adding bionic-proposed to /etc/apt/sources.list and doing 'sudo apt update; sudo apt upgrade' Linux ubuntuvm1 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Like Daniel, the changes incorporated into 4.15.0-55 are working for me as well. -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-hwe source package in Bionic: Fix Released Status in mutter source package in Bionic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-hwe source package in Disco: Invalid Status in mutter source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in linux-hwe source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] Low, it should fix vmwgfx and stop using the wrong clock. A test kernel (pre-sru) has been made available to impact users for them to test and conclude it works. It does work as expected, and no regression has been found during the pre-sru testing phase. As per commit description: " This should be transparent to to user space, as long as it doesn't compare the time against the result of gettimeofday(). " [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
[Kernel-packages] [Bug 1835343] 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 1835343 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: eoan -- 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/1835343 Title: [HMEM] Parse HMAT table and populate sysfs object model Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: Once we have our generic sysfs layout, we will need to parse the HMAT and create the kobjects and references to populate that layout. Merged during 5.2 window. Commit IDs and Patch Subject: 13bac55ef7ae doc/mm: New documentation for memory performance d9e8844c7d81 acpi/hmat: Register memory side cache attributes 8d59f5a2ca76 acpi/hmat: Register performance attributes 665ac7e92757 acpi/hmat: Register processor domain to its memory acc02a109b04 node: Add memory-side caching attributes e1cf33aafb84 node: Add heterogenous memory access attributes 08d9dbe72b1f node: Link memory nodes to their compute nodes 3accf7ae37a9 acpi/hmat: Parse and report heterogeneous memory 3bc0e8eb179d acpi: Add HMAT to generic parsing tables 60574d1e05b0 acpi: Create subtable parsing infrastructure Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835343/+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 1835340] 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 1835340 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: eoan -- 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/1835340 Title: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. Target Release: 19.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835340/+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 1835347] [NEW] device_dax - export a 'resource' attribute for dax devices
Public bug reported: Description: device_dax devices need to export a resource attribute so that libdaxctl can use it to find the address range for the device. This is required for onlining/offlining memory associated with a device in the system-ram mode (i.e. kmem). Target Release: 19.10 Target Kernel: 5.3 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/1835347 Title: device_dax - export a 'resource' attribute for dax devices Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: device_dax devices need to export a resource attribute so that libdaxctl can use it to find the address range for the device. This is required for onlining/offlining memory associated with a device in the system-ram mode (i.e. kmem). Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835347/+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 1835343] [NEW] [HMEM] Parse HMAT table and populate sysfs object model
Public bug reported: Description: Once we have our generic sysfs layout, we will need to parse the HMAT and create the kobjects and references to populate that layout. Merged during 5.2 window. Commit IDs and Patch Subject: 13bac55ef7ae doc/mm: New documentation for memory performance d9e8844c7d81 acpi/hmat: Register memory side cache attributes 8d59f5a2ca76 acpi/hmat: Register performance attributes 665ac7e92757 acpi/hmat: Register processor domain to its memory acc02a109b04 node: Add memory-side caching attributes e1cf33aafb84 node: Add heterogenous memory access attributes 08d9dbe72b1f node: Link memory nodes to their compute nodes 3accf7ae37a9 acpi/hmat: Parse and report heterogeneous memory 3bc0e8eb179d acpi: Add HMAT to generic parsing tables 60574d1e05b0 acpi: Create subtable parsing infrastructure Target Release: 19.10 Target Kernel: 5.2 ** Affects: intel Importance: Undecided Status: Fix Committed ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Committed ** Description changed: Description: Once we have our generic sysfs layout, we will need to parse the HMAT and create the kobjects and references to populate that layout. - 08d9dbe72b1f 13bac55ef7ae 3accf7ae37a9 3bc0e8eb179d 60574d1e05b0 - 665ac7e92757 8d59f5a2ca76 acc02a109b04 d9e8844c7d81 e1cf33aafb84 + Merged during 5.2 window. Commit IDs and Patch Subject: + + 13bac55ef7ae doc/mm: New documentation for memory performance + d9e8844c7d81 acpi/hmat: Register memory side cache attributes + 8d59f5a2ca76 acpi/hmat: Register performance attributes + 665ac7e92757 acpi/hmat: Register processor domain to its memory + acc02a109b04 node: Add memory-side caching attributes + e1cf33aafb84 node: Add heterogenous memory access attributes + 08d9dbe72b1f node: Link memory nodes to their compute nodes + 3accf7ae37a9 acpi/hmat: Parse and report heterogeneous memory + 3bc0e8eb179d acpi: Add HMAT to generic parsing tables + 60574d1e05b0 acpi: Create subtable parsing infrastructure Target Release: 19.10 Target Kernel: 5.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835343 Title: [HMEM] Parse HMAT table and populate sysfs object model Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: Once we have our generic sysfs layout, we will need to parse the HMAT and create the kobjects and references to populate that layout. Merged during 5.2 window. Commit IDs and Patch Subject: 13bac55ef7ae doc/mm: New documentation for memory performance d9e8844c7d81 acpi/hmat: Register memory side cache attributes 8d59f5a2ca76 acpi/hmat: Register performance attributes 665ac7e92757 acpi/hmat: Register processor domain to its memory acc02a109b04 node: Add memory-side caching attributes e1cf33aafb84 node: Add heterogenous memory access attributes 08d9dbe72b1f node: Link memory nodes to their compute nodes 3accf7ae37a9 acpi/hmat: Parse and report heterogeneous memory 3bc0e8eb179d acpi: Add HMAT to generic parsing tables 60574d1e05b0 acpi: Create subtable parsing infrastructure Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835343/+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 1835345] [NEW] [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
Public bug reported: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in linux-firmware package in Ubuntu: In Progress Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1835345/+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 1835340] [NEW] [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications
Public bug reported: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. Target Release: 19.10 Target Kernel: TBD ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/1835340 Title: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. Target Release: 19.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835340/+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 1834893] Re: linux-azure: 4.18.0-1025.26 -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 1834889 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1834904 - phase: Ready for Packaging - phase-changed: Tuesday, 02. July 2019 16:05 UTC + phase: Packaging + phase-changed: Thursday, 04. July 2019 03:04 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded 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/1834893 Title: linux-azure: 4.18.0-1025.26 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Cosmic: New 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 1834889 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1834904 phase: Packaging phase-changed: Thursday, 04. July 2019 03:04 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834893/+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 1835333] 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 1835333 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: eoan -- 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/1835333 Title: [IOMMU] IOMMU scalable mode for mdev pass-through Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: Intel IOMMU scalable mode is proposed in the new IOMMU spec. It provides two level address translation based on a PASID. With this translation mode, a PASID-capable PCIe device could pass through partial of its resource (also called AI, Assignment Instance) to the guest VM with fully IOMMU protection and isolation. It’s the key for a platform in order to support SIOV. 0e8000f8f616 67b8e02b5e76 8cc3759a6c49 95587a75de17 a3a195929d40 d7cbc0f3220f Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835333/+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 1835334] 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 1835334 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: eoan -- 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/1835334 Title: [IOMMU] vfio/vfio-mdev enhancement for full-iommu support Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: VFIO (Virtual Function I/O) is an IOMMU/device agnostic framework for exposing direct device access to user space in a secure IOMMU protected environment. VFIO/MDEV(mediated device) is based on VFIO to provide a generic framework for mediated devices simulated by a real physical device. Current vfio/mdev doesn’t implement full iommu support. With scalable mode supported by IOMMU hardware, each mediated device could be isolated and protected by IOMMU. Hence all IOMMU ops could be handled in vfio/mdev (no dependency on the parent device). 7bd50f0cd2fd 8ac13175cbe9 be068fa236c3 Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835334/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
apport information -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+attachment/5274989/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+attachment/5274987/+files/CurrentDmesg.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+attachment/5274986/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274986/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) - --- + --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: t 4604 F pulseaudio - /dev/snd/pcmC0D0p: t 4604 F...m pulseaudio - /dev/snd/controlC1: t 4604 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: a 4604 F pulseaudio + /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio + /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: - enp63s0 no wireless extensions. - - wg0 no wireless extensions. - - lono wireless extensions. + enp63s0 no wireless extensions. + + wg0 no wireless extensions. + + lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: - linux-restricted-modules-5.0.0-20-generic N/A - linux-backports-modules-5.0.0-20-generic N/A - linux-firmware1.178.2 + linux-restricted-modules-5.0.0-20-generic N/A + linux-backports-modules-5.0.0-20-generic N/A + linux-firmware1.178.2 RfKill: - + Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+attachment/5274976/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro
[Kernel-packages] [Bug 1833793] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274984/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274983/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274981/+files/ProcEnviron.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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274982/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274977/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274980/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274985/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
apport information ** Tags added: apport-collected ** Description changed: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: t 4604 F pulseaudio + /dev/snd/pcmC0D0p: t 4604 F...m pulseaudio + /dev/snd/controlC1: t 4604 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2017-08-23 (679 days ago) + InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + IwConfig: + enp63s0 no wireless extensions. + + wg0 no wireless extensions. + + lono wireless extensions. + MachineType: Hewlett-Packard HP Compaq dc5700 Microtower + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-20-generic N/A + linux-backports-modules-5.0.0-20-generic N/A + linux-firmware1.178.2 + RfKill: + + Tags: disco + Uname: Linux 5.0.0-20-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) + UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo + _MarkForUpload: True + dmi.bios.date: 11/10/2011 + dmi.bios.vendor: Hewlett-Packard + dmi.bios.version: 786E2 v02.09 + dmi.board.name: 0A60h + dmi.board.vendor: Hewlett-Packard + dmi.chassis.type: 6 + dmi.chassis.vendor: Hewlett-Packard + dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: + dmi.product.family: 103C_53307F + dmi.product.name: HP Compaq dc5700 Microtower + dmi.product.sku: EW287AV + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274974/+files/AlsaInfo.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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor:
[Kernel-packages] [Bug 1834893] Re: linux-azure: 4.18.0-1025.26 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.18.0-1025.26 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1834893 Title: linux-azure: 4.18.0-1025.26 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Cosmic: New 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 1834889 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1834904 phase: Ready for Packaging phase-changed: Tuesday, 02. July 2019 16:05 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834893/+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 1833793] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274979/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274975/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274976/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1833793/+attachment/5274978/+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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1835335] [NEW] Enable Interrupt Message Store (IMS)
Private bug reported: Description: Implement IMS framework and VFIO MSI Extensions Target Release: 19.10 Target Kernel: 5.3 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1835335 Title: Enable Interrupt Message Store (IMS) Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: Implement IMS framework and VFIO MSI Extensions Target Release: 19.10 Target Kernel: 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835335/+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 1834913] Re: linux-snapdragon: 4.4.0-1119.125 -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 1834912 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834918 - phase: Ready for Packaging - phase-changed: Tuesday, 02. July 2019 15:35 UTC + phase: Packaging + phase-changed: Thursday, 04. July 2019 02:35 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834913 Title: linux-snapdragon: 4.4.0-1119.125 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New 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 1834912 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834918 phase: Packaging phase-changed: Thursday, 04. July 2019 02:35 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834913/+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 1835333] [NEW] [IOMMU] IOMMU scalable mode for mdev pass-through
Public bug reported: Description: Intel IOMMU scalable mode is proposed in the new IOMMU spec. It provides two level address translation based on a PASID. With this translation mode, a PASID-capable PCIe device could pass through partial of its resource (also called AI, Assignment Instance) to the guest VM with fully IOMMU protection and isolation. It’s the key for a platform in order to support SIOV. 0e8000f8f616 67b8e02b5e76 8cc3759a6c49 95587a75de17 a3a195929d40 d7cbc0f3220f Target Kernel: 5.2 Target Release: 19.10 ** Affects: intel Importance: Undecided Status: Fix Committed ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => 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/1835333 Title: [IOMMU] IOMMU scalable mode for mdev pass-through Status in intel: Fix Committed Status in linux package in Ubuntu: New Bug description: Description: Intel IOMMU scalable mode is proposed in the new IOMMU spec. It provides two level address translation based on a PASID. With this translation mode, a PASID-capable PCIe device could pass through partial of its resource (also called AI, Assignment Instance) to the guest VM with fully IOMMU protection and isolation. It’s the key for a platform in order to support SIOV. 0e8000f8f616 67b8e02b5e76 8cc3759a6c49 95587a75de17 a3a195929d40 d7cbc0f3220f Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835333/+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 1834114] Re: AX88772A USB to Ethernet dongle doesn't work
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1834114 Title: AX88772A USB to Ethernet dongle doesn't work Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Triaged Bug description: [Impact] There are 2 asix drivers in the kernel, they are drivers/net/usb/asix and drivers/net/phy/asix. It leads to the compilation race condition that one overwrites the other asix.mod in .tmp_version directory. This affects the USB dongle if the "phy" one wins. T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0b95 ProdID=7720 Rev=00.01 S: Manufacturer=ASIX Elec. Corp. S: Product=AX88772A S: SerialNumber=000527 C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=250mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=asix [Fix] The same name asix has been introduced since v4.18-rc1 by this commit 31dd83b96641 net-next: phy: new Asix Electronics PHY driver the new commit fix this issue by renaming it a9520543b123 net: phy: rename Asix Electronics PHY driver [Test] Verified on my own ASIX USB Ethernet dongle. [Regression Potential] Low, it only rename the module name, no code change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834114/+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 1835334] [NEW] [IOMMU] vfio/vfio-mdev enhancement for full-iommu support
Public bug reported: Description: VFIO (Virtual Function I/O) is an IOMMU/device agnostic framework for exposing direct device access to user space in a secure IOMMU protected environment. VFIO/MDEV(mediated device) is based on VFIO to provide a generic framework for mediated devices simulated by a real physical device. Current vfio/mdev doesn’t implement full iommu support. With scalable mode supported by IOMMU hardware, each mediated device could be isolated and protected by IOMMU. Hence all IOMMU ops could be handled in vfio/mdev (no dependency on the parent device). 7bd50f0cd2fd 8ac13175cbe9 be068fa236c3 Target Release: 19.10 Target Kernel: 5.2 ** Affects: intel Importance: Undecided Status: Fix Committed ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => 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/1835334 Title: [IOMMU] vfio/vfio-mdev enhancement for full-iommu support Status in intel: Fix Committed Status in linux package in Ubuntu: New Bug description: Description: VFIO (Virtual Function I/O) is an IOMMU/device agnostic framework for exposing direct device access to user space in a secure IOMMU protected environment. VFIO/MDEV(mediated device) is based on VFIO to provide a generic framework for mediated devices simulated by a real physical device. Current vfio/mdev doesn’t implement full iommu support. With scalable mode supported by IOMMU hardware, each mediated device could be isolated and protected by IOMMU. Hence all IOMMU ops could be handled in vfio/mdev (no dependency on the parent device). 7bd50f0cd2fd 8ac13175cbe9 be068fa236c3 Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835334/+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 1834883] Re: linux-aws: 4.18.0-1021.25 -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 1834882 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1834904 - phase: Ready for Packaging - phase-changed: Tuesday, 02. July 2019 16:05 UTC + phase: Packaging + phase-changed: Thursday, 04. July 2019 02:34 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded 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/1834883 Title: linux-aws: 4.18.0-1021.25 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New 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 1834882 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1834904 phase: Packaging phase-changed: Thursday, 04. July 2019 02:34 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834883/+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 1828133] Re: Intel CyclonePeak wifi firmware
** Changed in: oem-priority Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828133 Title: Intel CyclonePeak wifi firmware Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: [Impact] New Intel CyclonePeak Wifi cards require new firmware to enable. [Fix] To update the firmware we want only, backport the following 2 commits from iwlwifi tree for-upstream branch[1], and remove all 9000 series related firmwares. 95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series 68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares 1. git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git [Test Case] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Risk] Low. This firmware is for new cards and new ABI, it won't affect current Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi DKMS driver or oem-osp1 kernel loads this firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828133/+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 1834883] Re: linux-aws: 4.18.0-1021.25 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.18.0-1021.25 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- 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/1834883 Title: linux-aws: 4.18.0-1021.25 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New 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 1834882 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1834904 phase: Packaging phase-changed: Thursday, 04. July 2019 02:34 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834883/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
Need you to collect some logs, then let us see if it can be fixed through kernel driver. 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 1833793 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. ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Incomplete Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1833793] [NEW] Updating to 19.04 audio keeps clicking when nothing is playing audio
You have been subscribed to a public bug: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) ** Affects: linux (Ubuntu) Importance: High Status: Incomplete ** Tags: audio bot-comment disco -- Updating to 19.04 audio keeps clicking when nothing is playing audio https://bugs.launchpad.net/bugs/1833793 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834913] Re: linux-snapdragon: 4.4.0-1119.125 -proposed tracker
** Summary changed: - linux-snapdragon: -proposed tracker + linux-snapdragon: 4.4.0-1119.125 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834913 Title: linux-snapdragon: 4.4.0-1119.125 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New 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 1834912 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834918 phase: Ready for Packaging phase-changed: Tuesday, 02. July 2019 15:35 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834913/+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 1834942] Re: linux-oracle: 4.15.0-1018.20~16.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 -- swm properties -- kernel-stable-master-bug: 1834943 - phase: Ready for Packaging - phase-changed: Wednesday, 03. July 2019 07:12 UTC + phase: Packaging + phase-changed: Thursday, 04. July 2019 02:10 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834942 Title: linux-oracle: 4.15.0-1018.20~16.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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New 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: 1834943 phase: Packaging phase-changed: Thursday, 04. July 2019 02:10 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834942/+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 1781924] Re: Kernel wrong temperature reporting
This bug has been reported a few times in Ask Ubuntu. Just today (July 3rd, 2019) I was going back through `dmesg` and by chance I noticed on June 22nd, 2019 the errors appear about a dozen times. I've been on the same kernel version 4.14.114 LTS for a couple/few months now but I did flirt with version 4.14.120 LTS briefly and it is possible I was using that kernel version that day. I would have to check journalctl to find out for sure if someone deems it relevant. I don't view this bogus throttling error as a problem more of a curiosity if anything. -- 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/1781924 Title: Kernel wrong temperature reporting Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A
[Kernel-packages] [Bug 1834942] Re: linux-oracle: 4.15.0-1018.20~16.04.1 -proposed tracker
** Summary changed: - linux-oracle: -proposed tracker + linux-oracle: 4.15.0-1018.20~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834942 Title: linux-oracle: 4.15.0-1018.20~16.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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New 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: 1834943 phase: Ready for Packaging phase-changed: Wednesday, 03. July 2019 07:12 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834942/+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 1831065] Re: does not detect headphone when there is no other output devices
** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- 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/1831065 Title: does not detect headphone when there is no other output devices Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Bug description: These two patches are already in the kernel-v5.0, so only B and C need these two patches. [Impact] On a Dell machine, there is no other output devices but a headphone on it, when plugging headset, the headset-mic can't work. [Fix] The headphone detection method is buggy, the driver can't detect the headphone, then the driver will not initialize for headset-mic, after applying these patches, the problem is fixed. [Test Case] Plug headset and record the sound from headset-mic, it works well. [Regression Risk] Low. the patch just change the headphone detection function, and the function is already in the kernel from 5.0-rc, no bug is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831065/+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 1832299] Re: Add new sound card PCIID into the alsa driver
** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-bionic verification-done-cosmic verification-done-disco -- 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/1832299 Title: Add new sound card PCIID into the alsa driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: New Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1832299 The 0001-xxx.patch is for adding the ICL pciid, it is not in the bionic kernel, so bionic kernel needs two patches. The 0002-xxx.patch is in the upstream from v5.2-rc1, it is needed for b/c/d/e. [Impact] We have some cometlake machines, after installing the bionic kernel, the sound can't work at all, we found the sound driver didn't load into the kernel. [Fix] After add the pciid in the pci_driver, the sound driver can be loaded and sound worked well. [Test Case] Boot the system and play sound or record sound, they all worked well [Regression Risk] Low. Adding new pciid, will not change existing functions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+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 1826868] Re: Sound device not detected after resume from hibernate
** Tags removed: verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-cosmic verification-done-disco -- 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/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: The patch is already in the v5.2-rc1, so don't send the patch to unstable. In the V2, I added 3 more patches. The 0001-xxx.patch is for fixing the issue of "audio doesn't work after s3/s4 on cln and glk machines", but it introduces a new issue of "screen flickering when CDCLK changes", So I added 0002/3/4-xxx.patch to fix the new issue. [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] I applied the patches to bionic kernel and disco kernel, and tested them on Whiskeylake, cannonlake, kabylake, skylake and geminilake machines, before s3, I verified analogue audio, hdmi audio and screen dispaly all worked well, then let the system enter s3 and resume, recheck the analogue audio, hdmi audio and screen display, all worked well too. And repeated the test 5 times. [Regression Risk] Low. I have tested the patched kernel on different Dell and Lenovo machines, they include Whiskeylake, cannonlake, kabylake, skylake and geminilake. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures
Without the patch, I can reproduce the hang fairly frequently, in one or
two loops, which fails in this way:
[ 1069.711956] bcache: cancel_writeback_rate_update_dwork() give up waiting for
dc->writeback_write_update to quit
[ 1088.583986] INFO: task kworker/0:2:436 blocked for more than 120 seconds.
[ 1088.590330] Tainted: P O 4.15.0-54-generic #58-Ubuntu
[ 1088.595831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 1088.598210] kworker/0:2 D0 436 2 0x8000
[ 1088.598244] Workqueue: events update_writeback_rate [bcache]
[ 1088.598246] Call Trace:
[ 1088.598255] __schedule+0x291/0x8a0
[ 1088.598258] ? __switch_to_asm+0x40/0x70
[ 1088.598260] schedule+0x2c/0x80
[ 1088.598262] schedule_preempt_disabled+0xe/0x10
[ 1088.598264] __mutex_lock.isra.2+0x18c/0x4d0
[ 1088.598266] ? __switch_to_asm+0x34/0x70
[ 1088.598268] ? __switch_to_asm+0x34/0x70
[ 1088.598270] ? __switch_to_asm+0x40/0x70
[ 1088.598272] __mutex_lock_slowpath+0x13/0x20
[ 1088.598274] ? __mutex_lock_slowpath+0x13/0x20
[ 1088.598276] mutex_lock+0x2f/0x40
[ 1088.598281] update_writeback_rate+0x98/0x2b0 [bcache]
[ 1088.598285] process_one_work+0x1de/0x410
[ 1088.598287] worker_thread+0x32/0x410
[ 1088.598289] kthread+0x121/0x140
[ 1088.598291] ? process_one_work+0x410/0x410
[ 1088.598293] ? kthread_create_worker_on_cpu+0x70/0x70
[ 1088.598295] ret_from_fork+0x35/0x40
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux source package in Disco:
New
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures
I've setup our integration test that runs the the CDO-QA bcache/ceph
setup.
On the updated kernel I got through 10 loops on the deployment before it
stacktraced:
http://paste.ubuntu.com/p/zVrtvKBfCY/
[ 3939.846908] bcache: bch_cached_dev_attach() Caching vdd as bcache5 on set
275985b3-da58-41f8-9072-958bd960b490
[ 3939.878388] bcache: register_bcache() error /dev/vdd: device already
registered (emitting change event)
[ 3939.904984] bcache: register_bcache() error /dev/vdd: device already
registered (emitting change event)
[ 3939.972715] bcache: register_bcache() error /dev/vdd: device already
registered (emitting change event)
[ 3940.059415] bcache: register_bcache() error /dev/vdd: device already
registered (emitting change event)
[ 3940.129854] bcache: register_bcache() error /dev/vdd: device already
registered (emitting change event)
[ 3949.257051] md: md0: resync done.
[ 4109.273558] INFO: task python3:19635 blocked for more than 120 seconds.
[ 4109.279331] Tainted: P O 4.15.0-55-generic #60+lp796292
[ 4109.284767] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 4109.288771] python3 D0 19635 16361 0x
[ 4109.288774] Call Trace:
[ 4109.288818] __schedule+0x291/0x8a0
[ 4109.288822] ? __switch_to_asm+0x34/0x70
[ 4109.288824] ? __switch_to_asm+0x40/0x70
[ 4109.288826] schedule+0x2c/0x80
[ 4109.288852] bch_bucket_alloc+0x1fa/0x350 [bcache]
[ 4109.288866] ? wait_woken+0x80/0x80
[ 4109.288872] __bch_bucket_alloc_set+0xfe/0x150 [bcache]
[ 4109.288876] bch_bucket_alloc_set+0x4e/0x70 [bcache]
[ 4109.22] __uuid_write+0x59/0x150 [bcache]
[ 4109.288895] ? submit_bio+0x73/0x140
[ 4109.288900] ? __write_super+0x137/0x170 [bcache]
[ 4109.288905] bch_uuid_write+0x16/0x40 [bcache]
[ 4109.288911] __cached_dev_store+0x1a1/0x6d0 [bcache]
[ 4109.288916] bch_cached_dev_store+0x39/0xc0 [bcache]
[ 4109.288992] sysfs_kf_write+0x3c/0x50
[ 4109.288998] kernfs_fop_write+0x125/0x1a0
[ 4109.289001] __vfs_write+0x1b/0x40
[ 4109.289003] vfs_write+0xb1/0x1a0
[ 4109.289004] SyS_write+0x55/0xc0
[ 4109.289010] do_syscall_64+0x73/0x130
[ 4109.289014] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 4109.289016] RIP: 0033:0x7f8d2833e154
[ 4109.289018] RSP: 002b:7ffcda55a4e8 EFLAGS: 0246 ORIG_RAX:
0001
[ 4109.289020] RAX: ffda RBX: 0008 RCX: 7f8d2833e154
[ 4109.289021] RDX: 0008 RSI: 022b7360 RDI: 0003
[ 4109.289022] RBP: 7f8d288396c0 R08: R09:
[ 4109.289022] R10: 0100 R11: 0246 R12: 0003
[ 4109.289026] R13: R14: 022b7360 R15: 01fe8db0
[ 4109.289033] INFO: task bcache_allocato:22317 blocked for more than 120
seconds.
[ 4109.292172] Tainted: P O 4.15.0-55-generic #60+lp796292
[ 4109.295345] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 4109.298208] bcache_allocato D0 22317 2 0x8000
[ 4109.298212] Call Trace:
[ 4109.298217] __schedule+0x291/0x8a0
[ 4109.298225] schedule+0x2c/0x80
[ 4109.298232] bch_bucket_alloc+0x1fa/0x350 [bcache]
[ 4109.298235] ? wait_woken+0x80/0x80
[ 4109.298241] bch_prio_write+0x19f/0x340 [bcache]
[ 4109.298246] bch_allocator_thread+0x502/0xca0 [bcache]
[ 4109.298260] kthread+0x121/0x140
[ 4109.298264] ? bch_invalidate_one_bucket+0x80/0x80 [bcache]
[ 4109.298274] ? kthread_create_worker_on_cpu+0x70/0x70
[ 4109.298277] ret_from_fork+0x35/0x40
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux source package in Disco:
New
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1824690] Re: proc_thermal flooding dmesg
@colin-king, I tried your kernel and it works! Currently I am running linux-generic-hwe-18.04-edge kernel 5.0.0-20-generic and you're version now lags behind. Can this be integrated onto kernel 5.0? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1824690 Title: proc_thermal flooding dmesg Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Incomplete Bug description: [ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91] [ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91] [ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91] [ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91] [ 31.588851] proc_thermal :00:00.1: Unsupported event [0x91] [ 36.592827] proc_thermal :00:00.1: Unsupported event [0x91] [ 41.572682] random: crng init done [ 41.572690] random: 7 urandom warning(s) missed due to ratelimiting Kernel 4.18.0-18-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1175 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-15 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N24_25GU Package: thermald 1.7.0-5ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= acpi_os_name=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/18/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25GU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25GU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+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 1835322] [NEW] [linux-azure] panic in ext4_resize_fs() found during storage testing
Public bug reported:
A panic was observed during file system testing. The trace is the
following:
[ 8783.243586] kernel BUG at
/build/linux-azure-3iFJ9j/linux-azure-4.18.0/fs/ext4/resize.c:266!
[ 8783.252751] invalid opcode: [#1] SMP PTI
[ 8783.256735] CPU: 7 PID: 39476 Comm: resize2fs Not tainted 4.18.0-1023-azure
#24~18.04.1-Ubuntu
[ 8783.256735] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 8783.256735] RIP: 0010:ext4_resize_fs+0x73b/0xf10
[ 8783.256735] Code: 50 ff ff ff 41 8b 75 10 4d 8b 65 00 85 f6 0f 94 c0 4d 85
e4 0f 94 c1 09 c8 83 bd 5c ff ff ff 01 7e 48 84 c0 0f 84 43 06 00 00 <0f> 0b 48
c7 c2 68 a7 8d 8f 48 c7 c6 00 fb 88 8f 4c 89 f7 e8 0d f8
[ 8783.256735] RSP: 0018:984e8dce7cb0 EFLAGS: 00010202
[ 8783.256735] RAX: 00205c01 RBX: 001f RCX:
[ 8783.256735] RDX: 8b1dbe1367d0 RSI: RDI:
[ 8783.256735] RBP: 984e8dce7d88 R08: 984e8dce7d4c R09: 984e8dce7d54
[ 8783.256735] R10: 0120 R11: 0001 R12: 8b1dbe136800
[ 8783.256735] R13: 8b1d74aefe80 R14: 8b1dbdeb9000 R15:
[ 8783.256735] FS: 7f213fed30c0() GS:8b1ded7c()
knlGS:
[ 8783.256735] CS: 0010 DS: ES: CR0: 80050033
[ 8783.256735] CR2: 556aa08ae9b8 CR3: 001b8e324005 CR4: 003606e0
[ 8783.256735] DR0: DR1: DR2:
[ 8783.256735] DR3: DR6: fffe0ff0 DR7: 0400
[ 8783.256735] Call Trace:
[ 8783.256735] ? security_capable+0x3c/0x60
[ 8783.256735] ext4_ioctl+0xf91/0x14d0
[ 8783.256735] ? audit_filter_rules.constprop.14+0x325/0xf90
[ 8783.256735] ? audit_filter_rules.constprop.14+0x24b/0xf90
[ 8783.256735] do_vfs_ioctl+0xa8/0x630
[ 8783.256735] ksys_ioctl+0x75/0x80
[ 8783.256735] __x64_sys_ioctl+0x1a/0x20
[ 8783.256735] do_syscall_64+0x6a/0x1a0
[ 8783.256735] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 8783.256735] RIP: 0033:0x7f213f3825d7
[ 8783.256735] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48
[ 8783.256735] RSP: 002b:7ffe8effd688 EFLAGS: 0246 ORIG_RAX:
0010
[ 8783.256735] RAX: ffda RBX: 556aa08aa980 RCX: 7f213f3825d7
[ 8783.256735] RDX: 7ffe8effd7d0 RSI: 40086610 RDI: 0004
[ 8783.256735] RBP: 0004 R08: R09:
[ 8783.256735] R10: R11: 0246 R12: 556aa08ac980
[ 8783.256735] R13: 7ffe8effd7d0 R14: 556aa08a92d0 R15:
This issue is resolved by the following upstream commit:
f96c3ac8dfc2 ("ext4: fix crash during online resizing")
Commit f96c3ac8dfc2 is in mainline as of v5.1-rc1. This commit was requested
in the upstream stable kernels. However, the Ubuntu kernels are EOL upstream.
Please include this commit in the 16.04 and 18.04 linux-azure kernels.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1835322
Title:
[linux-azure] panic in ext4_resize_fs() found during storage testing
Status in linux-azure package in Ubuntu:
New
Bug description:
A panic was observed during file system testing. The trace is the
following:
[ 8783.243586] kernel BUG at
/build/linux-azure-3iFJ9j/linux-azure-4.18.0/fs/ext4/resize.c:266!
[ 8783.252751] invalid opcode: [#1] SMP PTI
[ 8783.256735] CPU: 7 PID: 39476 Comm: resize2fs Not tainted
4.18.0-1023-azure #24~18.04.1-Ubuntu
[ 8783.256735] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 8783.256735] RIP: 0010:ext4_resize_fs+0x73b/0xf10
[ 8783.256735] Code: 50 ff ff ff 41 8b 75 10 4d 8b 65 00 85 f6 0f 94 c0 4d 85
e4 0f 94 c1 09 c8 83 bd 5c ff ff ff 01 7e 48 84 c0 0f 84 43 06 00 00 <0f> 0b 48
c7 c2 68 a7 8d 8f 48 c7 c6 00 fb 88 8f 4c 89 f7 e8 0d f8
[ 8783.256735] RSP: 0018:984e8dce7cb0 EFLAGS: 00010202
[ 8783.256735] RAX: 00205c01 RBX: 001f RCX:
[ 8783.256735] RDX: 8b1dbe1367d0 RSI: RDI:
[ 8783.256735] RBP: 984e8dce7d88 R08: 984e8dce7d4c R09:
984e8dce7d54
[ 8783.256735] R10: 0120 R11: 0001 R12:
8b1dbe136800
[ 8783.256735] R13: 8b1d74aefe80 R14: 8b1dbdeb9000 R15:
[ 8783.256735] FS: 7f213fed30c0() GS:8b1ded7c()
knlGS:
[ 8783.256735] CS: 0010 DS: ES: CR0: 80050033
[ 8783.256735] CR2: 556aa08ae9b8 CR3: 001b8e324005 CR4:
003606e0
[
[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
Seems I used wrong kernel for previous test. Sorry. This new kernel works, but xorg doesn't start. I'm testing on Lubuntu xenial. How to add "Xenial" under the "Bionic" on the top of this thread? -- 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/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: NOTE: Boot problems on TWO different laptops after Software Updater updated to kernel 4.15.0-48 Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu desktop. Both fresh installs from minimal CD in early April, originally kernel 0.4.15.0-47, both working fine. Bug report filed on THIS MACHINE: HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel integrated graphics controller GM965/GL960 (with kernel command line parameter ¨video=SVIDEO-1:d¨) SYMPTOM: 4.15.0-48 requires a second ´recovery´ boot to get it up and running. Will not boot properly after a normal shutdown - screen goes funny and it hangs Does boot successfully after a hard shutdown - detects improper shutdown, loads grub menu, then boot successfully Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48 Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots normally after a normal shutdown) OTHER MACHINE: Even older!!! ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility Radeon 9600 GPU. Running with command line parameter "forcepae". SYMPTOM: Won't boot at all. Was working fine under 4.15.0-47 as originally installed, until software updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I can't even get into the grub menu to try the older kernel. More Info on what I've already tried for troubleshooting (on the HP6710b) is outlined in https://answers.launchpad.net/ubuntu/+question/680486 Happy to provide more info if needed, but I'm just an end user user and new to Linux, so will be on a learning curve at this end. (and apologies in advance if this a user problem, and not an actual bug). Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1681 F pulseaudio CurrentDesktop: XFCE Date: Mon May 6 21:16:34 2019 MachineType: Hewlett-Packard HP Compaq 6710b PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DDU Ver. F.13 dmi.board.name: 30C0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.2E dmi.chassis.asset.tag: SGH8080272 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 6710b dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael1034 F pulseaudio /dev/snd/controlC0: michael1034 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c00f Logitech, Inc. MouseMan Traveler/Mobile Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. W1N Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=5e6f46b1-73a8-4779-bc20-414a46286723 ro forcepae quiet splash
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-hwe source package in Bionic: Fix Released Status in mutter source package in Bionic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-hwe source package in Disco: Invalid Status in mutter source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in linux-hwe source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] Low, it should fix vmwgfx and stop using the wrong clock. A test kernel (pre-sru) has been made available to impact users for them to test and conclude it works. It does work as expected, and no regression has been found during the pre-sru testing phase. As per commit description: " This should be transparent to to user space, as long as it doesn't compare the time against the result of gettimeofday(). " [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze
[Kernel-packages] [Bug 1834891] Re: linux-gcp: 5.0.0-1011.11 -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 -- kernel-stable-master-bug: 1834902 - phase: Ready for Packaging - phase-changed: Tuesday, 02. July 2019 14:03 UTC + phase: Packaging + phase-changed: Wednesday, 03. July 2019 23:04 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded 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/1834891 Title: linux-gcp: 5.0.0-1011.11 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New 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: 1834902 phase: Packaging phase-changed: Wednesday, 03. July 2019 23:04 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
bionic-proposed confirmation: I have tested the updates in bionic-proposed with the VM I created for this bug as described in comment #63 and can confirm this, like the test in comment #75, also resolves the issue. The login screen appears as expected after reboot (with kernel and updated packages for gir1.2-mutter-2, gnome-shell, gnome-shell-common, & libmutter-2-0). uname -a before: Linux test-vm 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux uname -a after: Linux test-vm 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-hwe source package in Bionic: Fix Released Status in mutter source package in Bionic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-hwe source package in Disco: Invalid Status in mutter source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in linux-hwe source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] Low, it should fix vmwgfx and stop using the wrong clock. A test kernel (pre-sru) has been made available to impact users for them to test and conclude it works. It does work as expected, and no regression has been found during the pre-sru testing phase. As per commit description: " This should be transparent to to user space, as long as it doesn't compare the time against the result of gettimeofday(). " [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA
[Kernel-packages] [Bug 1834891] Re: linux-gcp: 5.0.0-1011.11 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 5.0.0-1011.11 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- 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/1834891 Title: linux-gcp: 5.0.0-1011.11 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New 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: 1834902 phase: Ready for Packaging phase-changed: Tuesday, 02. July 2019 14:03 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+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 1834936] Re: linux-gcp: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-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 backports: bug 1834935 (xenial/linux-gcp) derivatives: bug 1834931 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Promote to Proposed - phase-changed: Wednesday, 03. July 2019 14:37 UTC + phase: Testing + phase-changed: Wednesday, 03. July 2019 22:37 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 + 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834936 Title: linux-gcp: 4.15.0-1037.39 -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-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: Confirmed 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: New 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 1834935 (xenial/linux-gcp) derivatives: bug 1834931 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 03. July 2019 22:37 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 verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834936/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Have the same issue for quite some time. Couldn't find any pattern yet. Also have the impression gdm is waiting for something. It happens for me when I am on Ethnernet as well when on wifi. Have Dell XPS13 with Ubuntu 18.04.2, kernel 4.18.0-25-generic. Found today dozens in syslog: /usr/lib/gdm3/gdm-x-session[475]: (II) systemd-logind: got pause for 13:67 -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero
[Kernel-packages] [Bug 1833962] Re: linux-oem: 4.15.0-1045.50 -proposed tracker
overriding testing, as the changes in this re-spin came from master and it was tested already, so overriding should be safe ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- 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/1833962 Title: linux-oem: 4.15.0-1045.50 -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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1833987 phase: Holding before Release phase-changed: Wednesday, 03. July 2019 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833962/+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 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1833987 - phase: Promote to Proposed - phase-changed: Wednesday, 03. July 2019 21:03 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 03. July 2019 21:33 UTC reason: - promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building - promote-to-proposed: Pending -- packages copied to Signing signed:building + promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed 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/1835112 Title: linux-fips: 4.15.0-1011.12 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug 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: 1833987 phase: Holding before Promote to Proposed phase-changed: Wednesday, 03. July 2019 21:33 UTC reason: promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+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 1833962] Re: linux-oem: 4.15.0-1045.50 -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: 1833987 - phase: Ready for Testing - phase-changed: Thursday, 27. June 2019 15:09 UTC + phase: Holding before Release + phase-changed: Wednesday, 03. July 2019 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present variant: debs -- 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/1833962 Title: linux-oem: 4.15.0-1045.50 -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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1833987 phase: Holding before Release phase-changed: Wednesday, 03. July 2019 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833962/+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 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) 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/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+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 1834899] Re: linux-gcp: 4.18.0-1016.17 -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 1834896 (bionic/linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1834904 - phase: Ready for Packaging - phase-changed: Tuesday, 02. July 2019 16:05 UTC + phase: Packaging + phase-changed: Wednesday, 03. July 2019 21:05 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded 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/1834899 Title: linux-gcp: 4.18.0-1016.17 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: New 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 1834896 (bionic/linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1834904 phase: Packaging phase-changed: Wednesday, 03. July 2019 21:05 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834899/+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 1834936] Re: linux-gcp: 4.15.0-1037.39 -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 1834935 (xenial/linux-gcp) derivatives: bug 1834931 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Promote to Proposed phase-changed: Wednesday, 03. July 2019 14:37 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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/1834936 Title: linux-gcp: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: New 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 1834935 (xenial/linux-gcp) derivatives: bug 1834931 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Promote to Proposed phase-changed: Wednesday, 03. July 2019 14:37 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834936/+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 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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: 1833987 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 03. July 2019 05:33 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 03. July 2019 21:03 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building + promote-to-proposed: Pending -- packages copied to Signing signed:building 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/1835112 Title: linux-fips: 4.15.0-1011.12 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug 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: 1833987 phase: Promote to Proposed phase-changed: Wednesday, 03. July 2019 21:03 UTC reason: promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+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 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+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 1834899] Re: linux-gcp: 4.18.0-1016.17 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.18.0-1016.17 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- 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/1834899 Title: linux-gcp: 4.18.0-1016.17 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: New 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 1834896 (bionic/linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1834904 phase: Packaging phase-changed: Wednesday, 03. July 2019 21:05 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834899/+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 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker
** Tags added: kernel-block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835112 Title: linux-fips: 4.15.0-1011.12 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug 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: 1833987 phase: Promote to Proposed phase-changed: Wednesday, 03. July 2019 21:03 UTC reason: promote-signing-to-proposed: Ongoing -- builds not complete in Signing signed:building promote-to-proposed: Pending -- packages copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+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 1835110] Re: linux: -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 1835108 (pc-kernel), bug 1835109 (pc-lowlatency- - kernel), bug 1835112 (linux-fips) + derivatives: bug 1835109 (pc-lowlatency-kernel), bug 1835112 (linux- + fips) -- swm properties -- phase: Ready for Packaging phase-changed: Tuesday, 02. July 2019 20:12 UTC reason: prepare-package: Pending -- version not specified variant: debs ** 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 1835109 (pc-lowlatency-kernel), bug 1835112 (linux- - fips) + derivatives: bug 1835112 (linux-fips) -- swm properties -- phase: Ready for Packaging phase-changed: Tuesday, 02. July 2019 20:12 UTC reason: prepare-package: Pending -- version not specified 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/1835110 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 1835112 (linux-fips) -- swm properties -- phase: Ready for Packaging phase-changed: Tuesday, 02. July 2019 20:12 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835110/+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
