[Kernel-packages] [Bug 1842059] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1842059 Title: shiftfs: mark kmem_cache as reclaimable Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: Shiftfs does not mark it's slab cache as reclaimable. While this is not a big deal it is not nice to the kernel in general. The shiftfs cache is not so important that it can't be reclaimed. Regression Potential: Limited to shiftfs. This patch has been tested for multiple days and has not caused any regressions. Test Case: Open a lot of files in shiftfs to get them into the cache and then cause memory pressure via e.g. stress-ng and see if the shiftfs cache shrinks. Target Kernels: All LTS kernels with shiftfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842059/+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 1842774] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1842774 Title: Enhanced Hardware Support - Finalize Naming Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in qemu source package in Bionic: In Progress Status in linux source package in Disco: Fix Released Status in qemu source package in Disco: In Progress Bug description: @SRU Team: For SRU template of Qemu please scroll down ... SRU Justification Kernel: = [Impact] * Add / activate support for IBM z15 and LinuxONE III systems [Fix] * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support for IBM z15 machines" [Test Case] * check and verify cpuinfo - regression testing is possible by Canonical/me * functional testing is currently only doable by IBM [Regression Potential] * There is regression potential with having new code in and the flags added/active * but the code changes are pretty straight forward, just add config, cases and defs * and are not used on existing systems, just on the new generation that is not yet out in the field [Other Info] * SRU of LP 1842916 merged with (this) LP 1842774 --- SRU Template for qemu as the impact/scope is different == [Impact] * Update naming of the new HW Generation * Now that the systems are released people might look for types matching the name and no one really knows "IBM 8561 GA1". * Help users to identify the cpu type by backporting the fix that sets the defined name. [Fix] * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca [Test Case] * qemu-system-s390x -cpu ? | grep gen15 s390 gen15a-base IBM 8561 GA1(static, migration-safe) s390 gen15a IBM 8561 GA1(migration-safe) s390 gen15b-base IBM 8562 GA1(static, migration-safe) s390 gen15b IBM 8562 GA1(migration-safe) * With the fix gen15a should be called "IBM z15 GA1" [Regression Potential] * The only thing changing (for qemu) are some texts e.g. when showing CPU types. The cpu type itself that is used in e.g. scripts / commands will not change. Therefore the regression risk of the qemu change is next to none. The only I can think of is people grepping for the old ID in text output, but that seems theoretical and not important. [Other Info] * For an SRU perspective this is "nice to have" we will only do this "along" other higher impact SRUs. __ This feature request will provide the final naming of the next machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842774/+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 1838886] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1838886 Title: New ID in ums-realtek module breaks cardreader Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Bug description: === SRU Justification === [Impact] Some ums-realtek card readers may dropped from USB bus after using ums-realtek driver instead of usb-storage generic driver. [Fix] Disable auto-delink on new ums-realtek devices, only whitelist three oldest IDs. [Test] Affected user and myself confirmed disabling auto-delink works. [Regression Potential] Minimal. Limited to one specific driver and this also restore the old behavior. === Original Bug Report === When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber: 2012092657120 [3.911571] usbcore: registered new interface driver usb-storage [3.914796] usbcore: registered new interface driver uas [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.924478] scsi host2: usb-storage 1-5.1:1.0 [3.924649] usbcore: registered new interface driver ums-realtek [...] [ 13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 13.509592] scsi host2: usb-storage 1-5.1:1.0 [ 14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 170.961728] scsi 2:0:0:0: rejecting I/O to dead device [ 170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 170.962073] scsi 2:0:0:0: [sdb] Sense not available. [ 171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd [ 172.194299] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 172.194327] usb 1-5.1: Product: USB2.0-CRW [ 172.194338] usb 1-5.1: Manufacturer: Generic [ 172.194346] usb 1-5.1: SerialNumber: 2012092657120 [ 172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 172.212503] scsi host2: usb-storage 1-5.1:1.0 [ 173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 329.654468] usb 1-5.1: USB disconnect, device number 8 [ 329.665905] scsi 2:0:0:0: rejecting I/O to dead device [ 329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 329.665976] scsi 2:0:0:0: [sdb] Sense not available. [ 330.701685] usb 1-5.1: new high-speed USB device
[Kernel-packages] [Bug 1838751] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-bluefield
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1838751
Title:
Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards)
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Status in linux-oem-osp1 source package in Disco:
Fix Released
Bug description:
[Impact]
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
with 1 MB BAR size fails to initialize during system resume from S3
sleep.
As per our findings the issue is caused by the below upstream commit:
d3252ace0bc652a1a24446b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
We see that the same commit has been ported to UBUNTU18.X - PCI:
Restore resized BAR state on resume (bsc#1105355).
the fix has been submitted to upstream
https://patchwork.kernel.org/patch/11058689/
please include this patch in the upcoming releases.please let me know
if additional information required.
https://bugzilla.kernel.org/show_bug.cgi?id=203939
[Test case]
See that suspend/resume works correctly after applying the patch
[Regression potential]
slim, itself fixes a regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838751/+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 1841977] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1841977 Title: shiftfs: drop entries from cache on unlink Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: LXD on Ubuntu runs on top of zfs by defaults. Users that make use of shiftfs for efficient id-shifting currently hit a bug where zfs is confused about the amount of space that is used in a dataset. For example, creating a file with 1GB of random data will increase the space used by the dataset by 1GB. When the file is removed via rm the space is not freed for zfs. This leads to zfs running out of space pretty quickly. This bug has been observed, described, and reproduced here https://discuss.linuxcontainers.org/t/trying-out-shiftfs/5155/9 . Stéphane Graber observed related issues. Regression Potential: Limited to shiftfs. This patch has been tested on various backends btrfs, dir, zfs to verify that it doesn't regress other workloads. Shiftfs now also aligns more closely with overlayfs on file deletion. Test Case: sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo systemctl restart snap.lxd.daemon sudo lxd init # make sure to select zfs as backend sudo lxc launch images:ubuntu/bionic b1 sudo lxc exec b1 -- dd if=/dev/urandom bs=1M count=1000 of=dummy.file sudo zfs list default/containers/b1 # will show +1GB sudo lxc exec b1 -- rm dummy.file sudo zfs list default/containers/b1 # will show +1GB on a non-fixed kernel and -1GB on a fixed kernel Target Kernels: All LTS kernels with shiftfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841977/+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 1836912] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1836912 Title: ipv4: enable route flushing in network namespaces Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: Tools such as vpnc try to flush routes when run inside network namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This currently does not work because flush is not enabled in non-initial network namespaces. Users have complained about this at various times (cf. Link: https://github.com/lxc/lxd/issues/4257). Fix: Enable /proc/sys/net/ipv4/route/flush inside non-initial network namespaces. Regression Potential: None, since this didn't use to work before. Since routes are per network namespace it is safe to enable /proc/sys/net/ipv4/route/flush in there. Test Case: Tested with LXD on a kernel with the patch applied and by running vpnc successfully. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cdda5f1d6adde02da591ca2196f20289977dc56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836912/+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 1842265] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1842265 Title: No sound inputs from the external microphone and headset on a Dell machine Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] When we plug an external mic/headset-mic, the system can't detect it and as a result can't record sound from it. [Fix] Apply an existing fixup to fix this issue. [Test Case] After applying the patch, plug an external mic or headset-mic, system can detect it and can record the sound from it too. [Regression Risk] Low. just add an existing fixup to this new machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1842265/+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 1836261] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1836261 Title: xfrm interface: several kernel panic Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1836261 [Impact] Upstream has recently received a number of bug fixes that resolve kernel panics, memory leaks, and list handling for virtual xfrm interfaces that were debuted in 4.19. [Test Case] 3 of the 5 patches have test cases in their commit message for reproducing the fault they address. Another patch prevents including a stale name in the log files. And the other patch that doesn't have an explicit test case improves list handling. [Regression Potential] This patchset contains a nontrivial amount of changes. However, the heavier patches contain test cases that they resolve the regressions they were created for. They've been upstream since July and I don't see any follow up Fixes commits targeting these. The blast radius is "only" the xfrm interface but this is smoke tested and if any dependents rely on it for core functionality they might exercise it and would possibly notice any issues by now as well. Original bug description follows: There was several problems reported upstream: 1/ 56c5ee1a5823: xfrm interface: fix memory leak on creation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=56c5ee1a5823 2/ xfrm interface: avoid corruption on changelink http://patchwork.ozlabs.org/patch/1130240/ 3/ xfrm interface: ifname may be wrong in logs http://patchwork.ozlabs.org/patch/1130241/ 4/ xfrm interface: fix list corruption for x-netns http://patchwork.ozlabs.org/patch/1130385/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836261/+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 1850799] Re: bionic/linux-oem: -proposed tracker
** Summary changed: - linux-oem: -proposed tracker + bionic/linux-oem: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** 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: 1849855 + packages: + lrm: linux-restricted-modules-oem + main: linux-oem + meta: linux-meta-oem + signed: linux-signed-oem + phase: Ready for Packaging + phase-changed: Thursday, 31. October 2019 14:20 UTC + reason: + prepare-package: Pending -- version not specified replaces: bug 1849012 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/1850799 Title: bionic/linux-oem: -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: Confirmed Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-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-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 -- kernel-stable-master-bug: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Packaging phase-changed: Thursday, 31. October 2019 14:20 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1849012 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850799/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1849012 + bionic/linux-oem: bug 1850799, bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799, bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1843644] Re: touchpad not working on LHMZNIY Yepbook
It is done. Do my bug will be treated on this platform ? -- 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/1843644 Title: touchpad not working on LHMZNIY Yepbook Status in linux package in Ubuntu: Confirmed Bug description: Fresh install, but the touchpad isn't showing in the device list at all.And it perfectly work on Windows. Device list attached. Works ok if you attach a mouse. ProblemType: Bug Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 21:40:32 2019 InstallationDate: Installed on 2019-09-10 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: quentin1138 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-17 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Insyde Braswell Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=f12f1e0c-114b-401a-9a27-af7ccef1c0b6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-27-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/25/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: E115C.intel.C005 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrE115C.intel.C005:bd05/25/2016:svnInsyde:pnBraswell:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: Braswell dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843644/+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 1843487] Re: UIO: mutex used in interrupt handler causes crash
@Kamal yes this seems to fix it. I was able to run my device stress test for over 15 minutes. With the bug I was lucky if I could make it 15 seconds. -- 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/1843487 Title: UIO: mutex used in interrupt handler causes crash Status in linux package in Ubuntu: In Progress Bug description: Running: Bionic Beaver Ubuntu 4.15.0-62.69-generic 4.15.18 Problem since: Ubuntu-4.15.0-59.66 In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to uio_interrupt. This results in a "scheduling while atomic" error if someone else owns the mutex at the time it is invoked. The following commit in the kernel mainline appears to fix this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3d27c4de8d4fb2d4099ff324671792aa2578c6f9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843487/+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 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
** Changed in: linux-raspi2 (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+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 1850548] Comment bridged from LTC Bugzilla
--- Comment From kuldip.na...@ibm.com 2019-10-31 10:05 EDT--- Hi, Please see the detail information below root@pok1-qz1-sr1-rk005-s10:~# mount | sed -e 's/^//g' /proc on /proc type proc (rw,relatime) /sys on /sys type sysfs (rw,relatime) /dev on /dev type devtmpfs (rw,relatime,size=188307264k,nr_inodes=2942301,mode=755) /dev/pts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) rootfs on / type tmpfs (rw,relatime,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=26,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=23573) debugfs on /sys/kernel/debug type debugfs (rw,relatime) tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=1024M) tmpfs on /var/tmp type tmpfs (rw,relatime) tmpfs on /tmp type tmpfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other) sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=39788672k,mode=700) root@pok1-qz1-sr1-rk005-s10:~# ls -l /boot/ total 91840 -rw--- 1 root root 3661770 Oct 8 18:31 System.map-4.15.0-1039-ibm-gt -rw-r--r-- 1 root root 192377 Oct 8 18:31 config-4.15.0-1039-ibm-gt drwxr-xr-x 5 root root 160 Oct 8 18:31 grub lrwxrwxrwx 1 root root 29 Oct 8 18:31 initrd.img -> initrd.img-4.15.0-1039-ibm-gt -rw-r--r-- 1 root root 53903653 Oct 8 18:31 initrd.img-4.15.0-1039-ibm-gt -rw-r--r-- 1 root root 11537139 Oct 8 18:31 initrd.img-4.15.0-65-generic lrwxrwxrwx 1 root root 29 Oct 8 18:31 initrd.img.old -> initrd.img-4.15.0-1039-ibm-gt lrwxrwxrwx 1 root root 26 Oct 8 18:31 vmlinux -> vmlinux-4.15.0-1039-ibm-gt -rw--- 1 root root 24595712 Oct 8 18:31 vmlinux-4.15.0-1039-ibm-gt lrwxrwxrwx 1 root root 26 Oct 8 18:31 vmlinux.old -> vmlinux-4.15.0-1039-ibm-gt root@pok1-qz1-sr1-rk005-s10:~# ls -l /boot/ total 91840 -rw--- 1 root root 3661770 Oct 8 18:31 System.map-4.15.0-1039-ibm-gt -rw-r--r-- 1 root root 192377 Oct 8 18:31 config-4.15.0-1039-ibm-gt drwxr-xr-x 5 root root 160 Oct 8 18:31 grub lrwxrwxrwx 1 root root 29 Oct 8 18:31 initrd.img -> initrd.img-4.15.0-1039-ibm-gt -rw-r--r-- 1 root root 53903653 Oct 8 18:31 initrd.img-4.15.0-1039-ibm-gt -rw-r--r-- 1 root root 11537139 Oct 8 18:31 initrd.img-4.15.0-65-generic lrwxrwxrwx 1 root root 29 Oct 8 18:31 initrd.img.old -> initrd.img-4.15.0-1039-ibm-gt lrwxrwxrwx 1 root root 26 Oct 8 18:31 vmlinux -> vmlinux-4.15.0-1039-ibm-gt -rw--- 1 root root 24595712 Oct 8 18:31 vmlinux-4.15.0-1039-ibm-gt lrwxrwxrwx 1 root root 26 Oct 8 18:31 vmlinux.old -> vmlinux-4.15.0-1039-ibm-gt root@pok1-qz1-sr1-rk005-s10:~# ls -l /lib/modules total 0 drwxr-xr-x 6 root root 360 Oct 30 17:28 4.15.0-1039-ibm-gt root@pok1-qz1-sr1-rk005-s10:~# ls -ld /var/lib/kdump drwxr-xr-x 3 root root 120 Oct 30 20:05 /var/lib/kdump root@pok1-qz1-sr1-rk005-s10:~# ls -ld /var/crash drwxrwxrwt 2 root root 80 Oct 30 20:05 /var/crash -- You received this bug notification because you are a member of Kernel Packages, which is
[Kernel-packages] [Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering
Today I noticed when I start my system with the other kernel 5.0.0-32-generic #34-Ubuntu there are no problem regarding the mouse movement (WiFi was activated) -- 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/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 19.10). For example: When I want to go to a button the cursor sometimes stops on the way to it and moves on milliseconds later. In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is not present. Please let me now if I can add some further information. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 All available system updates were installed. No extensions added additionally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 06:23:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-20 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
The testcase here doesn't seem to be working (or, rather, failing) for me, which makes it harder to investigate this. It passes on both sid and eoan for me: (sid-amd64)root@nosferatu:~# dpkg -l \*klibc\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii klibc-utils2.0.7-1 amd64small utilities built with klibc for early boot ii libklibc:amd64 2.0.7-1 amd64minimal libc subset for use with initramfs (sid-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop0 /dev/loop0 (sid-amd64)root@nosferatu:~# (eoan-amd64)root@nosferatu:~# dpkg -l \*klibc\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--=== ii klibc-utils2.0.6-1ubuntu2 amd64small utilities built with klibc for early boot ii libklibc:amd64 2.0.6-1ubuntu2 amd64minimal libc subset for use with initramfs (eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop0 /dev/loop0 (eoan-amd64)root@nosferatu:~# -- 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1849051] Re: xenial/linux: 4.4.0-167.196 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 16:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 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/1849051 Title: xenial/linux: 4.4.0-167.196 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 16:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** Patch added: "save-argc.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850184/+attachment/5301773/+files/save-argc.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: New Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: New Bug description: http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 I have tried the v3d.ko with latest stable version of mesa 19.2 Which works well. glxinfo is the application to show everything is working and it produces ...Accelerated: yes for a fast graphical interface However Chromium 78.0.3904.70 snap fails for some reason I am using a workaround until it is fixed chromium -use-gl=egl The chromium-browser 76.0.3809.100 (from ubuntu 19.04) worked OK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+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 1850548] Comment bridged from LTC Bugzilla
--- Comment From kuldip.na...@ibm.com 2019-10-31 10:20 EDT--- I thought a lot about it and I think this problem will come in any time the m/c is network booted and diskless. So in a way it is still generic and not IBM specific. Based on this I now have second thought on if we should really close this. Can kdump-tools be extended to take care of the diskless workstations. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1850548 Title: Unable to install kdump tools: post install script returning fail Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: ---Problem Description--- Unable to install Kdump-tools. ---Steps to Reproduce--- Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb Note: Unable to install the Kdump-tool. The problem comes when postinst script is run: root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash [0.00] Kernel command line: imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz XCAT=192.168.0.2:3001 XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 transparent_hugepage=never intel_iommu=on iommu=pt cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt ds=nocloud crashkernel=768M,low crashkernel=4G,high Error: = update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz because associated file /usr/share/man/man1/bsd-write.1.gz (of link group write) doesn't exist^M update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) doesn't exist^M Setting up ifenslave (2.9ubuntu1) ...^M Setting up file (1:5.32-2ubuntu0.2) ...^M Setting up kdump-tools (1:1.6.3-2) ...^M ^M Creating config file /etc/default/kdump-tools with new version^M dpkg: error processing package kdump-tools (--configure):^M installed kdump-tools package post-installation script subprocess returned error exit status 1^M dpkg: dependency problems prevent configuration of linux-crashdump:^M linux-crashdump depends on kdump-tools; however:^M Package kdump-tools is not configured yet.^M ^M Detail Log: === root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic1_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up file (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i bsdmainutils_11.1.2ubuntu1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ... Setting up bsdmainutils (11.1.2ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb ... Unpacking makedumpfile (1:1.6.5-1ubuntu1~18.04.1) over (1:1.6.5-1ubuntu1~18.04.1) ... Setting up makedumpfile (1:1.6.5-1ubuntu1~18.04.1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack
[Kernel-packages] [Bug 1850443] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301819/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
So, I'm not sure if this is a kernel headers/assembly bug (as ioctl is used from there), gcc-9 bug, or the combination of the two. I'm going to save argc, and use a saved copy for now, but this needs deeper analysis. This sounds like a retpoline mitigation. ** Also affects: klibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: klibc (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: New Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: New Bug description: http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1850184] 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 1850184 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 Eoan) 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * sudo /usr/lib/klibc/bin/losetup -vf should not fail, and should print next available free loop device [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** Description changed: + [Impact] + + * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. + + [Test Case] + + * sudo /usr/lib/klibc/bin/losetup -vf + +should not fail, and should print next available free loop device + + [Regression Potential] + + * klibc is quite special, as it uses linux kernel headers/assembly. It + seems like there is incompatibility between klibc sources, and gcc-9 + with linux-5.3 when used to build userspace programmes. + + * disabling cf-protection and stack-clash-protection did not help. + + * building with gcc-8 does not exhibit the problem. + + * the workaround is quite simple in the code, keep a copy of argc to + compare to it later in the code. + + [Other Info] + + * Original bug report + http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address - BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * sudo /usr/lib/klibc/bin/losetup -vf should not fail, and should print next available free loop device [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1850799] [NEW] bionic/linux-oem: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Packaging phase-changed: Thursday, 31. October 2019 14:20 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1849012 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.10.21-4 kernel-sru-derivative-of-1849855 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team
[Kernel-packages] [Bug 1850548] Comment bridged from LTC Bugzilla
--- Comment From kuldip.na...@ibm.com 2019-10-31 10:11 EDT--- This problem will be seen ion any of the diskless workstation; Please note as I see there are three places which are of concern /var/lib/dpkg/info/kdump-tools.postinst fails because: 1. It cannot make the initrd image because of wrong values set in /etc/initramfs-tools/initramfs.conf a) Post installation script calls /etc/kernel/postinst.d/kdump-tools which does not sets the tag to "Modules=most" in /etc/initramfs-tools/initramfs.conf b) Post installation script does not set the tag BusyBox=y in /etc/initramfs-tools/initramfs.conf. 2. It runs update-grub. This fails with the below message # update-grub /usr/sbin/grub-probe: error: failed to get canonical path of `rootfs' Disabling it I could proceed. 3. Even after making all these changes, it failed to start the kdump-tools-dump.service. Please see below: + deb-systemd-invoke start kdump-tools-dump.service kdump-tools-dump.service is a disabled or a static unit, not starting it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1850548 Title: Unable to install kdump tools: post install script returning fail Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: ---Problem Description--- Unable to install Kdump-tools. ---Steps to Reproduce--- Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb Note: Unable to install the Kdump-tool. The problem comes when postinst script is run: root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash [0.00] Kernel command line: imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz XCAT=192.168.0.2:3001 XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 transparent_hugepage=never intel_iommu=on iommu=pt cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt ds=nocloud crashkernel=768M,low crashkernel=4G,high Error: = update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz because associated file /usr/share/man/man1/bsd-write.1.gz (of link group write) doesn't exist^M update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) doesn't exist^M Setting up ifenslave (2.9ubuntu1) ...^M Setting up file (1:5.32-2ubuntu0.2) ...^M Setting up kdump-tools (1:1.6.3-2) ...^M ^M Creating config file /etc/default/kdump-tools with new version^M dpkg: error processing package kdump-tools (--configure):^M installed kdump-tools package post-installation script subprocess returned error exit status 1^M dpkg: dependency problems prevent configuration of linux-crashdump:^M linux-crashdump depends on kdump-tools; however:^M Package kdump-tools is not configured yet.^M ^M Detail Log: === root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic1_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up file (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i bsdmainutils_11.1.2ubuntu1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ...
[Kernel-packages] [Bug 1845716] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1845716 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: Confirmed Bug description: - ProblemType: Package DistroRelease: Ubuntu 19.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 27 23:20:40 2019 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2017-10-07 (720 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1845716/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1850799, bug 1849012 + bionic/linux-oem: bug 1849012, bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1849012, bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850443] AlsaInfo.txt
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301810/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301814/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301812/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] Re: Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb3553 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2018-06-18 (500 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc.
Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HRCTO1WW
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
RelatedPackageVersions:
linux-restricted-modules-5.3.0-19-generic N/A
linux-backports-modules-5.3.0-19-generic N/A
linux-firmware1.183.1
Tags: eoan
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-26 (5 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd netdev plugdev sambashare sudo
video
_MarkForUpload: True
dmi.bios.date: 09/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET57W (1.42 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN1MET57W(1.42):bd09/03/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HRCTO1WW
dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO
** Tags added: apport-collected 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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301811/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1843487] Re: UIO: mutex used in interrupt handler causes crash
@Tom Sounds like a winner to me! I've submitted the patch to our process pipeline: https://lists.ubuntu.com/archives/kernel-team/2019-October/105155.html A post will appear here once it lands in a production Bionic kernel (most likely in our next three-week cycle, around 18-Nov). Thanks again for doing the leg-work on this! ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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/1843487 Title: UIO: mutex used in interrupt handler causes crash Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Running: Bionic Beaver Ubuntu 4.15.0-62.69-generic 4.15.18 Problem since: Ubuntu-4.15.0-59.66 In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to uio_interrupt. This results in a "scheduling while atomic" error if someone else owns the mutex at the time it is invoked. The following commit in the kernel mainline appears to fix this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3d27c4de8d4fb2d4099ff324671792aa2578c6f9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843487/+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 1843622] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1843622 Title: Disco update: upstream stable patchset 2019-09-11 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-09-11 Ported from the following upstream stable releases: v4.19.70, v5.2.12 v4.19.71, v5.2.13 v4.19.72, v5.2.14 from git://git.kernel.org/ dmaengine: ste_dma40: fix unneeded variable warning nvme-multipath: revalidate nvme_ns_head gendisk in nvme_validate_ns afs: Fix the CB.ProbeUuid service handler to reply correctly afs: Fix loop index mixup in afs_deliver_vl_get_entry_by_name_u() fs: afs: Fix a possible null-pointer dereference in afs_put_read() afs: Only update d_fsdata if different in afs_d_revalidate() nvmet-loop: Flush nvme_delete_wq when removing the port nvme: fix a possible deadlock when passthru commands sent to a multipath device nvme-pci: Fix async probe remove race soundwire: cadence_master: fix register definition for SLAVE_STATE soundwire: cadence_master: fix definitions for INTSTAT0/1 auxdisplay: panel: need to delete scan_timer when misc_register fails in panel_attach dmaengine: stm32-mdma: Fix a possible null-pointer dereference in stm32_mdma_irq_handler() omap-dma/omap_vout_vrfb: fix off-by-one fi value iommu/dma: Handle SG length overflow better usb: gadget: composite: Clear "suspended" on reset/disconnect usb: gadget: mass_storage: Fix races between fsg_disable and fsg_set_alt xen/blkback: fix memory leaks arm64: cpufeature: Don't treat granule sizes as strict i2c: rcar: avoid race when unregistering slave client i2c: emev2: avoid race when unregistering slave client drm/ast: Fixed reboot test may cause system hanged usb: host: fotg2: restart hcd after port reset tools: hv: fixed Python pep8/flake8 warnings for lsvmbus tools: hv: fix KVP and VSS daemons exit code watchdog: bcm2835_wdt: Fix module autoload drm/bridge: tfp410: fix memleak in get_modes() scsi: ufs: Fix RX_TERMINATION_FORCE_ENABLE define value drm/tilcdc: Register cpufreq notifier after we have initialized crtc net/tls: swap sk_write_space on close net: tls, fix sk_write_space NULL write when tx disabled ipv6/addrconf: allow adding multicast addr if IFA_F_MCAUTOJOIN is set ipv6: Default fib6_type to RTN_UNICAST when not set net/smc: make sure EPOLLOUT is raised tcp: make sure EPOLLOUT wont be missed ipv4/icmp: fix rt dst dev null pointer dereference mm/zsmalloc.c: fix build when CONFIG_COMPACTION=n ALSA: usb-audio: Check mixer unit bitmap yet more strictly ALSA: line6: Fix memory leak at line6_init_pcm() error path ALSA: hda - Fixes inverted Conexant GPIO mic mute led ALSA: seq: Fix potential concurrent access to the deleted pool ALSA: usb-audio: Fix invalid NULL check in snd_emuusb_set_samplerate() ALSA: usb-audio: Add implicit fb quirk for Behringer UFX1604 kvm: x86: skip populating logical dest map if apic is not sw enabled KVM: x86: Don't update RIP or do single-step on faulting emulation uprobes/x86: Fix detection of 32-bit user mode x86/apic: Do not initialize LDR and DFR for bigsmp ftrace: Fix NULL pointer dereference in t_probe_next() ftrace: Check for successful allocation of hash ftrace: Check for empty hash and comment the race with registering probes usb-storage: Add new JMS567 revision to unusual_devs USB: cdc-wdm: fix race between write and disconnect due to flag abuse usb: hcd: use managed device resources usb: chipidea: udc: don't do hardware access if gadget has stopped usb: host: ohci: fix a race condition between shutdown and irq usb: host: xhci: rcar: Fix typo in compatible string matching USB: storage: ums-realtek: Update module parameter description
[Kernel-packages] [Bug 1843291] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
fsprotect/unknown (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-bluefield
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1843291
Title:
Add -fcf-protection=none when using retpoline flags
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Bug description:
SRU Justification
Impact: Starting in eoan -fcf-protection is enabled by default in gcc,
see https://wiki.ubuntu.com/ToolChain/CompilerFlags. This option is
incompatible with -mindirect-branch, which is used for building
kernels with retpoline support. Building a kernel or dkms modules
fails without the patch, and during upgrade to eoan we can get
failures due to dkms modules failing to build for older kernels with
the new compiler.
Fix: Backport upstream patch to add -fcf-protection=none to kernel
retpoline flags.
Test Case: Upgrade from {bionic,diso} to eoan with dkms modules
installed.
Regression Potential: The patch probes the compiler for support for
-fcf-protection and only adds it if the compiler supports it, and
=none was the default prior to the change in eoan. It's also been
upstream and in eoan for a while now, so it's unlikely to cause any
regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843291/+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 1845390] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845390 Title: Disco update: upstream stable patchset 2019-09-25 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-09-25 Ported from the following upstream stable releases: v4.19.74, v5.2.16 from git://git.kernel.org/ bridge/mdb: remove wrong use of NLM_F_MULTI cdc_ether: fix rndis support for Mediatek based smartphones ipv6: Fix the link time qualifier of 'ping_v6_proc_exit_net()' isdn/capi: check message length in capi_write() ixgbe: Fix secpath usage for IPsec TX offload. net: Fix null de-reference of device refcount net: gso: Fix skb_segment splat when splitting gso_size mangled skb having linear-headed frag_list net: phylink: Fix flow control resolution net: sched: fix reordering issues sch_hhf: ensure quantum and hhf_non_hh_weight are non-zero sctp: Fix the link time qualifier of 'sctp_ctrlsock_exit()' sctp: use transport pf_retrans in sctp_do_8_2_transport_strike tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR tipc: add NULL pointer check before calling kfree_rcu tun: fix use-after-free when register netdev failed gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist gpio: fix line flag validation in linehandle_create Btrfs: fix assertion failure during fsync and use of stale transaction ixgbe: Prevent u8 wrapping of ITR value to something less than 10us genirq: Prevent NULL pointer dereference in resend_irqs() KVM: s390: kvm_s390_vm_start_migration: check dirty_bitmap before using it as target for memset() KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl KVM: x86: work around leak of uninitialized stack contents KVM: nVMX: handle page fault in vmread x86/purgatory: Change compiler flags from -mcmodel=kernel to -mcmodel=large to fix kexec relocation errors powerpc: Add barrier_nospec to raw_copy_in_user() drm/meson: Add support for XBGR & ABGR formats clk: rockchip: Don't yell about bad mmc phases when getting mtd: rawnand: mtk: Fix wrongly assigned OOB buffer pointer issue PCI: Always allow probing with driver_override gpio: fix line flag validation in lineevent_create ubifs: Correctly use tnc_next() in search_dh_cookie() driver core: Fix use-after-free and double free on glue directory crypto: talitos - check AES key size crypto: talitos - fix CTR alg blocksize crypto: talitos - check data blocksize in ablkcipher. crypto: talitos - fix ECB algs ivsize crypto: talitos - Do not modify req->cryptlen on decryption. crypto: talitos - HMAC SNOOP NO AFEU mode requires SW icv checking. firmware: ti_sci: Always request response from firmware drm: panel-orientation-quirks: Add extra quirk table entry for GPD MicroPC drm/mediatek: mtk_drm_drv.c: Add of_node_put() before goto Revert "Bluetooth: btusb: driver to enable the usb-wakeup feature" iio: adc: stm32-dfsdm: fix data type modules: fix BUG when load module with rodata=n modules: fix compile error if don't have strict module rwx platform/x86: pmc_atom: Add CB4063 Beckhoff Automation board to critclk_systems DMI table rsi: fix a double free bug in rsi_91x_deinit() x86/build: Add -Wnoaddress-of-packed-member to REALMODE_CFLAGS, to silence GCC9 build warning ixgbevf: Fix secpath usage for IPsec Tx offload net: fixed_phy: Add forward declaration for struct gpio_desc; net: sock_map, fix missing ulp check in sock hash case Revert "mmc: bcm2835: Terminate timeout work synchronously" mmc: tmio: Fixup runtime PM management during probe mmc: tmio: Fixup runtime PM management during remove drm/i915: Restore relaxed padding
[Kernel-packages] [Bug 1846096] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
*** This bug is a duplicate of bug 1849002 *** https://bugs.launchpad.net/bugs/1849002 All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846096 Title: bionic/linux-bluefield: 5.0.0-1003.12 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846097 packages: main: linux-bluefield meta: linux-meta-bluefield phase: Ready for Testing phase-changed: Wednesday, 23. October 2019 17:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846096/+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 1844722] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1844722 Title: Disco update: upstream stable patchset 2019-09-19 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-09-19 Ported from the following upstream stable releases: v4.19.73, v5.2.15 from git://git.kernel.org/ ALSA: hda - Fix potential endless loop at applying quirks ALSA: hda/realtek - Fix overridden device-specific initialization ALSA: hda/realtek - Add quirk for HP Pavilion 15 ALSA: hda/realtek - Enable internal speaker & headset mic of ASUS UX431FL ALSA: hda/realtek - Fix the problem of two front mics on a ThinkCentre sched/fair: Don't assign runtime for throttled cfs_rq drm/vmwgfx: Fix double free in vmw_recv_msg() vhost/test: fix build for vhost test vhost/test: fix build for vhost test - again batman-adv: fix uninit-value in batadv_netlink_get_ifindex() batman-adv: Only read OGM tvlv_len after buffer len check timekeeping: Use proper ktime_add when adding nsecs in coarse offset selftests: fib_rule_tests: use pre-defined DEV_ADDR powerpc/64: mark start_here_multiplatform as __ref media: stm32-dcmi: fix irq = 0 case scripts/decode_stacktrace: match basepath using shell prefix operator, not regex nvme-fc: use separate work queue to avoid warning modules: always page-align module section allocations kernel/module: Fix mem leak in module_add_modinfo_attrs drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse" drm/vblank: Allow dynamic per-crtc max_vblank_count mfd: Kconfig: Fix I2C_DESIGNWARE_PLATFORM dependencies tpm: Fix some name collisions with drivers/char/tpm.h drm/nouveau: Don't WARN_ON VCPI allocation failures drm: add __user attribute to ptr_to_compat() drm/i915: Handle vm_mmap error during I915_GEM_MMAP ioctl with WC set drm/i915: Sanity check mmap length against object size arm64: dts: stratix10: add the sysmgr-syscon property from the gmac's kvm: mmu: Fix overflow on kvm mmu page limit calculation KVM: x86: Always use 32-bit SMRAM save state for 32-bit kernels media: i2c: tda1997x: select V4L2_FWNODE ext4: protect journal inode's blocks using block_validity ARM: dts: qcom: ipq4019: Fix MSI IRQ type dt-bindings: mmc: Add supports-cqe property dt-bindings: mmc: Add disable-cqe-dcmd property. dm mpath: fix missing call of path selector type->end_io mmc: sdhci-pci: Add support for Intel CML PCI: dwc: Use devm_pci_alloc_host_bridge() to simplify code cifs: smbd: take an array of reqeusts when sending upper layer data drm/amdkfd: Add missing Polaris10 ID kvm: Check irqchip mode before assign irqfd Btrfs: fix race between block group removal and block group allocation cifs: add spinlock for the openFileList to cifsInodeInfo ceph: use ceph_evict_inode to cleanup inode's resource KVM: x86: optimize check for valid PAT value KVM: VMX: Always signal #GP on WRMSR to MSR_IA32_CR_PAT with bad value btrfs: correctly validate compression type dm thin metadata: check if in fail_io mode when setting needs_check bcache: only clear BTREE_NODE_dirty bit when it is set bcache: add comments for mutex_lock(>write_lock) bcache: fix race in btree_flush_write() drm/i915: Make sure cdclk is high enough for DP audio on VLV/CHV virtio/s390: fix race on airq_areas[] drm/atomic_helper: Allow DPMS On<->Off changes for unregistered connectors ext4: don't perform block validity checks on the journal inode ext4: fix block validity checks for journal inodes using indirect blocks ext4: unsigned int compared against zero PCI: Reset both NVIDIA GPU and HDA in ThinkPad P50 workaround gpio: pca953x: correct type of reg_direction
[Kernel-packages] [Bug 1845355] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1845355 Title: Support Hi1620 zip hw accelerator Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to userspace by Ubuntu. [Test Case] ubuntu@scobee:~$ dmesg | grep zip [ 29.688222] hisi_zip :75:00.0: enabling device ( -> 0002) [ 29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002) ubuntu@scobee:~$ lspci | grep ZIP 75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP Engine (rev 21) b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP Engine (rev 21) [Fix] 263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon QM module dfed0098ab91f crypto: hisilicon - add hardware SGL support 62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support 79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP 8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip 72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver 00ae05db583a7 crypto: hisilicon - fix kbuild warnings db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP 5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning 902f0babf5457 crypto: hisilicon - add missing single_release 1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t 62a9d9fc7a210 crypto: hisilicon - Fix return value check in hisi_zip_acompress() bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning [Regression Risk] This is a new driver which will only load automatically on systems that expose a supported PCI device. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1845355/+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 1846097] Autopkgtest regression report (linux-bluefield/5.0.0-1003.12)
All autopkgtests for the newly accepted linux-bluefield (5.0.0-1003.12) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fsprotect/unknown (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1846097 Title: disco/linux: 5.0.0-32.34 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Released 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Complete phase-changed: Monday, 21. October 2019 10:02 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-bluefield: bug 1846096 bionic/linux-hwe: bug 1846092 bionic/linux-oem-osp1: bug 1846095 disco/linux-aws: bug 1846075 disco/linux-azure: bug 1846079 disco/linux-gcp: bug 1846086 disco/linux-kvm: bug 1846087 disco/linux-oracle: bug 1846089 disco/linux-raspi2: bug 1846073 disco/linux-snapdragon: bug 1846091 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846097/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
Ah-ha. If loop0 is in use, then the test-case appropriately fails in both unstable and eoan, which is comforting, as I didn't look forward to figuring out why this works in Debian (it doesn't). -- 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** Description changed: [Impact] - * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. - + * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, + as main(argc) is reset to zero, after ioctl() operations in a function + call, quite unexpectadly. + [Test Case] - * sudo /usr/lib/klibc/bin/losetup -vf - -should not fail, and should print next available free loop device + * $ sudo /usr/lib/klibc/bin/losetup -vf + Loop device is /dev/loop20 + loop: can't get info on device /dev/loop20: No such device or address + + is bad. + + Note that ioctl() must succeed, thus loop0 device must be configured to + trigger the bug. + [Regression Potential] - * klibc is quite special, as it uses linux kernel headers/assembly. It + * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. - * disabling cf-protection and stack-clash-protection did not help. + * disabling cf-protection and stack-clash-protection did not help. - * building with gcc-8 does not exhibit the problem. + * building with gcc-8 does not exhibit the problem. - * the workaround is quite simple in the code, keep a copy of argc to + * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] - - * Original bug report + + * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e
[Kernel-packages] [Bug 1850443] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301817/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301815/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301813/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301818/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301816/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301820/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] Re: Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message
Attaching logs from a reproduction, occured at 10:09:50 localtime in the
journal on the computer.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301821/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850443] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301822/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+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 1850826] [NEW] nvidia-graphics-drivers-390 390.129-0ubuntu2 ADT test failure with linux 5.4.0-3.4
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-390/20191030_143354_e7fac@/log.gz ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1850826 Title: nvidia-graphics-drivers-390 390.129-0ubuntu2 ADT test failure with linux 5.4.0-3.4 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-390/20191030_143354_e7fac@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1850826/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
This bug was fixed in the package klibc - 2.0.7-1ubuntu1 --- klibc (2.0.7-1ubuntu1) focal; urgency=low * Merge from Debian unstable. Remaining changes: * Fix FTBFS on eoan and later with new gcc - cf-protection.patch: Disable cf-protection for syscalls stub. * save-argc.patch: when build with gcc-9 linux-5.3, calling ioctl, clears global argc, thus save it, to compare to it later. Otheriwse losetup -f is broken LP: #1850184 klibc (2.0.7-1) unstable; urgency=medium [ Ben Hutchings ] * New upstream version: - klcc: Enable stripping even if CONFIG_DEBUG_INFO is enabled - run-init: Allow the initramfs to be persisted across root changes (thanks to Matthew Garrett) - ipconfig: Implement support -d ...:dns0:dns1 options (Closes: #931416) - Kbuild: Work around broken "ar s" in binutils 2.32 (see #941921) * debian/rules: Reorganise make flags variables * debian/rules: Define ARCH for klibc, for all architectures * debian/rules: Delete redundant architecture mappings * debian/rules: Delete redundant export * klibc-utils: Trigger update-initramfs on install/upgrade * initramfs-tools: Don't install commands that already exist in /sbin * initramfs-tools: Exclude kinit and zcat commands earlier * initramfs-tools: Exclude gzip command * Drop "resume: Backward compatibility for resume_offset", which will not be needed in the next release * [klibc] fstype: Drop obsolete support for "ext4dev" (Closes: #932926) * debian/control: Set Maintainer to Debian Kernel Team; move maks to Uploaders [ James Clarke ] * debian/control: Restrict m4 build dependency to just sparc [ Helmut Grohne ] * Honour DEB_BUILD_OPTIONS=nocheck. (Closes: #922814) -- Dimitri John Ledkov Thu, 31 Oct 2019 11:50:44 + ** Changed in: klibc (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: Fix Released Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1848236] Re: Add installer support for iwlmvm adapters
I've verified this bug using the following procedure: a) For all the required series, download the "debian-installer" source package and all of its build dependencies; b) Modify the build/config/amd64.cfg to use the -proposed version of the kernel for the series you're verifying; c) Run make "build_netboot" to create the installer images; d) Check the generated initrd.gz to see if the kernel there contains the right module. The results from my testing: For Xenial: # zcat initrd.gz | cpio -tdm | grep iwlmvm lib/modules/4.4.0-167-generic/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko For Bionic: # zcat initrd.gz | cpio -tdm | grep iwlmvm lib/modules/4.15.0-68-generic/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko For Disco: # zcat initrd.gz | cpio -tdm | grep iwlmvm lib/modules/5.0.0-34-generic/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko For Eoan: # zcat initrd.gz | cpio -tdm | grep iwlmvm lib/modules/5.3.0-21-generic/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko Cheers, Guilherme ** Tags removed: verification-needed-bionic verification-needed-disco verification-needed-eoan verification-needed-xenial ** Tags added: verification-done-bionic verification-done-disco verification-done-eoan 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/1848236 Title: Add installer support for iwlmvm adapters Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] Some wireless Intel cards that use the iwlmvm driver are not available during installation. [Test Case] Boot up the Ubuntu installer on a system with an iwlmvm adapter, and try using the wireless connection. [Fix] Add the missing sub-module to debian.master/d-i/nic-modules [Regression Potential] As we're including a new sub-module, this change makes the installer susceptible to bugs present in the iwlmvm driver. Other than that, this change should not introduce any new regressions as it doesn't change any driver code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848236/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1849012, bug 1850799 + bionic/linux-oem: bug 1850799, bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799, bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)
I don't know if my problem is related specifically to the Realtek AC256 codec. In any case, it seems FreeBSD folk fixed a while back the same issue: no headphone output through some patches related to this codec on some Dell models. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219350 https://github.com/trueos/trueos/pull/279 https://reviews.freebsd.org/D19017 ** Bug watch added: bugs.freebsd.org/bugzilla/ #219350 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219350 -- 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/1850702 Title: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows) Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64
[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
Here's a fresh one: Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0. Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x22CE | ADVANCED_SYSASSERT Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0590A2F0 | trm_hw_status0 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | trm_hw_status1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0048853E | branchlink2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x00479392 | interruptlink1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | interruptlink2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x012C | data1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | data2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0400 | data3 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x47C01D18 | beacon time Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xE6D232B3 | tsf low Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0037 | tsf hi Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | time gp1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xEFAD9254 | time gp2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x002E | uCode version major Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x6BF1DF06 | uCode version minor Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0321 | hw version Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x00489004 | board version Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x001C | hcmd Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xA7F93840 | isr0 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x000C | isr1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x1802 | isr2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x404155DD | isr3 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | isr4 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x00A90400 | last cmd Id Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x00018802 | wait_event Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x4288 | l2p_control Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0020 | l2p_duration Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x03BF | l2p_mhvalid Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x00EF | l2p_addr_match Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x000D | lmpm_pmg_sel Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x08081424 | timestamp Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x15401818 | flow_handler Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Status: 0x0040, count: 7 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | umac branchlink1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xC00E | umac branchlink2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xC0084414 | umac interruptlink1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xC0084414 | umac interruptlink2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x0800 | umac data1 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xC0084414 | umac data2 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xDEADBEEF | umac data3 Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x002E | umac major Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x6BF1DF06 | umac minor Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xEFAD940D | frame pointer Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xC088627C | stack pointer Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x00A90400 | last host cmd Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | isr status reg Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: Fseq Registers: Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xB8499186 | FSEQ_ERROR_CODE Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x | FSEQ_TOP_INIT_VERSION Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xBF732FED | FSEQ_CNVIO_INIT_VERSION Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xA371 | FSEQ_OTP_VERSION Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x2DF66FFD | FSEQ_TOP_CONTENT_VERSION Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0x103205DA | FSEQ_ALIVE_TOKEN Oct 31 19:35:40 weywot kernel: iwlwifi :03:00.0: 0xF76D7FD7 | FSEQ_CNVI_ID Oct 31
[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured
Retested with Bionic-proposed version (1:1.6.5-1ubuntu1~18.04.3) and Disco-proposed (1:1.6.5-1ubuntu1.3), both including the fix for this bug. All working fine. I've used the "droppkt" hack (see comment #24) to simulate the problem, and it's fixed in the -proposed version. Thanks, Guilherme ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * Kdump over network (like NFS mount or SSH dump) relies on network- online target from systemd. Even so, there are some NICs that report "Link Up" state but aren't ready to transmit packets. This is a generally bad behavior that is credited probably to NIC firmware delays, usually not fixable from drivers. Some adapters known to act like this are bnx2x, tg3 and ixgbe. * Kdump is a mechanism that may be a last resort to debug complex/hard to reproduce issues, so it's interesting to increase its reliability / resilience. We then propose here a solution/quirk to this issue on network dump by adding a retry/delay mechanism; if it's a network dump, kdump will retry some times and sleep between the attempts in order to exclude the case of NICs that aren't ready yet but will soon be able to transmit packets. * Although first reported by IBM in PowerPC arch, the scope for this issue is the NIC, and it was later reported in x86 arch too. [Test case] Usually it's difficult to naturally reproduce this issue in a deterministic way, but we have an artificial test case on comment #24 of this LP. Also, we have a report from this bug in which the user managed to reproduce the problem consistently - it's fixed after testing our solution. [Regression potential] There's not a clear regression potential here since it's just a retry/delay mechanism. Some potential problems may come from bad coding in the script. The delay between attempts is only 3 sec per iteration, so it shouldn't block the kdump progress for a high amount of time at once. [Other information] Salsa Debian commit: https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)
Just to give more insight about this, I just tried a live USB with 18.04.03 and the results are similar: the sound is extremely low, but with no distortion whatsoever. -- 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/1850702 Title: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows) Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name:
[Kernel-packages] [Bug 1850548] Re: Unable to install kdump tools: post install script returning fail
kdump-tools requires a kernel to be loaded by kexec -p to work. There is no workaround on that. If your /boot/ does not contain a kernel, it could possibly use a kernel from somewhere else, but you would still need a kernel. There is a pending patch that I have in the works that would postpone the creation of the initrd after the first reboot or after kdump-tools is first started. That would allow postinst to succeed and the installation would be fine. However, kdump-tools might still not work before proper configuration. About the GRUB support, it's used to add the crashkernel parameter to the bootloader, GRUB being one of the options supported. If your netbooting, it's very likely GRUB is not used at all or the local configuration is totally ignored, so you would still need to manually configure your netboot setup to add that parameter to the kernel command line. I will send a test version to a ppa that skips the initrd creation during postinst. Which series are you testing this on? Is it bionic? Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1850548 Title: Unable to install kdump tools: post install script returning fail Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: ---Problem Description--- Unable to install Kdump-tools. ---Steps to Reproduce--- Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb Note: Unable to install the Kdump-tool. The problem comes when postinst script is run: root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash [0.00] Kernel command line: imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz XCAT=192.168.0.2:3001 XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 transparent_hugepage=never intel_iommu=on iommu=pt cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt ds=nocloud crashkernel=768M,low crashkernel=4G,high Error: = update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz because associated file /usr/share/man/man1/bsd-write.1.gz (of link group write) doesn't exist^M update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) doesn't exist^M Setting up ifenslave (2.9ubuntu1) ...^M Setting up file (1:5.32-2ubuntu0.2) ...^M Setting up kdump-tools (1:1.6.3-2) ...^M ^M Creating config file /etc/default/kdump-tools with new version^M dpkg: error processing package kdump-tools (--configure):^M installed kdump-tools package post-installation script subprocess returned error exit status 1^M dpkg: dependency problems prevent configuration of linux-crashdump:^M linux-crashdump depends on kdump-tools; however:^M Package kdump-tools is not configured yet.^M ^M Detail Log: === root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic1_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up file (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i bsdmainutils_11.1.2ubuntu1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ...
[Kernel-packages] [Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
This is my replacement "minimized" losetup.c that exhibits the problem. Simply, drop this into klibc sources and run: ./debian/rules build; sudo ./usr/utils/static/losetup 1 Argc before find_unused_loop_devices() 0 Argc after find_unused_loop_devices() Argc values before and after did not match. Note that same source works fine as glibc binary: gcc ./usr/utils/losetup.c; sudo ./a.out 1 Argc before find_unused_loop_devices() 1 Argc after find_unused_loop_devices() ** Attachment added: "losetup.c" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+attachment/5301878/+files/losetup.c -- 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: Fix Released Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1850675] Re: ARM CPU support update
https://lists.ubuntu.com/archives/kernel-team/2019-October/105157.html -- 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/1850675 Title: ARM CPU support update Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: In Progress Status in linux-aws source package in Disco: In Progress Status in linux-aws source package in Eoan: In Progress Bug description: linux-aws kernels need various arm64 commits from mainline and linux- arm-kernel ML to support latest ARM CPUs. Needed commits include - SSBS support [mainline] - irqchip/gic-v3 updates [mainline] - all mainline Neoverse errata including https://lore.kernel.org/linux-arm-kernel/20191002094935.48848-1-james.mo...@arm.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1850675/+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 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured
There is some reported regressions in autopkgtests for ppc64el and s390x, I'm investigating. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: Fix Committed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * Kdump over network (like NFS mount or SSH dump) relies on network- online target from systemd. Even so, there are some NICs that report "Link Up" state but aren't ready to transmit packets. This is a generally bad behavior that is credited probably to NIC firmware delays, usually not fixable from drivers. Some adapters known to act like this are bnx2x, tg3 and ixgbe. * Kdump is a mechanism that may be a last resort to debug complex/hard to reproduce issues, so it's interesting to increase its reliability / resilience. We then propose here a solution/quirk to this issue on network dump by adding a retry/delay mechanism; if it's a network dump, kdump will retry some times and sleep between the attempts in order to exclude the case of NICs that aren't ready yet but will soon be able to transmit packets. * Although first reported by IBM in PowerPC arch, the scope for this issue is the NIC, and it was later reported in x86 arch too. [Test case] Usually it's difficult to naturally reproduce this issue in a deterministic way, but we have an artificial test case on comment #24 of this LP. Also, we have a report from this bug in which the user managed to reproduce the problem consistently - it's fixed after testing our solution. [Regression potential] There's not a clear regression potential here since it's just a retry/delay mechanism. Some potential problems may come from bad coding in the script. The delay between attempts is only 3 sec per iteration, so it shouldn't block the kdump progress for a high amount of time at once. [Other information] Salsa Debian commit: https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+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 1850828] [NEW] nvidia-graphics-drivers-435 435.21-0ubuntu3 ADT test failure with linux 5.4.0-3.4
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-435/20191030_151840_5f268@/log.gz ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1850828 Title: nvidia-graphics-drivers-435 435.21-0ubuntu3 ADT test failure with linux 5.4.0-3.4 Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-unstable/focal/amd64/n/nvidia-graphics-drivers-435/20191030_151840_5f268@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1850828/+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 1850886] [NEW] Auto-rotate is not working properly when system is booted up while not in its regular orientation
Public bug reported: [RELEASE VERSION] Description:Ubuntu 18.04.3 LTS Release:18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-oem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in linux-meta-oem package in Ubuntu: New Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1849012, bug 1850799 + bionic/linux-oem: bug 1850799, bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799, bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1836858] Re: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
** Summary changed: - i915: Display flickers during "flickerfree" boot (BIOS logo on a black background) + i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background -- 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/1836858 Title: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in linux package in Ubuntu: Confirmed Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+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 1843207] Re: Doesn't boot on Raspberry Pi 4
Hello, Apologies for a newbie question. Is there a scheduled release date for the upgrade/update at ubuntu-19.10-preinstalled-server-arm64+raspi3.img? Just need to get my ducks in a row by suspending work on the current image with respect to items other than the total_mem issue. Thanks. Kind regards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1843207 Title: Doesn't boot on Raspberry Pi 4 Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Bug description: linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to missing kernel modules for the new hardware components. It would be nice if these got included. Also it only boots the kernel when the Pi is configured for 1GB RAM or less. (Then gets stuck on missing root FS because the microSD isn't detected.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+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 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -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: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 31. October 2019 12:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1850480 Title: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 31. October 2019 12:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850480/+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 1850860] [NEW] 5.0.0-32.34 causes system instability with cephfs
You have been subscribed to a public bug: On Ubuntu 18.04 linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 According to https://www.mail-archive.com/ceph- us...@ceph.io/msg00940.html the same happens on Disco with this kernel version. Processes that read data from CephFS get stuck, the system becomes unstable. dmesg contains messages like this: [ 1510.703090] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.711590] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.720093] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.728592] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.737086] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.745587] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.754080] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info According to the discussion here: https://github.com/coreos/bugs/issues/2616 this is caused by a faulty patch. If that information is correct the problematic patch should be https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=100a8eb40c492f2525cdae434c50d53ec7f5cc23 ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- 5.0.0-32.34 causes system instability with cephfs https://bugs.launchpad.net/bugs/1850860 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed 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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** No longer affects: gcc-9 (Ubuntu) ** No longer affects: gcc-9 (Ubuntu Eoan) ** No longer affects: gcc-9 (Ubuntu Focal) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Eoan) ** No longer affects: 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/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Status in klibc source package in Focal: Confirmed Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1849871] Re: Skip frame when buffer overflow on UVC camera
** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1849871 Title: Skip frame when buffer overflow on UVC camera Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Currently to use Intel RealSense, kernel needs to be patched [1]. This SRU is to bring one of several fixes to Ubuntu kernel. "Some cameras post inaccurate frame where next frame data overlap it. this results in screen flicker, and it need to be prevented." [Fix] "So this patch marks the buffer error to discard the frame where buffer overflow." [Test] I don't have such bad device so I can't test it. By reading through the code, this patch seems to be correct. [Regression Potential] Low. This patch has been in the kernel tree for more than two years and it doesn't bring any regression. So it should be fairly safe. [1] https://github.com/IntelRealSense/librealsense/blob/master/scripts /patch-realsense-ubuntu-lts.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849871/+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 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress 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/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+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 1850870] [NEW] Disco update: upstream stable patchset 2019-10-31
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-10-31 Ported from the following upstream stable releases: v4.19.79, v5.3.6 from git://git.kernel.org/ s390/process: avoid potential reading of freed stack KVM: s390: Test for bad access register and size at the start of S390_MEM_OP s390/topology: avoid firing events before kobjs are created s390/cio: exclude subchannels with no parent from pseudo check KVM: PPC: Book3S HV: Fix race in re-enabling XIVE escalation interrupts KVM: PPC: Book3S HV: Check for MMU ready on piggybacked virtual cores KVM: PPC: Book3S HV: Don't lose pending doorbell request on migration on P9 KVM: X86: Fix userspace set invalid CR4 nbd: fix max number of supported devs PM / devfreq: tegra: Fix kHz to Hz conversion ASoC: Define a set of DAPM pre/post-up events ASoC: sgtl5000: Improve VAG power and mute control powerpc/mce: Fix MCE handling for huge pages powerpc/mce: Schedule work from irq_work powerpc/powernv: Restrict OPAL symbol map to only be readable by root powerpc/powernv/ioda: Fix race in TCE level allocation powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions can: mcp251x: mcp251x_hw_reset(): allow more time after a reset tools lib traceevent: Fix "robust" test of do_generate_dynamic_list_file crypto: qat - Silence smp_processor_id() warning crypto: skcipher - Unmap pages after an external error crypto: cavium/zip - Add missing single_release() crypto: caam - fix concurrency issue in givencrypt descriptor crypto: ccree - account for TEE not ready to report crypto: ccree - use the full crypt length value MIPS: Treat Loongson Extensions as ASEs power: supply: sbs-battery: use correct flags field power: supply: sbs-battery: only return health when battery present tracing: Make sure variable reference alias has correct var_ref_idx usercopy: Avoid HIGHMEM pfn warning timer: Read jiffies once when forwarding base clk PCI: vmd: Fix shadow offsets to reflect spec changes watchdog: imx2_wdt: fix min() calculation in imx2_wdt_set_timeout perf stat: Fix a segmentation fault when using repeat forever drm/omap: fix max fclk divider for omap36xx drm/msm/dsi: Fix return value check for clk_get_parent drm/nouveau/kms/nv50-: Don't create MSTMs for eDP connectors drm/i915/gvt: update vgpu workload head pointer correctly mmc: sdhci: improve ADMA error reporting mmc: sdhci-of-esdhc: set DMA snooping based on DMA coherence Revert "locking/pvqspinlock: Don't wait if vCPU is preempted" xen/xenbus: fix self-deadlock after killing user process ieee802154: atusb: fix use-after-free at disconnect s390/cio: avoid calling strlen on null pointer cfg80211: initialize on-stack chandefs ima: always return negative code for error ima: fix freeing ongoing ahash_request fs: nfs: Fix possible null-pointer dereferences in encode_attrs() 9p: Transport error uninitialized 9p: avoid attaching writeback_fid on mmap with type PRIVATE xen/pci: reserve MCFG areas earlier ceph: fix directories inode i_blkbits initialization ceph: reconnect connection if session hang in opening state watchdog: aspeed: Add support for AST2600 netfilter: nf_tables: allow lookups in dynamic sets drm/amdgpu: Fix KFD-related kernel oops on Hawaii drm/amdgpu: Check for valid number of registers to read pNFS: Ensure we do clear the return-on-close layout stateid on fatal errors pwm: stm32-lp: Add check in case requested period cannot be achieved x86/purgatory: Disable the stackleak GCC plugin for the purgatory ntb: point to right memory window index thermal: Fix use-after-free when unregistering thermal zone device thermal_hwmon: Sanitize thermal_zone type libnvdimm/region: Initialize bad block for volatile namespaces fuse: fix memleak in cuse_channel_open libnvdimm/nfit_test: Fix acpi_handle redefinition sched/membarrier: Call sync_core only before usermode for same mm sched/membarrier: Fix private expedited registration check sched/core: Fix migration to invalid CPU in __set_cpus_allowed_ptr() perf build: Add detection of java-11-openjdk-devel package kernel/elfcore.c: include proper prototypes perf unwind: Fix libunwind build failure on i386 systems nfp: flower: fix memory leak in nfp_flower_spawn_vnic_reprs drm/radeon: Bail earlier when radeon.cik_/si_support=0 is passed KVM: PPC: Book3S HV: XIVE: Free escalation interrupts before disabling the VP KVM: nVMX: Fix consistency check on injected exception error code nbd: fix crash when the blksize is zero powerpc/pseries: Fix cpu_hotplug_lock acquisition in resize_hpt()
[Kernel-packages] [Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf)
** Summary changed: - CONFIG_KVM is disabled for linux-raspi2 (aarch64) + CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+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 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)
** Summary changed: - [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering + [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 19.10). For example: When I want to go to a button the cursor sometimes stops on the way to it and moves on milliseconds later. In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is not present. Please let me now if I can add some further information. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 All available system updates were installed. No extensions added additionally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 06:23:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-20 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+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 1850668] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850668 Title: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly Status in linux package in Ubuntu: Confirmed Bug description: NO se que le pasa ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CompositorRunning: None Date: Wed Oct 30 17:33:50 2019 DistUpgraded: 2019-10-23 18:48:24,042 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-32-generic, x86_64: installed nvidia, 430.50, 5.3.0-19-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:125f] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1261] InstallationDate: Installed on 2019-08-19 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire A717-72G ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a2aeaa4e-4f3c-4b06-b9e5-ba7fe9d5ee08 ro acpi_osi=Linux acpi_backlight=vendor quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (6 days ago) dmi.bios.date: 10/31/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charizard_CFS dmi.board.vendor: CFL dmi.board.version: V1.22 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnAspireA717-72G:pvrV1.22:rvnCFL:rnCharizard_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22: dmi.product.family: Aspire 7 dmi.product.name: Aspire A717-72G dmi.product.sku: dmi.product.version: V1.22 dmi.sys.vendor: Acer nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Oct 30 16:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4509 vendor AUO xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850668/+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 1849917] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849917 Title: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10 from 19.04 I noticed the mouse moves unequally/choppy. I did a fresh install (deleting and overwriting 19.04 with 19.10). For example: When I want to go to a button the cursor sometimes stops on the way to it and moves on milliseconds later. In Ubuntu Ubuntu 19.04 (which is my daily driver for now) this behavior is not present. Please let me now if I can add some further information. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 All available system updates were installed. No extensions added additionally. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 06:23:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-20 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 - bionic/linux-oem: bug 1850799, bug 1849012 + bionic/linux-oem: bug 1849012, bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1849012, bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850668] [NEW] Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly
You have been subscribed to a public bug: NO se que le pasa ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CompositorRunning: None Date: Wed Oct 30 17:33:50 2019 DistUpgraded: 2019-10-23 18:48:24,042 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-32-generic, x86_64: installed nvidia, 430.50, 5.3.0-19-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:125f] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1261] InstallationDate: Installed on 2019-08-19 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire A717-72G ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a2aeaa4e-4f3c-4b06-b9e5-ba7fe9d5ee08 ro acpi_osi=Linux acpi_backlight=vendor quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (6 days ago) dmi.bios.date: 10/31/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charizard_CFS dmi.board.vendor: CFL dmi.board.version: V1.22 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnAspireA717-72G:pvrV1.22:rvnCFL:rnCharizard_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22: dmi.product.family: Aspire 7 dmi.product.name: Aspire A717-72G dmi.product.sku: dmi.product.version: V1.22 dmi.sys.vendor: Acer nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Oct 30 16:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4509 vendor AUO xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly https://bugs.launchpad.net/bugs/1850668 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 1850860] [NEW] 5.0.0-32.34 causes system instability with cephfs
Public bug reported: On Ubuntu 18.04 linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 According to https://www.mail-archive.com/ceph- us...@ceph.io/msg00940.html the same happens on Disco with this kernel version. Processes that read data from CephFS get stuck, the system becomes unstable. dmesg contains messages like this: [ 1510.703090] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.711590] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.720093] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.728592] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.737086] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.745587] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.754080] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info According to the discussion here: https://github.com/coreos/bugs/issues/2616 this is caused by a faulty patch. If that information is correct the problematic patch should be https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=100a8eb40c492f2525cdae434c50d53ec7f5cc23 ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1850860 Title: 5.0.0-32.34 causes system instability with cephfs Status in linux-signed package in Ubuntu: New Bug description: On Ubuntu 18.04 linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 According to https://www.mail-archive.com/ceph- us...@ceph.io/msg00940.html the same happens on Disco with this kernel version. Processes that read data from CephFS get stuck, the system becomes unstable. dmesg contains messages like this: [ 1510.703090] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.711590] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.720093] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.728592] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.737086] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.745587] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.754080] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info According to the discussion here: https://github.com/coreos/bugs/issues/2616 this is caused by a faulty patch. If that information is correct the problematic patch should be https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=100a8eb40c492f2525cdae434c50d53ec7f5cc23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1850860/+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 1690085]
Could this be related? [620533.9804061 RBP: R08: 0001 R09: 7f901480 [620533.981792] R10: 7f9014de0270 R11: 0206 R12: 7f90477fdlfe [620533.983039] R13: 7f90477fdlff R14: 7f901700 R15: 7f901fffe540 [620541.767819] watchdog: BUG: soft lockup - CPU#4 stuck for 220 Enc4:Eantoor:5552.1 [620541.769193] Modules linked in: tun ueth nf_conntrack_netlink nfnetlink xfrm_user xfrn_algo xt_addrtype iptable filter xt c, ntrack br_petfilter bridge stp 11c ouerlay xt_nat xt_tcpudp iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defraliipu6 -n id.nfjlefrag_ipu4 nouueau snd_bda_codec_realtek snd_hda_codec_generic ledtrig_audio mxn_wmi i2c_algo_bit ttm edac_mCe_amd snd a_intel drmitms_helper snd_hda_codec eeepc_wmi kum_and snd_hda_core sparse_keymap drm rfkill snd_hudep joydeu inputied s snd, cm r8169 wml_trmof kum irgbypass realtek snd_timer libphy agpgart ccp snd syscopyarea sysfillrect sysimgblt sp5100_tco sou ndcore fb_sys_fops rng_core i2cpiix4 crctlOdif_pclmul klOtemp crc32_pclmul ghash_clmulni_inte1 aesni_intel aes_x86_64 crypto_si md crypt& glue helper pcspkr wmi pinctrl_and pcc_cpufreq eudeu gpio_andpt mac_hid acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd gr ace sunrpc ip_tables x tables ext4 crc16 mbcache jbd2 raid456 libcrc32c crc32c_generic async_raid6_recou 1620541.7692211 async memcpy async_pq async_xor xor async_tx raid6_pq raidl md_mod hid_generic sd_mod usbhid hid ahci libahci 1 ibata crc32c_intel xhcipci xhci_bcd scsi_mod 1620541.7638311 CPU: 4 PID: 5552 Comm: nc4:Eantoor Tainted: G U L 5.2.11-archl-l-ARCH #1 [620541.765314] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIBS 1804 07/29/2019 [620541.766760] RIP: 0010:smp_call_function_many+Ox20b/Ox270 [620541.766216] Code: e6 8a ae 78 00 3b 05 f8 Od 21 01 89 c7 Of 83 7a fe ff ff 48 63 c7 48 8b Ob 48 03 Oc c5 60 ba d6 al 8b 41 1 6 a8 01 74 Oa f3 90 51 16 83 e2 01 75 f6 eb c9 48 c7 c2 c0 14 f4 al 4c 89 fe 89 df [620541.791144] RSP: 0016:aefd63e2bcd0 EFLAGS: 0202 ORIG_RAX: ffl3 [620541.7925011 RAX: 0003 RBX: 8fe6be72b440 RCX: 8fe6be7flle0 1620541.793697] RDX: 0001 BSI: RDI: 0007 [620541.795357] RBP: a0c7c7e0 R08: 8fe6be72b448 R09: 8fe6be72b470 1620541.796751] R10: 8fe6be72b448 R11: 0005 R12: 8febbe729d40 1620541:798198] R13: 8fe6be72b448 R14: 0001 R15: 0140 [620541.799600] FS: 7f9044d5c700() G3:8fe6be70() knlGS: [620541.800986] CS: 0010 DS: ES: CH0: 80050033 [620541.802414] CR2: 7f9062e8 f3b0 CR3: 0003ae65a000 CR4: 003406e0 [620541.803847] Call Trace: [629541.80-r 8] flush tlb mm_range+Oxe1/0x140 1620541.8065503 tlb_flush mmu+Ox72/0x140 [628541.807929] tlb_finish_mmu+Ox3d/Ox70 t62e541me92?el zap_page_range+Oxl4b/Oxia0 [620541.810589] se sys maduise+Ox613/0x890 [620541.811932] ? do syscall_64+0x5f/Ox1d0 [628541.813277] do syscall_64+0x5f/Ox1d0 [629541.8146481 ? page_fault+Ox8/0x30 [628541.815992] entry SYSCALL64afterbaframe+Ox44/0xa9 [620541i817395] RIP: 0833:0x7f9062dd7597 russdriAluffral Code: ff ff ff ff c3 48 8b 15 f7 f8 Oc 00 f7 d8 64 89 02 b8 ff ff ff ff eb be 66 2e Of if 84 00 00 00 00 00 90 b 8 lc ee ee ee Of 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b Od c9 f8 c 0 f7 dB 64 89 01 48 1.8Z1587.1 1SP: 082b:7f9044d5b478 EFLAGS: 0206 ORIG_ORAX:0 001c tfiZe541.13229471 RAX: ffda RBX. 7f904455c000 RCX: 7f9062dd7597 007fb000 RDI: 7f904455c000 E629541.8Z44311 RDX: 000 0004 BSI: [ 1.8258153] RBP: R08: 0001 R09: 7f902480 E 1.8M871 B1e: 7f90246af180R11: 0206 R12: 7f9047ffelfe I 1.8287181 R13: 7f9047ffelff R14: 7f9044d5c700 R15: 7f9044d5b540 ME, Sorry, no logging in syslog because the machine crashes hard. Optional picture of the output: https://iot.jcz.nl/soft_lockup.jpg -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks:
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
I have the same problem with my custom install, inherited and upgraded from my Ubuntu 19.04 system. After each boot I run a small script to export and import my three pools again. zsys is not installed anymore on this manual install from early 2019. The system worked without problems on Ubuntu 19.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+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 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 We have a bug to track the enabling of v3d.ko https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396=01a0c4b0cb4c05e605cbf9d41f660e08=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+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 1850668] Re: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly
** Summary changed: - No conozco el error + Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850668 Title: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly Status in linux package in Ubuntu: Confirmed Bug description: NO se que le pasa ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CompositorRunning: None Date: Wed Oct 30 17:33:50 2019 DistUpgraded: 2019-10-23 18:48:24,042 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-32-generic, x86_64: installed nvidia, 430.50, 5.3.0-19-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:125f] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1261] InstallationDate: Installed on 2019-08-19 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire A717-72G ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a2aeaa4e-4f3c-4b06-b9e5-ba7fe9d5ee08 ro acpi_osi=Linux acpi_backlight=vendor quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (6 days ago) dmi.bios.date: 10/31/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charizard_CFS dmi.board.vendor: CFL dmi.board.version: V1.22 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnAspireA717-72G:pvrV1.22:rvnCFL:rnCharizard_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22: dmi.product.family: Aspire 7 dmi.product.name: Aspire A717-72G dmi.product.sku: dmi.product.version: V1.22 dmi.sys.vendor: Acer nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Oct 30 16:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4509 vendor AUO xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850668/+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 1850876] [NEW] CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
Public bug reported: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 ** Affects: linux-raspi2 (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: New Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
I guess this patch fixes the issue:
commit b05f65d7720b172b6fde3abfa49ed66837071d45
Author: Alex Deucher
Date: Thu Aug 15 08:27:09 2019 -0500
drm/amdgpu/gfx9: update pg_flags after determining if gfx off is
possible
We need to set certain power gating flags after we determine
if the firmware version is sufficient to support gfxoff.
Previously we set the pg flags in early init, but we later
we might have disabled gfxoff if the firmware versions didn't
support it. Move adding the additional pg flags after we
determine whether or not to support gfxoff.
Fixes: 005440066f92 ("drm/amdgpu: enable gfxoff again on raven series (v2)")
Tested-by: Kai-Heng Feng
Tested-by: Tom St Denis
Signed-off-by: Alex Deucher
Cc: Kai-Heng Feng
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc5/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848741
Title:
[amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen
2500u (Raven Ridge)
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
Confirmed
Bug description:
I have graphics artefacts: screan tearing, pieces of the previous window
appear in the newly opened window.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-09-08 (42 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: gnome-shell 3.34.1-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
Tags: eoan
Uname: Linux 5.3.0-18-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago)
UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+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 1850738] Re: Intel Bluetooth AX201 HarrisonPeak (HrP) firmware causes system hang in deep suspend
https://lists.ubuntu.com/archives/kernel-team/2019-October/105147.html ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Disco) Status: New => 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/1850738 Title: Intel Bluetooth AX201 HarrisonPeak (HrP) firmware causes system hang in deep suspend Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Disco: In Progress Bug description: When system has been paired with BLE devices, bluetooth firmware may fail to suspend, or even hangs the whole system that it can only be rebooted with SysRq keys. [Reproduce steps]: 1. pair with BLE devices. They doesn't have to stay connected/powered on during the test. 2. make sure Bluetooth is now receiving LE ADV broadcats, which should leave messages in dmesg like: Bluetooth: hci0: advertising data len corrected 3. suspend the system a few times. With 5.0.0-1025-oem-osp1 kernel, symptoms would usually appear in <= 5 times. [Results] 1. one may observed following errors in between the suspend messages: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 PM: Device :00:14.0 failed to suspend async: error -16 PM: Some devices failed to suspend, or early wake event detected where :00:14.0 is the xHCI Usb hub. 2. with or without above error messages appear first, system may hang and leave only "PM: suspend entry (deep)" in the syslog. [Notes] * kernels newer than v5.2.1, inclusive of latest v5.4-rc5, still have those PM suspend errors, but they doesn't seem to cause system block. Instead, they may resume immediately. * this was found on one platform with Intel Dual Band Wireless AC 9462 [8086:02f0] subsystem id [8086:42a4], linux-firmware 1.173.11 with intel/ibt-19-0-0.sfi REL0282. However, it's not reproducible on another platform with same hw/fw/kernel configuration. kernel: [ 78.136285] PM: suspend entry (deep) kernel: [ 78.139836] Filesystems sync: 0.003 seconds kernel: [ 78.140461] Freezing user space processes ... (elapsed 0.002 seconds) done. kernel: [ 78.142669] OOM killer disabled. kernel: [ 78.142669] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. kernel: [ 78.143875] printk: Suspending console(s) (use no_console_suspend to debug) kernel: [ 78.335256] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 kernel: [ 78.457675] sof-audio-pci :00:1f.3: firmware boot complete kernel: [ 78.460486] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 kernel: [ 78.460494] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 kernel: [ 78.460497] PM: Device :00:14.0 failed to suspend async: error -16 kernel: [ 78.567263] PM: Some devices failed to suspend, or early wake event detected kernel: [ 78.580871] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 kernel: [ 78.713018] sof-audio-pci :00:1f.3: firmware boot complete kernel: [ 78.733982] Bluetooth: hci0: advertising data len corrected kernel: [ 78.792707] nvme nvme0: Shutdown timeout set to 8 seconds kernel: [ 78.841602] nvme nvme0: 8/0/0 default/read/poll queues kernel: [ 78.859328] usb 1-4: reset high-speed USB device number 12 using xhci_hcd kernel: [ 79.113113] Bluetooth: hci0: advertising data len corrected kernel: [ 79.331948] usb 1-4.4: reset high-speed USB device number 14 using xhci_hcd kernel: [ 79.432122] Bluetooth: hci0: advertising data len corrected kernel: [ 79.559747] usb 1-4.1: reset full-speed USB device number 13 using xhci_hcd kernel: [ 79.887006] acpi LNXPOWER:05: Turning OFF kernel: [ 79.887265] OOM killer enabled. kernel: [ 79.887266] Restarting tasks ... done. kernel: [ 79.926848] PM: suspend exit ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.11 [modified: lib/firmware/intel/ibt-19-0-0.sfi lib/firmware/intel/sof/sof-cnl.ri] ProcVersionSignature: Ubuntu 5.0.0-1025.28-oem-osp1 5.0.21 Uname: Linux 5.0.0-1025-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2037 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 22:11:48 2019 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-tywin+X17
[Kernel-packages] [Bug 1849419] Re: kernel panic after upgrading from 19.04 to 19.10
please help, it's a week i am testing everything with no success -- 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/1849419 Title: kernel panic after upgrading from 19.04 to 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from 19.04 to 19.10 on two of my pc does the same thing. the upgrade is ok , boot ok, but after some time, and never the same, every app is crashing unable to reboot. i manage a reset with the pc button, but after that kernel panic and no boot. every kernel listed is having a panic. only chance after that is clonezilla and turn back to previous image 19.04 that i saved. unable to enter recovery menu. grub works bios secure boot disabled. description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 13GiB *-cpu product: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 3715MHz capacity: 3900MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 09 width: 32 bits clock: 33MHz configuration: driver=ivb_uncore resources: irq:0 *-pci:0 description: PCI bridge product: Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 09 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:f7e0-f7ef ioport:e000(size=268435456) *-display description: VGA compatible controller product: Turks XT [Radeon HD 6670/7670] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:27 memory:e000-efff memory:f7e2-f7e3 ioport:e000(size=256) memory:c-d *-multimedia description: Audio device product: Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:30 memory:f7e4-f7e43fff *-usb:0 description: USB controller product: 7 Series/C210 Series Chipset Family USB xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 04 width: 64 bits clock: 33MHz capabilities: xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:25 memory:f7f0-f7f0 *-communication description: Communication controller product: 7 Series/C216 Chipset Family MEI Controller #1 vendor: Intel Corporation physical id: 16 bus info: pci@:00:16.0 version: 04 width: 64 bits clock: 33MHz capabilities: bus_master cap_list
[Kernel-packages] [Bug 1849419] Re: kernel panic after upgrading from 19.04 to 19.10
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849419/+attachment/5301659/+files/syslog -- 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/1849419 Title: kernel panic after upgrading from 19.04 to 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from 19.04 to 19.10 on two of my pc does the same thing. the upgrade is ok , boot ok, but after some time, and never the same, every app is crashing unable to reboot. i manage a reset with the pc button, but after that kernel panic and no boot. every kernel listed is having a panic. only chance after that is clonezilla and turn back to previous image 19.04 that i saved. unable to enter recovery menu. grub works bios secure boot disabled. description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 13GiB *-cpu product: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 3715MHz capacity: 3900MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 09 width: 32 bits clock: 33MHz configuration: driver=ivb_uncore resources: irq:0 *-pci:0 description: PCI bridge product: Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 09 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:f7e0-f7ef ioport:e000(size=268435456) *-display description: VGA compatible controller product: Turks XT [Radeon HD 6670/7670] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:27 memory:e000-efff memory:f7e2-f7e3 ioport:e000(size=256) memory:c-d *-multimedia description: Audio device product: Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:30 memory:f7e4-f7e43fff *-usb:0 description: USB controller product: 7 Series/C210 Series Chipset Family USB xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 04 width: 64 bits clock: 33MHz capabilities: xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:25 memory:f7f0-f7f0 *-communication description: Communication controller product: 7 Series/C216 Chipset Family MEI Controller #1 vendor: Intel Corporation physical id: 16 bus info: pci@:00:16.0 version: 04 width: 64 bits clock:
[Kernel-packages] [Bug 1849419] Re: kernel panic after upgrading from 19.04 to 19.10
I did upgrade again. 19.04 to 19.10 after poweroff for all night. the morning i switch pc on and after a few minutes i get the same kernel panic on every kernel installed. i did test kernel 5.4 rc3 and no success. same bug i am starting to think it's related to deluge because i was adding a magnet torrent and everything crashed. every application command had i sigfault. -- 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/1849419 Title: kernel panic after upgrading from 19.04 to 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Upgrading from 19.04 to 19.10 on two of my pc does the same thing. the upgrade is ok , boot ok, but after some time, and never the same, every app is crashing unable to reboot. i manage a reset with the pc button, but after that kernel panic and no boot. every kernel listed is having a panic. only chance after that is clonezilla and turn back to previous image 19.04 that i saved. unable to enter recovery menu. grub works bios secure boot disabled. description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 13GiB *-cpu product: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 3715MHz capacity: 3900MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 09 width: 32 bits clock: 33MHz configuration: driver=ivb_uncore resources: irq:0 *-pci:0 description: PCI bridge product: Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 09 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:f7e0-f7ef ioport:e000(size=268435456) *-display description: VGA compatible controller product: Turks XT [Radeon HD 6670/7670] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:27 memory:e000-efff memory:f7e2-f7e3 ioport:e000(size=256) memory:c-d *-multimedia description: Audio device product: Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:30 memory:f7e4-f7e43fff *-usb:0 description: USB controller product: 7 Series/C210 Series Chipset Family USB xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 04 width: 64 bits clock: 33MHz capabilities: xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:25 memory:f7f0-f7f0 *-communication description: Communication controller
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
I've fixed my problem by applying the kernel suggested in [1] [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016 -- 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/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15:13:31 Lappy kernel: [ 85.320173] iwlwifi :3b:00.0: 0x1000 | data2 Jul 17 15:13:31 Lappy kernel: [
[Kernel-packages] [Bug 1850776] [NEW] Kernel NULL pointer dereference on suspend
Public bug reported: Hi, I had a bug every now and then with the Nvidia proprietary driver 435 (installed via the "additionals proprietary drivers" GUI) where I try to suspend my laptop, and the system freezes. It happens from time to time, but so far, I have this issue quite frequently, as I'm often suspending my laptop, so very annoying as you can imagine. Looking at journactl -b 1, the reason is simple: kernel NULL pointer dereference: oct. 31 09:01:51 Strix kernel: BUG: kernel NULL pointer dereference, address: oct. 31 09:01:51 Strix kernel: #PF: supervisor instruction fetch in kernel mode oct. 31 09:01:51 Strix kernel: #PF: error_code(0x0010) - not-present page oct. 31 09:01:51 Strix kernel: PGD 0 P4D 0 oct. 31 09:01:51 Strix kernel: Oops: 0010 [#1] SMP PTI oct. 31 09:01:51 Strix kernel: CPU: 2 PID: 2719 Comm: Xorg Tainted: P O 5.3.0-19-generic #20-Ubuntu oct. 31 09:01:51 Strix kernel: Hardware name: ASUSTeK COMPUTER INC. Strix GL504GV_G515GV/GL504GV, BIOS GL504GV.307 07/11/2019 oct. 31 09:01:51 Strix kernel: RIP: 0010:0x0 oct. 31 09:01:51 Strix kernel: Code: Bad RIP value. oct. 31 09:01:51 Strix kernel: RSP: 0018:afb0c4077920 EFLAGS: 00010286 oct. 31 09:01:51 Strix kernel: RAX: RBX: 8db4a3fff110 RCX: c1c72060 oct. 31 09:01:51 Strix kernel: RDX: 0010 RSI: 8db4a3fff118 RDI: 8db4a3fff150 oct. 31 09:01:51 Strix kernel: RBP: 8db517aaadf0 R08: c1c720b8 R09: oct. 31 09:01:51 Strix kernel: R10: c0f0af14 R11: 8db51dea8820 R12: 8db4a3fff118 oct. 31 09:01:51 Strix kernel: R13: 8db3a87da120 R14: 8db517aaaf10 R15: 8db51ef3d028 oct. 31 09:01:51 Strix kernel: FS: 7faede56ca80() GS:8db52d88() knlGS: oct. 31 09:01:51 Strix kernel: CS: 0010 DS: ES: CR0: 80050033 oct. 31 09:01:51 Strix kernel: CR2: ffd6 CR3: 00045b712002 CR4: 003626e0 oct. 31 09:01:51 Strix kernel: Call Trace: oct. 31 09:01:51 Strix kernel: _nv004359rm+0x45/0x80 [nvidia] oct. 31 09:01:51 Strix kernel: WARNING: kernel stack frame pointer at d844b2ec in Xorg:2719 has bad value deb3a039 oct. 31 09:01:51 Strix kernel: unwind stack type:0 next_sp:93bd32f2 mask:0x2 graph_idx:0 oct. 31 09:01:51 Strix kernel: d844b2ec: 0018 (0x18) oct. 31 09:01:51 Strix kernel: 182c383c: c12f4285 (_nv004359rm+0x45/0x80 [nvidia]) oct. 31 09:01:51 Strix kernel: 0c257d20: 8db51ef3d010 (0x8db51ef3d010) oct. 31 09:01:51 Strix kernel: 18eb8076: 8db4a3fff110 (0x8db4a3fff110) oct. 31 09:01:51 Strix kernel: 58beaab6: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: d7d391bc: c12f0c9c (_nv034838rm+0x1c/0x20 [nvidia]) oct. 31 09:01:51 Strix kernel: 3d9d3366: 8db51ef3d218 (0x8db51ef3d218) oct. 31 09:01:51 Strix kernel: eaaf8f98: c12ff249 (_nv003603rm+0x9/0x20 [nvidia]) oct. 31 09:01:51 Strix kernel: 79766f3e: 8db51ef3d028 (0x8db51ef3d028) oct. 31 09:01:51 Strix kernel: fbeb93a1: c12f425b (_nv004359rm+0x1b/0x80 [nvidia]) oct. 31 09:01:51 Strix kernel: 160c8872: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 40aecac9: 8db51949c810 (0x8db51949c810) oct. 31 09:01:51 Strix kernel: 5884ca89: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: f66282ec: c12f1897 (_nv011071rm+0x2d7/0x350 [nvidia]) oct. 31 09:01:51 Strix kernel: c77ee642: 8db517aaaf10 (0x8db517aaaf10) oct. 31 09:01:51 Strix kernel: f4fcb456: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: ef44b1aa: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 514af435: 00010049 (0x10049) oct. 31 09:01:51 Strix kernel: b0f4b16c: ... oct. 31 09:01:51 Strix kernel: 03a0e9a9: c0ce4a55 (_nv034837rm+0x1a5/0x1f0 [nvidia]) oct. 31 09:01:51 Strix kernel: 7a9ef523: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: 27d325ee: c1d3fe20 (_nv000488rm+0x1c/0xff69a1fc [nvidia]) oct. 31 09:01:51 Strix kernel: 4163f071: 8db517aaaf10 (0x8db517aaaf10) oct. 31 09:01:51 Strix kernel: 53a31c36: ... oct. 31 09:01:51 Strix kernel: b53af793: 8db51949c810 (0x8db51949c810) oct. 31 09:01:51 Strix kernel: d5350376: c12efe6e (_nv034836rm+0x24e/0x430 [nvidia]) oct. 31 09:01:51 Strix kernel: 75b21a0d: c1d3fe80 (_nv019251rm+0x20/0xff69a1a0 [nvidia]) oct. 31 09:01:51 Strix kernel: acf63617: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 6047e6a8: 00010049 (0x10049) oct. 31 09:01:51 Strix kernel: c3545543: ... oct. 31
[Kernel-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
Indeed, I forgot to upgrade so I missed the issue. Now that I did I see the hiss is indeed much louder. Thanks Kai for sending this upstream already. -- 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1850477] Re: eoan/linux-aws: 5.3.0-1006.6 -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 ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Promote to Proposed - phase-changed: Thursday, 31. October 2019 09:20 UTC + phase: Testing + phase-changed: Thursday, 31. October 2019 11:06 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1850477 Title: eoan/linux-aws: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 31. October 2019 11:06 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/1850477/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Acer aspire a715-71g. Same problem. Laptop overheating when i switch on nvidia proprietary driver. On ubuntu 17.10 it worked fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr10HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
[Kernel-packages] [Bug 1849721] Re: Raydium Touchscreen on ThinkPad L390 does not work
Can you please test this kernel: https://people.canonical.com/~khfeng/lp1849721+3/ -- 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/1849721 Title: Raydium Touchscreen on ThinkPad L390 does not work Status in linux package in Ubuntu: Confirmed Bug description: I have bought new Lenovo ThinkPad L390 with touchscreen and it works fine on Windows, but not on Ubuntu. I've tried Ubuntu LTS 18.4, 19.4 and 19.10. I've tried installing Ubuntu and running Live USB image, and also other distributions (Manjaro i3, Kubuntu). There is an Ubuntu certification with the same touchscreen using Ubuntu 18.4: https://certification.ubuntu.com/hardware/201812-26720 Other info: - `xinput` is showing touchscreen: "Raydium Touchscreen id=10 [slave pointer (2)]" - if I list device props using `xinput list-props 10`, I see device: `Device Node (277): "/dev/input/event9"` - `cat /dev/input/event9` does not produce anything - `xinput --test-xi2 --root` does not produce any touchscreen events, even though events from other devices are successfully shown Also, attached `ubuntu-bug` report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1821 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 18:32:07 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NRCTO1WW:pvrThinkPadL390:rvnLENOVO:rn20NRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NRCTO1WW dmi.product.sku: LENOVO_MT_20NR_BU_Think_FM_ThinkPad L390 dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849721/+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
