[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch
[Expired for linux (Ubuntu Disco) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Disco) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723223 Title: linux-lts and linux-hwe autopkgtests fail due to version mismatch Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Status in linux source package in Disco: Expired Bug description: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 exit 1 fi However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that invoke linux autopkgtests - for example, initramfs-tools, systemd, ... This requires unnecessary work to investigate the autopkgtest errors every time, only to find it's a autopkgtest error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch
[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723223 Title: linux-lts and linux-hwe autopkgtests fail due to version mismatch Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Status in linux source package in Disco: Expired Bug description: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 exit 1 fi However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that invoke linux autopkgtests - for example, initramfs-tools, systemd, ... This requires unnecessary work to investigate the autopkgtest errors every time, only to find it's a autopkgtest error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch
[Expired for linux (Ubuntu Cosmic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723223 Title: linux-lts and linux-hwe autopkgtests fail due to version mismatch Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Status in linux source package in Disco: Expired Bug description: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 exit 1 fi However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that invoke linux autopkgtests - for example, initramfs-tools, systemd, ... This requires unnecessary work to investigate the autopkgtest errors every time, only to find it's a autopkgtest error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723223 Title: linux-lts and linux-hwe autopkgtests fail due to version mismatch Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Status in linux source package in Disco: Expired Bug description: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 exit 1 fi However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that invoke linux autopkgtests - for example, initramfs-tools, systemd, ... This requires unnecessary work to investigate the autopkgtest errors every time, only to find it's a autopkgtest error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824800] Re: Sony Vaio VPCF13Z1E won't boot with kernel 5.0.0-11
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824800 Title: Sony Vaio VPCF13Z1E won't boot with kernel 5.0.0-11 Status in linux package in Ubuntu: Expired Bug description: Experienced on an up-to-date Disco system. I get past GRUB, but then the boot is stuck before GDM shows up. Instead there's just text on the screen, but nothing showing what the problem actually is. Used to boot fine - and still does - on 5.0.0-8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch
[Expired for linux (Ubuntu Trusty) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723223 Title: linux-lts and linux-hwe autopkgtests fail due to version mismatch Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Status in linux source package in Disco: Expired Bug description: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 exit 1 fi However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that invoke linux autopkgtests - for example, initramfs-tools, systemd, ... This requires unnecessary work to investigate the autopkgtest errors every time, only to find it's a autopkgtest error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723223 Title: linux-lts and linux-hwe autopkgtests fail due to version mismatch Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Status in linux source package in Disco: Expired Bug description: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 exit 1 fi However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that invoke linux autopkgtests - for example, initramfs-tools, systemd, ... This requires unnecessary work to investigate the autopkgtest errors every time, only to find it's a autopkgtest error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1832435] Re: Lenovo miix 510 wifi adapter cannot be turned on
Jeremy That commit certainly looks like it will solve the problem. I would love to test it bud do not know how do so from the directory you have pointed me to. I have never installed a kernel only. Can you point me to instructions on how do do so? Miguel On Thursday, June 13, 2019, 10:41:15 PM GMT+8, Jeremy <1832...@bugs.launchpad.net> wrote: Could you try the latest kernel at http://kernel.ubuntu.com/~kernel-ppa/mainline/ And see if the wifi works without blacklisting ideapad-laptop as a new commit may have fixed this https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/platform/x86/ideapad-laptop.c?id=5105e78e5b2414ec39efaadca1802e37e7105bb1 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware 1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion:
[Kernel-packages] [Bug 1832903] Re: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver
I was able to reproduce the problem with 4.15.0-51, but problem seems to be gone using the hwe kernel 4.18.0-21-generic. I'll do a kernel bisection and try to find the commit which fixes the situation. I'll also ask another impacted user to confirm if v4.18 works fine too, to double-check my testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu
Installed and booted your kernel, dmesg attached. The MAC address of the dock has not changed with the new kernel, still using the dock's own MAC instead of the laptop's. Thanks! ** Attachment added: "dmesg.tar.bz2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+attachment/5270883/+files/dmesg.tar.bz2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top-tech /Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MES1WH00 dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1 dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832590] Re: linux-fips: -proposed tracker
** Tags added: apw-test -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832590 Title: linux-fips: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: 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-signing-to-proposed 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 package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 phase: Holding before Packaging phase-changed: Wednesday, 12. June 2019 14:37 UTC reason: prepare-package: Stalled -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832590] Re: linux-fips: -proposed tracker
update test ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832590 Title: linux-fips: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: 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-signing-to-proposed 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 package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 phase: Holding before Packaging phase-changed: Wednesday, 12. June 2019 14:37 UTC reason: prepare-package: Stalled -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832909] [NEW] Cache line contention prevents scaling of 100Gbps performance
Public bug reported: [Impact] 100Gbps network performance, as measured on an hns3 controller, doesn't scale as queue size goes up. [Test Case] Use a traffic generator instrument to generate load, using the SUT as an IP forwarder. 19.04 today: 8 queue 12 queue 16 queue 24 queue 37G 45G 38G 33G With the patch applied: 8 queue 12 queue 16 queue 24 queue 37G 50G 47G 47G [Fix] 14bd9a607f908 iommu/iova: Separate atomic variables to improve performance [Regression Risk] The patch makes no functional change, just reorders members of a structure. However, it is possible that this has unforeseen negative performance impacts on some platform. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832909 Title: Cache line contention prevents scaling of 100Gbps performance Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] 100Gbps network performance, as measured on an hns3 controller, doesn't scale as queue size goes up. [Test Case] Use a traffic generator instrument to generate load, using the SUT as an IP forwarder. 19.04 today: 8 queue 12 queue 16 queue 24 queue 37G 45G 38G 33G With the patch applied: 8 queue 12 queue 16 queue 24 queue 37G 50G 47G 47G [Fix] 14bd9a607f908 iommu/iova: Separate atomic variables to improve performance [Regression Risk] The patch makes no functional change, just reorders members of a structure. However, it is possible that this has unforeseen negative performance impacts on some platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832316] Re: shiftfs: allow changing ro/rw for subvolumes
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832316 Title: shiftfs: allow changing ro/rw for subvolumes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Bug description: SRU Justification Impact: Stéphane reported regression for btrfs workloads employing shiftfs. Unprivileged users can already toggle whether a subvolume will be ro or rw. This is broken on current shiftfs as we haven't whitelisted these ioctls(). Fix: To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO, BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. All of them should be safe for unprivileged users. Regression Potential: Limited to shiftfs. Test Case: Tested with LXD running shiftfs on top of btrfs and verified btrfs subvolumes can be made ro or rw. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832903] 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 1832903 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832903] [NEW] 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver
Public bug reported: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [44] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: vmwgfx Kernel modules: vmwgfx ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Description changed: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login - screen doesn't work if it 'wayland' is in use (default) and if video - kernel driver inside is 'vgwfx'. + screen doesn't work if 'Wayland' is in use (default) and if video kernel + driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Force the login screen to use x11: + - Access the machine via ssh or any other recovery approaches. + - Force the login screen to use x11: - File: /etc/gdm3/custom.conf + File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false - I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. - So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. + I tried to reproduce the behaviour on my personal laptop, KVM guest, ... + without success. + So far it is only reproducible when the 'vgwfx' driver is in use in + combination with Wayland. + + lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) - Subsystem: VMware SVGA II Adapter [15ad:0405] - Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- - Capabilities: [44] PCI Advanced Features - AFCap: TP+ FLR+ - AFCtrl: FLR- - AFStatus: TP- - Kernel driver in use: vmwgfx - Kernel modules: vmwgfx + Subsystem: VMware SVGA II Adapter [15ad:0405] + Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- + Capabilities: [44] PCI Advanced Features + AFCap: TP+ FLR+ + AFCtrl: FLR- + AFStatus: TP- + Kernel driver in use: vmwgfx + Kernel modules: vmwgfx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832903 Title: 18.04.2 login screen doesn't work if it uses 'wayland' and if video kernel driver is 'vgwfx' kernel driver Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login screen doesn't work if 'Wayland' is in use (default) and if video kernel driver is 'vgwfx'. It looks like the login screen got stuck, doesn't exit, and doesn't fallback to 'x11' by itself in case of failure. Workaround: - Access the machine via ssh or any other recovery approaches. - Force the login screen to use x11: File: /etc/gdm3/custom.conf [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false I tried to reproduce the behaviour on my personal laptop, KVM guest, ... without success. So far it is only reproducible when the 'vgwfx' driver is in use in combination with Wayland. lspci -nnvvv 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405]
[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list
On my Disco Dingo see this also, though it doesn't seem to have any negative effect. kernel: 5.0.0-16-generic secureboot: Secure boot could not be determined (mode 0) [2.243394] Loaded X.509 cert 'Build time autogenerated kernel key: ...' [2.267416] Couldn't get size: 0x800e [2.267418] MODSIGN: Couldn't get UEFI db list [2.279452] Couldn't get size: 0x800e [2.279454] MODSIGN: Couldn't get UEFI MokListRT [2.291440] Couldn't get size: 0x800e [2.291443] MODSIGN: Couldn't get UEFI dbx list [2.291467] zswap: loaded using pool lzo/zbud motherboard : Asus Crosshair V formula - not capable of secure boot cpu : FX8320 This shows up also in openSUSE Tumbleweed with the 5 series kernel. Not present in Fedora. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743908 Title: MODSIGN: Couldn't get UEFI db list Status in linux package in Ubuntu: Fix Released Bug description: Kernel is having problem loading or validating certificates. Looking over the internet looks like this is a kernel issue. Patchs from other distro: https://bugzilla.redhat.com/show_bug.cgi?id=1497559 - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734' [1.203352] Couldn't get size: 0x800e [1.203354] MODSIGN: Couldn't get UEFI db list [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys keyring [1.205102] Couldn't get size: 0x800e [1.205103] MODSIGN: Couldn't get UEFI dbx list ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wellington 1429 F pulseaudio /dev/snd/pcmC1D3p: wellington 1429 F...m pulseaudio /dev/snd/controlC1: wellington 1429 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 22:37:13 2018 HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e InstallationDate: Installed on 2018-01-16 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 R5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] Re: Backport VMW_PVRDMA PPN64 patch
** Changed in: linux (Debian) Status: Unknown => 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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: New Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 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-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1829912] Re: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad.
Find attached message On Fri 14 Jun, 2019, 11:30 PM Phaneesh G, wrote: > Sorry for the late reply, > The sound quality is still the same. > > While trying to install the fix, I get this message (attached), Am I > missing something? > > On Mon 27 May, 2019, 4:45 PM Hui Wang, wrote: > >> consulted with realtek engineer, and got a patch from him. >> >> please test this dkms as comment #6, if the audio works well after >> installing this dkms. >> >> thx. >> >> >> ** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb" >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+attachment/5266881/+files/oem-audio-hda-daily-dkms_0.1_all.deb >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1829912 >> >> Title: >> [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very >> bad. >> >> Status in linux package in Ubuntu: >> Incomplete >> >> Bug description: >> I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The >> audio quality in Ubuntu is horrible to say the least, It is very low, and >> in case I use VLC or enable overamplification, the quality of sound output >> becomes worse. >> I have ensured that the volume on alsamixer is 100. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 18.04 >> Package: pulseaudio 1:11.1-1ubuntu7.2 >> ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 >> Uname: Linux 4.18.0-20-generic x86_64 >> NonfreeKernelModules: nvidia_modeset nvidia >> ApportVersion: 2.20.9-0ubuntu7.6 >> Architecture: amd64 >> AudioDevicesInUse: >>USERPID ACCESS COMMAND >>/dev/snd/controlC0: phaneesh 1605 F pulseaudio >> CurrentDesktop: ubuntu:GNOME >> Date: Tue May 21 23:41:49 2019 >> InstallationDate: Installed on 2019-05-17 (4 days ago) >> InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 >> (20190210) >> ProcEnviron: >>LANGUAGE=en_IN:en >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_IN >>SHELL=/bin/bash >> SourcePackage: pulseaudio >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 06/13/2018 >> dmi.bios.vendor: LENOVO >> dmi.bios.version: 8TCN44WW >> dmi.board.asset.tag: NO Asset Tag >> dmi.board.name: LNVNB161216 >> dmi.board.vendor: LENOVO >> dmi.board.version: NO DPK >> dmi.chassis.asset.tag: NO Asset Tag >> dmi.chassis.type: 10 >> dmi.chassis.vendor: LENOVO >> dmi.chassis.version: Lenovo ideapad 330-15IKB >> dmi.modalias: >> dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: >> dmi.product.family: ideapad 330-15IKB >> dmi.product.name: 81DE >> dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB >> dmi.product.version: Lenovo ideapad 330-15IKB >> dmi.sys.vendor: LENOVO >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+subscriptions >> > ** Attachment added: "IMG_20190614_232901125.jpg" https://bugs.launchpad.net/bugs/1829912/+attachment/5270838/+files/IMG_20190614_232901125.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/1829912 Title: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad. Status in linux package in Ubuntu: Incomplete Bug description: I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The audio quality in Ubuntu is horrible to say the least, It is very low, and in case I use VLC or enable overamplification, the quality of sound output becomes worse. I have ensured that the volume on alsamixer is 100. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phaneesh 1605 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 21 23:41:49 2019 InstallationDate: Installed on 2019-05-17 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Kernel-packages] [Bug 1832863] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270830/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270837/+files/WifiSyslog.txt ** 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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270836/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270833/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270834/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270831/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270832/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270827/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270835/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270828/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1829912] Re: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad.
Sorry for the late reply, The sound quality is still the same. While trying to install the fix, I get this message (attached), Am I missing something? On Mon 27 May, 2019, 4:45 PM Hui Wang, wrote: > consulted with realtek engineer, and got a patch from him. > > please test this dkms as comment #6, if the audio works well after > installing this dkms. > > thx. > > > ** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+attachment/5266881/+files/oem-audio-hda-daily-dkms_0.1_all.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1829912 > > Title: > [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very > bad. > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The > audio quality in Ubuntu is horrible to say the least, It is very low, and > in case I use VLC or enable overamplification, the quality of sound output > becomes worse. > I have ensured that the volume on alsamixer is 100. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: pulseaudio 1:11.1-1ubuntu7.2 > ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 > Uname: Linux 4.18.0-20-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: phaneesh 1605 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Tue May 21 23:41:49 2019 > InstallationDate: Installed on 2019-05-17 (4 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > SourcePackage: pulseaudio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/13/2018 > dmi.bios.vendor: LENOVO > dmi.bios.version: 8TCN44WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: LNVNB161216 > dmi.board.vendor: LENOVO > dmi.board.version: NO DPK > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo ideapad 330-15IKB > dmi.modalias: > dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: > dmi.product.family: ideapad 330-15IKB > dmi.product.name: 81DE > dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB > dmi.product.version: Lenovo ideapad 330-15IKB > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829912/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829912 Title: [Lenovo ideapad 330-15IKB] Sound very low, and quality of audio very bad. Status in linux package in Ubuntu: Incomplete Bug description: I am on a Lenovo Ideapad 330. I've switched to Ubuntu from Windows. The audio quality in Ubuntu is horrible to say the least, It is very low, and in case I use VLC or enable overamplification, the quality of sound output becomes worse. I have ensured that the volume on alsamixer is 100. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phaneesh 1605 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 21 23:41:49 2019 InstallationDate: Installed on 2019-05-17 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad
[Kernel-packages] [Bug 1832863] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270829/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270825/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270826/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1742 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 InstallationDate: Installed on 2014-09-08 (1739 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK Computer INC. 1015PE Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] Re: Kernel 4.4.0.145 (& subsequent) boots to black screen.
apport information ** Tags added: apport-collected ** Description changed: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: chris 1742 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=fc4e1a58-00d6-42a0-b9a3-299f5504ebe4 + InstallationDate: Installed on 2014-09-08 (1739 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) + MachineType: ASUSTeK Computer INC. 1015PE + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=54ac8c35-d4b0-463a-9d75-61e88d737f11 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. + RelatedPackageVersions: + linux-restricted-modules-4.4.0-142-generic N/A + linux-backports-modules-4.4.0-142-generic N/A + linux-firmware 1.157.21 + Tags: xenial + Uname: Linux 4.4.0-142-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2019-01-01 (164 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/06/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0801 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: 1015PE + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: x.xx + dmi.chassis.asset.tag: 0x + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK Computer INC. + dmi.chassis.version: x.x + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd10/06/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: + dmi.product.name: 1015PE + dmi.product.version: x.x + dmi.sys.vendor: ASUSTeK Computer INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1832863/+attachment/5270824/+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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Confirmed Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk
[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000
I also installed networkd-dispatcher and added in the directory routable.d a file with #!/bin/sh ethtool -K eno1 gso off gro off tso off rx off tx off so i don't have to manual change the settings when rebooting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Confirmed Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel: [30304.199099] smp_apic_timer_interrupt+0x79/0x140 Jun 8 12:11:17 mc2 kernel: [30304.199100] apic_timer_interrupt+0xf/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199101] Jun 8 12:11:17 mc2
[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Can you check the nic settings and see if hidma is fixed or not? (ethtool -k ) If it is not fixed, then try disable it ethtool -K highdma off https://lauri.xn--vsandi-pxa.com/2016/02/fixing-broadcom-bcm5762-on- ubuntu.html Another option is to disable netplan and switch to networkd-systemd so you can set (this is the first thing i tried) [NETWORK] IgnoreCarrierLoss=true ConfigureWithoutCarrier=true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Confirmed Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel:
[Kernel-packages] [Bug 1832544] Re: linux-snapdragon: 4.15.0-1056.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832543 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:34 UTC + phase: Packaging + phase-changed: Friday, 14. June 2019 17:33 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1832544 Title: linux-snapdragon: 4.15.0-1056.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832543 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Packaging phase-changed: Friday, 14. June 2019 17:33 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832544] Re: linux-snapdragon: 4.15.0-1056.60 -proposed tracker
** Summary changed: - linux-snapdragon: -proposed tracker + linux-snapdragon: 4.15.0-1056.60 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1832544 Title: linux-snapdragon: 4.15.0-1056.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832543 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Holding before Packaging phase-changed: Wednesday, 12. June 2019 14:34 UTC reason: prepare-package: Stalled -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump
On Fri, Jun 14, 2019 at 11:20 AM Thadeu Lima de Souza Cascardo < 1832...@bugs.launchpad.net> wrote: > Manoj, > > How reproducible is this? Did you try multiple times? Did you only see > this on cosmic? > It reproduces in this form only on Cosmic, and I have been able to repro this a few times on this particular power9 (tesilius) > > I haven't been able to see this on an LPAR. This is certainly specific > to Power9, by the stack trace, as it involves the power9 idle driver. > However this issue seems to be isolated to this particular power9 system (tesilius) which is development grade system, and I was not able to repro this on lewis which is another development grade power9 system. I have done a few experiments and looks like the issue might be hardware related. I was sometimes running into CPU hard lockups on this system during my experiments. The production level power9s are currently being used by others, and IBM is shipping us our witherspoon power9 back next week after proc/fw upgrades. Also these two development systems are scheduled to be shipped back to IBM soon for upgrade to production hardware. I will retest this on the witherpoon that we will receive next week and report back if this can be reproduced there. If not I will close this as invalid. > Still, I haven't found anything on new kernels that seem to fix anything > like this, so it's possible newer releases are still affected. > > On the other hand, there doesn't seem to be anything here that looks > specific to kdump. Maybe the use of nr_cpus=1 or a kernel that is > kexec'ed. So, it would be interesting to try these as well. > > Finally, if you can reproduce it, we should coordinate, so we turn xmon > on and I can grab the system and take a look. > > Thanks. > Cascardo. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832388 > > Title: > [power9] [Cosmic] kernel panic while testing kdump > > Status in The Ubuntu-power-systems project: > New > Status in linux package in Ubuntu: > Incomplete > Status in linux source package in Cosmic: > Incomplete > > Bug description: > I installed cosmic on power9 (boston) a non-nvme system, installed > initramfs-tools from -proposed and install kdump-tools. Triggered a > dump, but I got a kernel panic. This might be a kernel bug/regression. > > ubuntu@tiselius:~$ uname -a > Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC > 2019 ppc64le ppc64le ppc64le GNU/Linux > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ apt policy initramfs-tools > initramfs-tools: > Installed: 0.131ubuntu15.2 > Candidate: 0.131ubuntu15.2 > Version table: >*** 0.131ubuntu15.2 500 > 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main > ppc64el Packages > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ apt policy kdump-tools > kdump-tools: > Installed: 1:1.6.5-1ubuntu1~18.10.1 > Candidate: 1:1.6.5-1ubuntu1~18.10.1 > Version table: >*** 1:1.6.5-1ubuntu1~18.10.1 500 > 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main > ppc64el Packages > 100 /var/lib/dpkg/status >1:1.6.4-2ubuntu1 500 > 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el > Packages > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ sudo kdump-config show > DUMP_MODE:kdump > USE_KDUMP:1 > KDUMP_SYSCTL: kernel.panic_on_oops=1 > KDUMP_COREDIR:/var/crash > crashkernel addr: > /var/lib/kdump/vmlinuz: symbolic link to > /boot/vmlinux-4.18.0-21-generic > kdump initrd: > /var/lib/kdump/initrd.img: symbolic link to > /var/lib/kdump/initrd.img-4.18.0-21-generic > current state:ready to kdump > > kexec command: > /sbin/kexec -p > --command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro > console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll > noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img > /var/lib/kdump/vmlinuz > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ cat /proc/cmdline > root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 > crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ dmesg | grep Reser > [0.00] Reserving 4096MB of memory at 128MB for crashkernel > (System RAM: 131072MB) > [0.00] cma: Reserved 6560 MiB at 0x200e6200 > ubuntu@tiselius:~$ > > root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq > root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger > > tiselius login: [ 150.167288] cloud-init[4529]: Cloud-init v. > 19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun > 2019 19:53:40 +. Up 149.80 seconds. > [ 150.167687] cloud-init[4529]: Cloud-init v. > 19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 > +. Datasource DataSourceMAAS [ >
[Kernel-packages] [Bug 1832782] Re: Backport VMW_PVRDMA PPN64 patch
** Bug watch added: Debian Bug tracker #930501 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930501 ** Also affects: linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930501 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Unknown Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 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-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832613] Re: Scrolling up is broken (affects also stuff like brightness setting or color HLSA)
Something breaks scrolling, I hope you can spot the difference if you Page Down before you start scrolling. Fix: Page Down before you scroll, never touch the edges. >:] ** Summary changed: - Scrolling up is broken (affects also stuff like brightness setting or color HLSA) + You can't scroll "indefinitely" without performance penalty >:] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832613 Title: You can't scroll "indefinitely" without performance penalty >:] Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Unknown Bug description: Anything that's allowed to set lowest to highest setting seems simply broken for some reason. e.g. volume, brightness settings are broken, as is scroll (web browser for example). More interesting example would be relocating focused tab to first position before closing it, for example in Chromium browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] 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 1832863 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: Incomplete Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832290] Re: Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle
*** This bug is a duplicate of bug 1825235 *** https://bugs.launchpad.net/bugs/1825235 ** This bug has been marked a duplicate of bug 1825235 Load average inexplicably high with 5.0 kernel on rpi -- 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/1832290 Title: Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: $ uptime 12:40:44 up 1 day, 10:56, 1 user, load average: 4.00, 4.02, 4.00 The load is always reported as higher than 4 even on an idle system. Seems to be this upstream: https://github.com/raspberrypi/linux/issues/2881 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9 ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8 Uname: Linux 5.0.0-1009-raspi2 aarch64 ApportVersion: 2.20.10-0ubuntu27 Architecture: arm64 Date: Tue Jun 11 12:33:57 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi2 UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1832290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832542] Re: linux-raspi2: 4.15.0-1039.41 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832541 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:34 UTC + phase: Packaging + phase-changed: Friday, 14. June 2019 16:04 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1832542 Title: linux-raspi2: 4.15.0-1039.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832541 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Packaging phase-changed: Friday, 14. June 2019 16:04 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump
Manoj, How reproducible is this? Did you try multiple times? Did you only see this on cosmic? I haven't been able to see this on an LPAR. This is certainly specific to Power9, by the stack trace, as it involves the power9 idle driver. Still, I haven't found anything on new kernels that seem to fix anything like this, so it's possible newer releases are still affected. On the other hand, there doesn't seem to be anything here that looks specific to kdump. Maybe the use of nr_cpus=1 or a kernel that is kexec'ed. So, it would be interesting to try these as well. Finally, if you can reproduce it, we should coordinate, so we turn xmon on and I can grab the system and take a look. Thanks. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832388 Title: [power9] [Cosmic] kernel panic while testing kdump Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: I installed cosmic on power9 (boston) a non-nvme system, installed initramfs-tools from -proposed and install kdump-tools. Triggered a dump, but I got a kernel panic. This might be a kernel bug/regression. ubuntu@tiselius:~$ uname -a Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy initramfs-tools initramfs-tools: Installed: 0.131ubuntu15.2 Candidate: 0.131ubuntu15.2 Version table: *** 0.131ubuntu15.2 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy kdump-tools kdump-tools: Installed: 1:1.6.5-1ubuntu1~18.10.1 Candidate: 1:1.6.5-1ubuntu1~18.10.1 Version table: *** 1:1.6.5-1ubuntu1~18.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:1.6.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ sudo kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-21-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz ubuntu@tiselius:~$ ubuntu@tiselius:~$ cat /proc/cmdline root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M ubuntu@tiselius:~$ ubuntu@tiselius:~$ dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x200e6200 ubuntu@tiselius:~$ root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger tiselius login: [ 150.167288] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 19:53:40 +. Up 149.80 seconds. [ 150.167687] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. Datasource DataSourceMAAS [http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/]. Up 150.11 seconds [ 360.313029] kdump-tools[4915]: Stopping kdump-tools: * unloaded kdump kernel [ 376.552452] kdump-tools[10449]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz [ 376.553743] kdump-tools[10449]: * Creating symlink /var/lib/kdump/initrd.img [ 376.585085] kdump-tools[10449]: Modified cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158784K [ 376.953223] kdump-tools[10449]: * loaded kdump kernel [ 398.517900] sysrq: SysRq : Trigger a crash [ 398.517952] Unable to handle kernel paging request for data at address 0x [ 398.518000] Faulting instruction address: 0xc082a3a8 [ 398.518071] Oops: Kernel access of bad area, sig: 11 [#1] [ 398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV [ 398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core
[Kernel-packages] [Bug 1830435] Re: libsas: old linkrate advertised after phy disabled
** Description changed: [Impact] sysfs continues to expose a valid phy linkrate even after the phy has been disabled. [Test Case] Using hisi_sas, a libsas-based driver: (initramfs) cd /sys/class/sas_phy/phy-0\:0\:20 (initramfs) cat negotiated_linkrate 12.0 Gbit (initramfs) echo 0 > enable [ 59.172411] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe [ 59.178851] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=4028 task=bb3ab63f dev id=1 CQ hdr: 0x1103 0x10fbc 0x0 0x2 Error info: 0x0 0x400 0x0 0x0 [ 59.194139] sas: smp_execute_task_sg: task to dev 500e004aaa1f response: 0x0 status 0x2 (initramfs) cat negotiated_linkrate 12.0 Gbit + (Note to self: d06-1 has the setup to reproduce this) + [Fix] d8649fc1c5e40 scsi: libsas: Do discovery on empty PHY to update PHY info 085f104a83d56 scsi: libsas: Inject revalidate event for root port event [Regression Risk] Impact is limited to drivers built on top of libsas. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830435 Title: libsas: old linkrate advertised after phy disabled Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] sysfs continues to expose a valid phy linkrate even after the phy has been disabled. [Test Case] Using hisi_sas, a libsas-based driver: (initramfs) cd /sys/class/sas_phy/phy-0\:0\:20 (initramfs) cat negotiated_linkrate 12.0 Gbit (initramfs) echo 0 > enable [ 59.172411] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe [ 59.178851] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=4028 task=bb3ab63f dev id=1 CQ hdr: 0x1103 0x10fbc 0x0 0x2 Error info: 0x0 0x400 0x0 0x0 [ 59.194139] sas: smp_execute_task_sg: task to dev 500e004aaa1f response: 0x0 status 0x2 (initramfs) cat negotiated_linkrate 12.0 Gbit (Note to self: d06-1 has the setup to reproduce this) [Fix] d8649fc1c5e40 scsi: libsas: Do discovery on empty PHY to update PHY info 085f104a83d56 scsi: libsas: Inject revalidate event for root port event [Regression Risk] Impact is limited to drivers built on top of libsas. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832151] Re: Unexpected CFS throttling
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832151 Title: Unexpected CFS throttling Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: Basically, this issue: https://bugzilla.kernel.org/show_bug.cgi?id=198197 ..is affecting a cloud provider on a 4.15 kernel. Customer testing with a kernel that is patched with the fix (upstream: 512ac999d2755d2b7109e996a76b6fb8b888631d ) confirms that it resolves the issue. More details in: https://canonical.my.salesforce.com/5003z1yUmC1 This bug is for SRU patch-tracking only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830435] Re: phy linkrate persists after deactivation
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) ** Summary changed: - phy linkrate persists after deactivation + libsas: old linkrate advertised after phy disabled ** Description changed: [Impact] sysfs continues to expose a valid phy linkrate even after the phy has been disabled. [Test Case] Using hisi_sas, a libsas-based driver: (initramfs) cd /sys/class/sas_phy/phy-0\:0\:20 - (initramfs) cat negotiated_linkrate + (initramfs) cat negotiated_linkrate 12.0 Gbit - (initramfs) echo 0 > enable + (initramfs) echo 0 > enable [ 59.172411] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe [ 59.178851] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=4028 task=bb3ab63f dev id=1 CQ hdr: 0x1103 0x10fbc 0x0 0x2 Error info: 0x0 0x400 0x0 0x0 [ 59.194139] sas: smp_execute_task_sg: task to dev 500e004aaa1f response: 0x0 status 0x2 - (initramfs) cat negotiated_linkrate + (initramfs) cat negotiated_linkrate 12.0 Gbit + + [Fix] + d8649fc1c5e40 scsi: libsas: Do discovery on empty PHY to update PHY info + 085f104a83d56 scsi: libsas: Inject revalidate event for root port event [Regression Risk] Impact is limited to drivers built on top of libsas. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830435 Title: libsas: old linkrate advertised after phy disabled Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] sysfs continues to expose a valid phy linkrate even after the phy has been disabled. [Test Case] Using hisi_sas, a libsas-based driver: (initramfs) cd /sys/class/sas_phy/phy-0\:0\:20 (initramfs) cat negotiated_linkrate 12.0 Gbit (initramfs) echo 0 > enable [ 59.172411] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe [ 59.178851] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=4028 task=bb3ab63f dev id=1 CQ hdr: 0x1103 0x10fbc 0x0 0x2 Error info: 0x0 0x400 0x0 0x0 [ 59.194139] sas: smp_execute_task_sg: task to dev 500e004aaa1f response: 0x0 status 0x2 (initramfs) cat negotiated_linkrate 12.0 Gbit [Fix] d8649fc1c5e40 scsi: libsas: Do discovery on empty PHY to update PHY info 085f104a83d56 scsi: libsas: Inject revalidate event for root port event [Regression Risk] Impact is limited to drivers built on top of libsas. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832542] Re: linux-raspi2: 4.15.0-1039.41 -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + linux-raspi2: 4.15.0-1039.41 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1832542 Title: linux-raspi2: 4.15.0-1039.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832541 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Holding before Packaging phase-changed: Wednesday, 12. June 2019 14:34 UTC reason: prepare-package: Stalled -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Just tested it. Totally disables the touchpad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] Re: Kernel 4.4.0.145 (& subsequent) boots to black screen.
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832863 Title: Kernel 4.4.0.145 (& subsequent) boots to black screen. Status in linux package in Ubuntu: New Bug description: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832863] [NEW] Kernel 4.4.0.145 (& subsequent) boots to black screen.
You have been subscribed to a public bug: On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to kernel 4.4.0.145 on 3 April 2019. On the first boot after the update, I got the usual grub screen, then "Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went black with no mouse pointer or invite. I could hear disk activity ( & see the disk-activity light) then the usual drumroll for login, but the screen stayed black. I escaped using REISUO & retried several times with the same result. If I wait for the login drumroll then input my login, there is more disk activity (setting up the desktop) but the screen stays black. So the PC is not freezing, just no screen. Trying Ctrl+Alt+F1 (or other F keys) produces nothing. I can continue to use the PC normally if I select the previous kernel 4.4.0.142 at the grub screen. On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black screen as with .145. So I am unable to use this PC AT ALL with current kernels. I asked about this problem on Ubuntu Forum https://ubuntuforums.org/showthread.php?t=2415972 with no success & the suggestion was to raise this bug... There may be useful information in that thread, including this output from "inxi -Fzr" (run in good kernel .142). chris@Netbk:~$ inxi -Fzr System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit) Desktop: Unity 7.4.5 Distro: Ubuntu 16.04 xenial Machine: System: ASUSTeK (portable) product: 1015PE v: x.x Mobo: ASUSTeK model: 1015PE v: x.xx Bios: American Megatrends v: 0801 date: 10/06/2010 CPU: Single core Intel Atom N455 (-HT-) cache: 512 KB clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz Graphics: Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.00hz GLX Renderer: Mesa DRI Intel Pineview M GLX Version: 1.4 Mesa 18.0.5 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Kernel 4.4.0.145 (& subsequent) boots to black screen. https://bugs.launchpad.net/bugs/1832863 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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
I think I have - can't remember. It was a few months ago. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752194] Re: Intel GPU tools crash with "Couldn't map MMIO region"
I have exactly the same "Couldn't map MMIO region: Operation not permitted"
problem with Ubuntu 19.04.
==
(intel_gpu_top:23801) intel-mmio-CRITICAL: Test assertion failure function
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23801) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23801) intel-mmio-CRITICAL: Last errno: 1, Operation not
permitted
(intel_gpu_top:23801) intel-mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
#0 [_init+0x7b87]
#1 [_init+0x5420]
#2 [_init+0xe85]
#3 [__libc_start_main+0xeb]
#4 [_init+0x1c92]
Test (null) failed.
DEBUG
(intel_gpu_top:23801) intel-chipset-DEBUG: Test requirement passed: pci_dev
(intel_gpu_top:23801) intel-mmio-CRITICAL: Test assertion failure function
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23801) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23801) intel-mmio-CRITICAL: Last errno: 1, Operation not
permitted
(intel_gpu_top:23801) intel-mmio-CRITICAL: Couldn't map MMIO region
(intel_gpu_top:23801) igt-core-INFO: Stack trace:
(intel_gpu_top:23801) igt-core-INFO: #0 [_init+0x7b87]
(intel_gpu_top:23801) igt-core-INFO: #1 [_init+0x5420]
(intel_gpu_top:23801) igt-core-INFO: #2 [_init+0xe85]
(intel_gpu_top:23801) igt-core-INFO: #3 [__libc_start_main+0xeb]
(intel_gpu_top:23801) igt-core-INFO: #4 [_init+0x1c92]
END
FAIL (-1.000s)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1752194
Title:
Intel GPU tools crash with "Couldn't map MMIO region"
Status in intel-gpu-tools package in Ubuntu:
Confirmed
Bug description:
Trying to run anything in intel-gpu-tools (tested intel_gpu_top,
intel_gpu_time and intel_backlight) on my laptop (which has hybrid graphics,
GTX 760m (proprietary nvidia driver not installed right now) + Intel 4th gen
iGPU) as root yields the following output:
(intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not
permitted
(intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
#0 [_init+0x1753f]
#1 [_init+0xc978]
#2 [_init+0x118d]
#3 [__libc_start_main+0xf1]
#4 [_init+0x1fba]
#5 [+0x1fba]
Test (null) failed.
DEBUG
(intel_gpu_top:23021) intel-chipset-DEBUG: Test requirement passed: pci_dev
(intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not
permitted
(intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
(intel_gpu_top:23021) igt-core-INFO: Stack trace:
(intel_gpu_top:23021) igt-core-INFO: #0 [_init+0x1753f]
(intel_gpu_top:23021) igt-core-INFO: #1 [_init+0xc978]
(intel_gpu_top:23021) igt-core-INFO: #2 [_init+0x118d]
(intel_gpu_top:23021) igt-core-INFO: #3 [__libc_start_main+0xf1]
(intel_gpu_top:23021) igt-core-INFO: #4 [_init+0x1fba]
(intel_gpu_top:23021) igt-core-INFO: #5 [+0x1fba]
END
FAIL (-1.000s)
Happens under bot Wayland and XOrg.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: intel-gpu-tools 1.20-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 00:30:15 2018
InstallationDate: Installed on 2015-11-25 (825 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: intel-gpu-tools
UpgradeStatus: Upgraded to artful on 2017-11-01 (118 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1752194/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787904] Re: [radeon] machine crash after GPU reset
Experienced crashes under kernel 4.15.0-51 after resuming from suspend on a Dell Latitude E6540 running BIOS version A12 with the following graphics hardware: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] After upgrading to kernel 5.0.0-16 seems to not be reoccurring. After searching online seems that the issues possibly relate to the issue fixed by this patch: https://patchwork.kernel.org/patch/10813959/ Interestingly I don't seem to see it included in kernel 5.0.0-16... Here are some kernel logs showing the issue: Jun 13 22:41:54 *** kernel: [38511.640938] acpi device:41: Cannot transition to power state D3hot for parent in (unknown) Jun 13 22:41:54 *** kernel: [38511.691197] wlp3s0: deauthenticating from 9c:d6:43:ce:eb:7a by local choice (Reason: 3=DEAUTH_LEAVING) Jun 13 22:41:54 *** kernel: [38511.710803] radeon :01:00.0: Refused to change power state, currently in D3 Jun 13 22:41:54 *** kernel: [38511.792418] radeon :01:00.0: Refused to change power state, currently in D3 Jun 13 22:41:54 *** kernel: [38511.812417] radeon :01:00.0: Refused to change power state, currently in D3 Jun 13 22:41:59 *** kernel: [38516.721783] PM: suspend entry (deep) [System suspended] Jun 13 23:07:54 *** kernel: [38516.721784] PM: Syncing filesystems ... done. Jun 13 23:07:54 *** kernel: [38516.769515] Freezing user space processes ... Jun 13 23:07:54 *** kernel: [38516.816504] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting Jun 13 23:07:54 *** kernel: [38516.816525] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing D1B2 (len 62, WS 0, PS 0) @ 0xD1CE Jun 13 23:07:54 *** kernel: [38516.816534] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B914 (len 236, WS 4, PS 0) @ 0xB9E1 Jun 13 23:07:54 *** kernel: [38516.816543] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B872 (len 74, WS 0, PS 8) @ 0xB87A Jun 13 23:07:54 *** kernel: [38516.817400] [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed Jun 13 23:07:54 *** kernel: [38516.817413] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed Jun 13 23:07:54 *** kernel: [38516.817417] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e Jun 13 23:07:54 *** kernel: [38516.817417] [drm] enabling PCIE gen 3 link speeds, disable with radeon.pcie_gen2=0 Jun 13 23:07:54 *** kernel: [38517.376157] radeon :01:00.0: Wait for MC idle timedout ! Jun 13 23:07:54 *** kernel: [38517.484936] radeon :01:00.0: Wait for MC idle timedout ! Jun 13 23:07:54 *** kernel: [38517.493371] [drm] PCIE GART of 2048M enabled (table at 0x001D6000). Jun 13 23:07:54 *** kernel: [38517.493468] radeon :01:00.0: WB enabled Jun 13 23:07:54 *** kernel: [38517.493470] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0xa0d314c4 Jun 13 23:07:54 *** kernel: [38517.493471] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x58fe2292 Jun 13 23:07:54 *** kernel: [38517.493472] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x95a12eba Jun 13 23:07:54 *** kernel: [38517.493473] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x965b6556 Jun 13 23:07:54 *** kernel: [38517.493474] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x1907e776 Jun 13 23:07:54 *** kernel: [38517.493671] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xcf9b1760 Jun 13 23:07:54 *** kernel: [38517.602966] radeon :01:00.0: failed VCE resume (-110). Jun 13 23:07:54 *** kernel: [38518.585588] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) Jun 13 23:07:54 *** kernel: [38518.585601] [drm:si_resume [radeon]] *ERROR* si startup failed on resume Jun 13 23:07:54 *** kernel: [38518.586403] [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed Jun 13 23:07:54 *** kernel: [38518.586415] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed Jun 13 23:07:54 *** kernel: [38518.617080] (elapsed 1.847 seconds) done. Jun 13 23:07:54 *** kernel: [38518.617083] OOM killer disabled. Jun 13 23:07:54 *** kernel: [38518.617083] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jun 13 23:07:54 *** kernel: [38518.618463] Suspending console(s) (use no_console_suspend to debug) [...] Jun 13 23:07:54 *** kernel: [38519.445085] ACPI: EC: interrupt blocked Jun 13 23:07:54 *** kernel: [38519.466649] ACPI: Preparing to enter system sleep state S3 Jun 13 23:07:54 *** kernel: [38519.470503] ACPI: EC: event blocked Jun 13 23:07:54 *** kernel: [38519.470504] ACPI: EC: EC stopped [...] Jun 13 23:07:54 ***
[Kernel-packages] [Bug 1832496] Re: linux-raspi2: 4.18.0-1017.19 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832508 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 11:32 UTC + phase: Packaging + phase-changed: Friday, 14. June 2019 14:02 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1832496 Title: linux-raspi2: 4.18.0-1017.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832508 phase: Packaging phase-changed: Friday, 14. June 2019 14:02 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824921] Re: package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1824921 Title: package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2 Status in linux-firmware package in Ubuntu: Confirmed Bug description: System is a new build. Right off the lastest ISO. Updates were applied. There were issues applying updates. This system does have a mobile i7 and a Geforce 960m 4GB edition. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-firmware 1.175.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Thu Apr 11 20:06:27 2019 Dependencies: Df: Dmesg: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2019-04-11 (4 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: linux-firmware Title: package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1824921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832496] Re: linux-raspi2: 4.18.0-1017.19 -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + linux-raspi2: 4.18.0-1017.19 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1832496 Title: linux-raspi2: 4.18.0-1017.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832508 phase: Holding before Packaging phase-changed: Wednesday, 12. June 2019 11:32 UTC reason: prepare-package: Stalled -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832488] Re: linux-snapdragon: 5.0.0-1015.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 10:31 UTC + phase: Packaging + phase-changed: Friday, 14. June 2019 13:32 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1832488 Title: linux-snapdragon: 5.0.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Packaging phase-changed: Friday, 14. June 2019 13:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832488] Re: linux-snapdragon: 5.0.0-1015.15 -proposed tracker
** Summary changed: - linux-snapdragon: -proposed tracker + linux-snapdragon: 5.0.0-1015.15 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1832488 Title: linux-snapdragon: 5.0.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Packaging phase-changed: Friday, 14. June 2019 13:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832483] Re: linux-raspi2: 5.0.0-1011.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 10:31 UTC + phase: Packaging + phase-changed: Friday, 14. June 2019 13:01 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1832483 Title: linux-raspi2: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Packaging phase-changed: Friday, 14. June 2019 13:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832483] Re: linux-raspi2: 5.0.0-1011.11 -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + linux-raspi2: 5.0.0-1011.11 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1832483 Title: linux-raspi2: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Holding before Packaging phase-changed: Wednesday, 12. June 2019 10:31 UTC reason: prepare-package: Stalled -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: [MIR] Please add support for SIPL
** Summary changed:
- Please add support for SIPL
+ [MIR] Please add support for SIPL
--
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/1829749
Title:
[MIR] Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Committed
Status in s390-tools-signed package in Ubuntu:
Fix Released
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
I can also confirm the reported issue. I've tried with Juju and plain MAAS to create a VM with just 2048MB and it fails in both cases. Creating, registering and commissioning the machine works, but it cannot be deployed. System information: 18.04.2 LTS up-to-date MAAS version: 2.5.3 (7533-g65952b418-0ubuntu1~18.04.1) Kernel version: 5.1.3 (Ukuu) I don't see what information we have to provide (last comment from @paelzer)? I've added a diff of the VM configuration ($ virsh dumpxml vm), but I don't see any unexpected difference. The VM with 4096MB memory specification boots and can be deployed while the 2048MB VM cannot. ** Patch added: "Diff of virsh vm configuration" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5270761/+files/vm.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Confirmed Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. If you are affected, please attach to the bug - the kernel used to boot the guest - the initrd used to boot the guest - libvirt guest XML used to define the guest - PXE config provided to the guest - the cloud image used to start the guest (That will likely not fit as bug attachment, consider storing it somewhere and contact us) TODO: The Maas Team will outline how to get all these artifacts. TODO: add reference to the comment outlining this (once added) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: Please add support for SIPL
This bug was fixed in the package s390-tools-signed - 2.9.0-0ubuntu2
---
s390-tools-signed (2.9.0-0ubuntu2) eoan; urgency=medium
* Initial Release LP: #1829749
-- Dimitri John Ledkov Tue, 28 May 2019 18:28:34
+0100
** Changed in: s390-tools-signed (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1829749
Title:
Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Committed
Status in s390-tools-signed package in Ubuntu:
Fix Released
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: Please add support for sipl
Reviewed and iterated on the s390-tools-signed source package; now
accepted.
** Also affects: s390-tools-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: s390-tools-signed (Ubuntu)
Status: New => Fix Committed
** Changed in: s390-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: s390-tools-signed (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: s390-tools (Ubuntu)
Importance: Undecided => High
** Changed in: s390-tools-signed (Ubuntu)
Importance: Undecided => High
** Changed in: linux-signed (Ubuntu)
Importance: Undecided => High
** Summary changed:
- Please add support for sipl
+ Please add support for SIPL
--
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/1829749
Title:
Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Committed
Status in s390-tools-signed package in Ubuntu:
Fix Committed
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: Please add support for sipl
Reviewed and accepted the s390-tools custom upload. Watched while it
was processed which happened without incident:
2019-06-14 09:43:09 DEBUG Publishing custom s390-tools,
s390-tools_2.9.0-0ubuntu2_s390x.tar.gz,
s390-tools_2.9.0-0ubuntu2_s390x_translations.tar.gz to ubuntu/eoan
Fri, 14 Jun 2019 09:43:09 +: (re-)signing
/srv/launchpad.net/ubuntu-archive/ubuntu/dists/eoan-proposed/main/signed/s390-tools-s390x/2.9.0-0ubuntu2/SHA256SUMS
as /srv/launchpad.net/ubuntu-archive/ubuntu/dists
/eoan-proposed/main/signed/s390-tools-s390x/2.9.0-0ubuntu2/SHA256SUMS.gpg (-u
0x790BC7277767219C42C86F933B4FE6ACC0B21F32 -u
0xF6ECB3762474EDA9D21B7022871920D1991BC93C --digest-algo SHA512)
2019-06-14 09:43:10 DEBUG Publishing custom s390-tools,
s390-tools_2.9.0-0ubuntu2_s390x.tar.gz,
s390-tools_2.9.0-0ubuntu2_s390x_translations.tar.gz to ubuntu/eoan
2019-06-14 09:43:09 DEBUG Publishing custom s390-tools,
s390-tools_2.9.0-0ubuntu2_s390x.tar.gz,
s390-tools_2.9.0-0ubuntu2_s390x_translations.tar.gz to ubuntu/eoan
Fri, 14 Jun 2019 09:43:09 +: (re-)signing
/srv/launchpad.net/ubuntu-archive/ubuntu/dists/eoan-proposed/main/signed/s390-tools-s390x/2.9.0-0ubuntu2/SHA256SUMS
as /srv/launchpad.net/ubuntu-archive/ubuntu/dists
/eoan-proposed/main/signed/s390-tools-s390x/2.9.0-0ubuntu2/SHA256SUMS.gpg (-u
0x790BC7277767219C42C86F933B4FE6ACC0B21F32 -u
0xF6ECB3762474EDA9D21B7022871920D1991BC93C --digest-algo SHA512)
2019-06-14 09:43:10 DEBUG Publishing custom s390-tools,
s390-tools_2.9.0-0ubuntu2_s390x.tar.gz,
s390-tools_2.9.0-0ubuntu2_s390x_translations.tar.gz to ubuntu/eoan
Downloaded the signed artifacts from ports.ubuntu.com, these correctly
contain the signature component and the public key. I am also able to
validate the resulting signature.
--
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/1829749
Title:
Please add support for sipl
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Committed
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Have you tested kernel in #38? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830951] Re: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8
This can be a good start: https://www.kernel.org/doc/html/latest/process/submitting-patches.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830951 Title: kernel panic: stack corrupted in efivar_ssdt_iter+0xd3/0xe8 Status in linux package in Ubuntu: Confirmed Bug description: We have a few 2010 mac pro running 1604 LTS that are just upgraded to Ubuntu 1804 LTS. While they all worked fine with the 1604 LTS and 4.4 kernel, they can no longer boot with the 4.15.0-50 kernel installed with 1804. We tried various kernel flags without luck, and installed latest 4.18.0-20 from HWE and got the same result. Unfortunately, no logs are created in /var/logs when the issue happens, and we could only boot with the old 4.4 kernel. We had to enable earlyprintk=efi to get a backtrace in a photo. The issue happens consistently, i.e. the backtrace looks always the same just happens on different cores. Attached the boot-info output and the picture taken at the end of the kernel loading. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: steventang 2047 F pulseaudio /dev/snd/controlC0: steventang 2047 F pulseaudio /dev/snd/controlC1: steventang 2047 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=a7ceb7f0-6040-4236-ad7d-35780a1dc870 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacPro5,1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=8d18bfd8-303b-4397-9216-a0e48cb6ef54 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-148-generic N/A linux-backports-modules-4.4.0-148-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.4.0-148-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MP51.88Z.0084.B00.1708080528 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.name: MacPro5,1 dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832828] [NEW] ipv6: fix EFAULT on sendto with icmpv6 and hdrincl
Public bug reported:
== SRU Justification ==
The following code returns EFAULT (Bad address):
s = socket(AF_INET6, SOCK_RAW, IPPROTO_ICMPV6);
setsockopt(s, SOL_IPV6, IPV6_HDRINCL, 1);
sendto(ipv6_icmp6_packet, addr); /* returns -1, errno = EFAULT */
The IPv4 equivalent code works.
The failure happens because 2 bytes are eaten from the msghdr by
rawv6_probe_proto_opt() starting from commit 19e3c66b52ca ("ipv6
equivalent of "ipv4: Avoid reading user iov twice after
raw_probe_proto_opt""), but at that time it was not a problem because
IPV6_HDRINCL was not yet introduced.
Only eat these 2 bytes if hdrincl == 0.
== Fix ==
Upstream commits:
59e3e4b52663 ("ipv6: use READ_ONCE() for inet->hdrincl as in ipv4")
b9aa52c4cb45 ("ipv6: fix EFAULT on sendto with icmpv6 and hdrincl")
== Regression Potential ==
Low. Only impacts IPv6 raw sockets with IPV6_HDRINCL.
== Test Case ==
Copy/paste this code in a python3 interpreter:
IPPROTO_ICMPV6 = socket.getprotobyname('ipv6-icmp')
SOL_IPV6 = 41
IPV6_HDRINCL = 36
import socket
send_s = socket.socket(socket.AF_INET6, socket.SOCK_RAW, IPPROTO_ICMPV6)
send_s.setsockopt(SOL_IPV6, IPV6_HDRINCL, 1)
# this is an IPv6 + ICMPv6 echo packet
req =
b'`\x00\x00\x00\x00":@?\xfe\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01?\xfe\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x80\x00\xe0\xda9\xa0V\x8dabcdefghijklmnopqrstuvwxyz'
send_s.sendto(req, ('3ffe::2', 0, 0, 0))
On error, it raises:
OSError: [Errno 14] Bad address
After the fix, no exception is raised.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832828
Title:
ipv6: fix EFAULT on sendto with icmpv6 and hdrincl
Status in linux package in Ubuntu:
Incomplete
Bug description:
== SRU Justification ==
The following code returns EFAULT (Bad address):
s = socket(AF_INET6, SOCK_RAW, IPPROTO_ICMPV6);
setsockopt(s, SOL_IPV6, IPV6_HDRINCL, 1);
sendto(ipv6_icmp6_packet, addr); /* returns -1, errno = EFAULT */
The IPv4 equivalent code works.
The failure happens because 2 bytes are eaten from the msghdr by
rawv6_probe_proto_opt() starting from commit 19e3c66b52ca ("ipv6
equivalent of "ipv4: Avoid reading user iov twice after
raw_probe_proto_opt""), but at that time it was not a problem because
IPV6_HDRINCL was not yet introduced.
Only eat these 2 bytes if hdrincl == 0.
== Fix ==
Upstream commits:
59e3e4b52663 ("ipv6: use READ_ONCE() for inet->hdrincl as in ipv4")
b9aa52c4cb45 ("ipv6: fix EFAULT on sendto with icmpv6 and hdrincl")
== Regression Potential ==
Low. Only impacts IPv6 raw sockets with IPV6_HDRINCL.
== Test Case ==
Copy/paste this code in a python3 interpreter:
IPPROTO_ICMPV6 = socket.getprotobyname('ipv6-icmp')
SOL_IPV6 = 41
IPV6_HDRINCL = 36
import socket
send_s = socket.socket(socket.AF_INET6, socket.SOCK_RAW, IPPROTO_ICMPV6)
send_s.setsockopt(SOL_IPV6, IPV6_HDRINCL, 1)
# this is an IPv6 + ICMPv6 echo packet
req =
b'`\x00\x00\x00\x00":@?\xfe\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01?\xfe\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x80\x00\xe0\xda9\xa0V\x8dabcdefghijklmnopqrstuvwxyz'
send_s.sendto(req, ('3ffe::2', 0, 0, 0))
On error, it raises:
OSError: [Errno 14] Bad address
After the fix, no exception is raised.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832828/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830584] Re: mkswap01_sh from commands test suite in LTP failed
** Tags added: ubunut-ltp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830584 Title: mkswap01_sh from commands test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Test failed with file check timeout: mkswap01 8 TBROK: "check_for_file /dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out <<>> tag=mkswap01_sh stime=1558936352 cmdline="mkswap01.sh" contacts="" analysis=exit <<>> incrementing stop mkswap01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop3' mkswap01 1 TPASS: 'mkswap /dev/loop3 ' passed. mkswap01 2 TPASS: 'mkswap /dev/loop3 262140' passed. mkswap01 3 TINFO: Can not do swapon on /dev/loop3. mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size. mkswap01 3 TINFO: Swapon failed expectedly. mkswap01 3 TPASS: 'mkswap -f /dev/loop3 262148' passed. mkswap01 4 TPASS: 'mkswap -c /dev/loop3 ' passed. mkswap01 5 TINFO: Can not do swapon on /dev/loop3. mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's page size. mkswap01 5 TINFO: Swapon failed expectedly. mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop3 ' passed. mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop3 ' passed. mkswap01 7 TPASS: 'mkswap -v1 /dev/loop3 ' passed. mkswap01 8 TBROK: "check_for_file /dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out mkswap01 8 TINFO: AppArmor enabled, this may affect test results mkswap01 8 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) mkswap01 8 TINFO: loaded AppArmor profiles: none Summary: passed 7 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon May 27 05:53:16 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832828] 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 1832828
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832828
Title:
ipv6: fix EFAULT on sendto with icmpv6 and hdrincl
Status in linux package in Ubuntu:
Incomplete
Bug description:
== SRU Justification ==
The following code returns EFAULT (Bad address):
s = socket(AF_INET6, SOCK_RAW, IPPROTO_ICMPV6);
setsockopt(s, SOL_IPV6, IPV6_HDRINCL, 1);
sendto(ipv6_icmp6_packet, addr); /* returns -1, errno = EFAULT */
The IPv4 equivalent code works.
The failure happens because 2 bytes are eaten from the msghdr by
rawv6_probe_proto_opt() starting from commit 19e3c66b52ca ("ipv6
equivalent of "ipv4: Avoid reading user iov twice after
raw_probe_proto_opt""), but at that time it was not a problem because
IPV6_HDRINCL was not yet introduced.
Only eat these 2 bytes if hdrincl == 0.
== Fix ==
Upstream commits:
59e3e4b52663 ("ipv6: use READ_ONCE() for inet->hdrincl as in ipv4")
b9aa52c4cb45 ("ipv6: fix EFAULT on sendto with icmpv6 and hdrincl")
== Regression Potential ==
Low. Only impacts IPv6 raw sockets with IPV6_HDRINCL.
== Test Case ==
Copy/paste this code in a python3 interpreter:
IPPROTO_ICMPV6 = socket.getprotobyname('ipv6-icmp')
SOL_IPV6 = 41
IPV6_HDRINCL = 36
import socket
send_s = socket.socket(socket.AF_INET6, socket.SOCK_RAW, IPPROTO_ICMPV6)
send_s.setsockopt(SOL_IPV6, IPV6_HDRINCL, 1)
# this is an IPv6 + ICMPv6 echo packet
req =
b'`\x00\x00\x00\x00":@?\xfe\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01?\xfe\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x80\x00\xe0\xda9\xa0V\x8dabcdefghijklmnopqrstuvwxyz'
send_s.sendto(req, ('3ffe::2', 0, 0, 0))
On error, it raises:
OSError: [Errno 14] Bad address
After the fix, no exception is raised.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832828/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-oem-osp1 (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-oem-osp1 (Ubuntu Disco) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware
[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000
I'm having this issue as well, with the 5.0.0-16-generic kernel on amd64 and an Intel I219-V NIC using the e1000e driver. I have a test case that can reproduce it somewhat reliably (involving a lot of concurrent back- and-forth chatter on my LAN). I was able to reproduce it even after this command: ethtool -K enp0s31f6 gso off gro off tso off rx off tx off although anecdotally, disabling those features makes reproduction harder. After the original oops with backtrace (similar to the one posted above), the problem presents simply as: Jun 14 03:54:43 good-fortune systemd-networkd[7815]: enp0s31f6: Lost carrier Jun 14 03:54:43 good-fortune systemd-networkd[7815]: enp0s31f6: DHCP lease lost with no further backtraces. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Confirmed Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8
[Kernel-packages] [Bug 1830584] Re: mkswap01_sh from commands test suite in LTP failed
Tested with Apparmor removed, this issue will gone. mkswap01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0' mkswap01 1 TPASS: 'mkswap /dev/loop0 ' passed. mkswap01 2 TPASS: 'mkswap /dev/loop0 262140' passed. mkswap01 3 TINFO: Can not do swapon on /dev/loop0. mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size. mkswap01 3 TINFO: Swapon failed expectedly. mkswap01 3 TPASS: 'mkswap -f /dev/loop0 262148' passed. mkswap01 4 TPASS: 'mkswap -c /dev/loop0 ' passed. mkswap01 5 TINFO: Can not do swapon on /dev/loop0. mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's page size. mkswap01 5 TINFO: Swapon failed expectedly. mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop0 ' passed. mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop0 ' passed. mkswap01 7 TPASS: 'mkswap -v1 /dev/loop0 ' passed. mkswap01 8 TPASS: 'mkswap -U 8ae72224-45b9-484c-999a-72a9e9a2a803 /dev/loop0 ' passed. mkswap01 9 TPASS: 'mkswap -V /dev/loop0 ' passed. mkswap01 10 TPASS: 'mkswap -h /dev/loop0 ' passed. As we have apparmor enabled by default, this can be ignored. However we will need to figure out how to do this from the test suite. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830584 Title: mkswap01_sh from commands test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Test failed with file check timeout: mkswap01 8 TBROK: "check_for_file /dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out <<>> tag=mkswap01_sh stime=1558936352 cmdline="mkswap01.sh" contacts="" analysis=exit <<>> incrementing stop mkswap01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop3' mkswap01 1 TPASS: 'mkswap /dev/loop3 ' passed. mkswap01 2 TPASS: 'mkswap /dev/loop3 262140' passed. mkswap01 3 TINFO: Can not do swapon on /dev/loop3. mkswap01 3 TINFO: Device size specified by 'mkswap' greater than real size. mkswap01 3 TINFO: Swapon failed expectedly. mkswap01 3 TPASS: 'mkswap -f /dev/loop3 262148' passed. mkswap01 4 TPASS: 'mkswap -c /dev/loop3 ' passed. mkswap01 5 TINFO: Can not do swapon on /dev/loop3. mkswap01 5 TINFO: Page size specified by 'mkswap -p' is not equal to system's page size. mkswap01 5 TINFO: Swapon failed expectedly. mkswap01 5 TPASS: 'mkswap -p 2048 /dev/loop3 ' passed. mkswap01 6 TPASS: 'mkswap -L ltp_testswap /dev/loop3 ' passed. mkswap01 7 TPASS: 'mkswap -v1 /dev/loop3 ' passed. mkswap01 8 TBROK: "check_for_file /dev/disk/by-uuid/c8c72a79-8639-406d-87ab-82ffec53b68a" timed out mkswap01 8 TINFO: AppArmor enabled, this may affect test results mkswap01 8 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) mkswap01 8 TINFO: loaded AppArmor profiles: none Summary: passed 7 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon May 27 05:53:16 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1832661] Re: Xenial update: 4.4.181 upstream stable release
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Xenial) 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/1832661 Title: Xenial update: 4.4.181 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed 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: 4.4.181 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu
Please install and boot this kernel: https://people.canonical.com/~khfeng/lp1827961/ And attach dmesg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top-tech /Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MES1WH00 dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1 dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
TJ,
Will you send the patch to kernel-team mailing list?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831751
Title:
rtlwifi: aggresive memory leak
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
Author: Larry Finger
Date: Sat Nov 17 20:55:03 2018 -0600
rtlwifi: Fix leak of skb when processing C2H_BT_INFO
With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
+1 also affected by this. Kubuntu 18.04 kernel 5.0.0-05-generic on Asus ZenBook UX433FN -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
