[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
Not just the changes to support for the new regulatory database format, but also to support the new firmware, as FW API has bumped and may need to pull in more patches. For example, 3165/7265D/8260 NIC in v4.4 supports FW API from 13 to 19, but the new FW for 3165/7265D has bumped to API 29, and 8260 has bumped to 36. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: New Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: New Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel
Can be found on 4.15 kvm as well. ** Summary changed: - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel + ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763323 Title: ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in linux-kvm source package in Xenial: New Bug description: The "enable disable fan test" will fail with Xenial KVM kernel Error message: RTNETLINK answers: Operation not supported /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16 /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation RTNETLINK answers: Cannot assign requested address iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory Try `iptables -h' or 'iptables --help' for more information. iptables: Bad rule (does a matching rule exist in that chain?). iptables: Bad rule (does a matching rule exist in that chain?). iptables: No chain/target/match by that name. rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory /usr/sbin/fanatic: unable to bring fan up, unable to configure ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26 ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117 Uname: Linux 4.4.0-1021-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 12 10:22:57 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Is this solved in latest mainline kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769517] Re: Radeon HD 3450 acceleration not working
Please file an upstream bug at https://bugs.freedesktop.org/ Product: DRI Component: DRM/radeon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769517 Title: Radeon HD 3450 acceleration not working Status in linux package in Ubuntu: Confirmed Bug description: The Radeon HD 3450 acceleration support does not work. In the dmesg is the information: [ 13.892364] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 13.892476] radeon :02:00.0: disabling GPU acceleration ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1645 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 6 22:28:53 2018 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 154b:005b PNY Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1001 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1001:bd06/21/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769993] Re: linux: 4.13.0-42.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-artful ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1769996 (linux-oem), bug 1769997 (linux-azure), bug 1766595 (linux-azure-edge), bug 1770001 (linux-hwe), bug 1770002 (linux-gcp) derivatives: bug 1769995 (linux-raspi2) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 09. May 2018 09:00 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769993 Title: linux: 4.13.0-42.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1769996 (linux-oem), bug 1769997 (linux-azure), bug 1766595 (linux-azure-edge), bug 1770001 (linux-hwe), bug 1770002 (linux-gcp) derivatives: bug 1769995 (linux-raspi2) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 09. May 2018 09:00 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769997] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1769997 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770002] Re: linux-gcp: 4.13.0-1016.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1770002 Title: linux-gcp: 4.13.0-1016.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769996] Re: linux-oem: 4.13.0-1027.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1769996 Title: linux-oem: 4.13.0-1027.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770294] Re: linux-azure: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1770294 Title: linux-azure: 4.15.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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765279] Re: Unable to build libghugetlbfs test on 4.15 Bionic/Xenial
This issue can be found on 4.15 KVM kernel as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765279 Title: Unable to build libghugetlbfs test on 4.15 Bionic Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Bug description: When trying to build the libhugetlbfs test Bionic, it will fail with: CC32 obj32/linkhuge_nofd.o LD32 (hugelink test) obj32/linkhuge_nofd CC32 obj32/linkshare.o LD32 (hugelink test) obj32/linkshare LD32 (xB test) obj32/xB.linkhuge /usr/bin/x86_64-linux-gnu-ld: unrecognized option '--hugetlbfs-link=B' /usr/bin/x86_64-linux-gnu-ld: use the --help option for usage information collect2: error: ld returned 1 exit status Makefile:227: recipe for target 'obj32/xB.linkhuge' failed make[1]: *** [obj32/xB.linkhuge] Error 1 Makefile:242: recipe for target 'tests/all' failed make: *** [tests/all] Error 2 Steps: 1. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 2. cd libhugetlbfs 3. make ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1003-kvm 4.15.0-1003.3 ProcVersionSignature: User Name 4.15.0-1003.3-kvm 4.15.10 Uname: Linux 4.15.0-1003-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 04:44:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765279/+subscriptions -- Mailing list: https://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 1768121] Re: Mainline Kernel since 4.16.4 has postinstall script error
Thanks for the heads up on the libssl issue. Much appreciated. It's just sad that this is where we are with the mainline kernel. Take care. HH 09.05.2018, 06:50, "Pasi Tarhonen" <1768...@bugs.launchpad.net>: > This is fixed partly in the the bug > https://bugs.launchpad.net/bugs/1766728 by updating Xenial package > linux-base to include linux-update-symlinks binary. No fix for Trusty > available so far, but the Xenial fix seems to working also with Trusty > by updating linux-base to version 4.5. > > Other error with libssl1.1 can be workaround at least by installing PPA > ppa:ondrej/nginx-mainline. That package contains among the nginx > binaries also newer version of OpenSSL package (that seems to be) > required by linux-4.16.4 onwards. > > I used both workarounds with my Trusty box and got linux-4.16.7 > installed OK, so far so good... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768121 > > Title: > Mainline Kernel since 4.16.4 has postinstall script error > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hello, > > I don't know who does the packaging for the Mainline > Kernel(http://kernel.ubuntu.com/~kernel-ppa/mainline/), but it has > been erroring out in packaging and also for the packages in x64/32 > that have made it, there are post install script errors within the > packaging which disallow installation of the kernel. Tested on Ubuntu > 16.04. > > Selecting previously unselected package linux-headers-4.16.6-041606. > (Reading database ... 392264 files and directories currently installed.) > Preparing to unpack > linux-headers-4.16.6-041606_4.16.6-041606.201804300418_all.deb ... > Unpacking linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... > Selecting previously unselected package linux-headers-4.16.6-041606-generic. > Preparing to unpack > linux-headers-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... > Unpacking linux-headers-4.16.6-041606-generic (4.16.6-041606.201804300418) > ... > Selecting previously unselected package > linux-image-unsigned-4.16.6-041606-generic. > Preparing to unpack > linux-image-unsigned-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb > ... > Unpacking linux-image-unsigned-4.16.6-041606-generic > (4.16.6-041606.201804300418) ... > Selecting previously unselected package linux-modules-4.16.6-041606-generic. > Preparing to unpack > linux-modules-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ... > Unpacking linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) > ... > Setting up linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ... > dpkg: dependency problems prevent configuration of > linux-headers-4.16.6-041606-generic: > linux-headers-4.16.6-041606-generic depends on libssl1.1 (>= 1.1.0); > however: > Package libssl1.1 is not installed. > > dpkg: error processing package linux-headers-4.16.6-041606-generic > (--install): > dependency problems - leaving unconfigured > Setting up linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) > ... > Setting up linux-image-unsigned-4.16.6-041606-generic > (4.16.6-041606.201804300418) ... > /var/lib/dpkg/info/linux-image-unsigned-4.16.6-041606-generic.postinst: 50: > /var/lib/dpkg/info/linux-image-unsigned-4.16.6-041606-generic.postinst: > linux-update-symlinks: not found > dpkg: error processing package linux-image-unsigned-4.16.6-041606-generic > (--install): > subprocess installed post-installation script returned error exit status > 127 > Errors were encountered while processing: > linux-headers-4.16.6-041606-generic > linux-image-unsigned-4.16.6-041606-generic > > What's new in 4.16.6 is the libssl1.1 dependency, as it just errored > out with a half installed kernel and that post-installation script > error you see above. Please let whoever packages these kernels know > that is't been dead stick post 4.16.3. Thanks. > > HH > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768121/+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/1768121 Title: Mainline Kernel since 4.16.4 has postinstall script error Status in linux package in Ubuntu: Confirmed Bug description: Hello, I don't know who does the packaging for the Mainline Kernel(http://kernel.ubuntu.com/~kernel-ppa/mainline/), but it has been erroring out in packaging and also for the packages in x64/32 that have made it, there are post install script errors within the packaging which disallow installation of the kernel. Tested on Ubuntu 16.04. Selecting previously unselected package linux-headers-4.16.6-041606. (Reading database ... 392264 files and directories currently installed.) Prep
[Kernel-packages] [Bug 1768115] Patch to add extra tlbsyncs and ptesyncs
--- Comment on attachment From p...@au1.ibm.com 2018-05-10 00:32 EDT--- Try this one instead of the "Patch to add extra tlbsyncs". Ben H pointed out that it is ptesync which is important, not tlbsync (which is actually a no-op, though architecturally required), so this version adds a ptesync to the guest exit path as well as the tlbsync. ** Attachment added: "Patch to add extra tlbsyncs and ptesyncs" https://bugs.launchpad.net/bugs/1768115/+attachment/5137005/+files/extra-ptesync.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768115 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160. Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: Problem Description: Migration Guest running with IO stress crashed@security_file_permission+0xf4/0x160 after couple of migrations. Steps to re-create: Source host - boslcp3 Destination host - boslcp4 1.boslcp3 & boslcp4 installed with latest kernel root@boslcp3:~# uname -a Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# root@boslcp4:~# uname -a Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# 2. Installed guest boslcp3g1 with kernel and started LTP run from boslcp3 host root@boslcp3g1:~# uname -a Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux 3. Started migrating boslcp3g1 guest from source to destination & viceversa. 4. After couple of migrations it crashed at boslcp4 & enters into xmon 8:mon> t [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> S msr= 80001033 sprg0 = pvr= 004e1202 sprg1 = c7a85800 dec= 591e3e03 sprg2 = c7a85800 sp = c004f8a234a0 sprg3 = 00010008 toc= c16eae00 dar = 023c srr0 = c00c355c srr1 = 80001033 dsisr = 4000 dscr = ppr = 0010 pir= 0011 amr= uamor = dpdes = tir = cir= fscr = 05000180 tar = pspb = mmcr0 = 8000 mmcr1 = mmcr2 = pmc1 = pmc2 = pmc3 = pmc4 = mmcra = siar = pmc5 = 026c sdar = sier = pmc6 = 0861 ebbhr = ebbrr = bescr = iamr = 4000 pidr = 0034 tidr = cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220] pc: c00e4854: xmon_core+0x1f24/0x3520 lr: c00e4850: xmon_core+0x1f20/0x3520 sp: c004f8a234a0 msr: 80041033 current = 0xc004f89faf00 paca= 0xc7a85800 softe: 0irq_happened: 0x01 pid = 24028, comm = top Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.17) cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> r R00 = c043b7fc R16 = R01 = c004f8a23c90 R17 = ff70 R02 = c16eae00 R18 = 0a51b4bebfc8 R03 = c00279557200 R19 = 7fffe99edbb0 R04 = c003242499c0 R20 = 0a51b4c04db0 R05 = 0002 R21 = 0a51b4c20e90 R06 = 0004 R22 = 00040f00 R07 = ff81 R23 = 0a51b4c06560 R08 = ff80 R24 = ff80 R09 = R25 = 0a51b4bec2b8 R10 = R26 = 71f177bb0b20 R11 = 000
[Kernel-packages] [Bug 1770013] Re: linux-aws: 4.4.0-1020.20 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1020.20 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1770013 Title: linux-aws: 4.4.0-1020.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1770011 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745727] Re: Wifi stops working on Del XPS 9360
[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/1745727 Title: Wifi stops working on Del XPS 9360 Status in linux package in Ubuntu: Expired Bug description: I am running a a Dell XPS 9360 laptop and the wifi started to sometime "hang" this week after an update (not sure which one). Running Ubuntu 17.10 (upgraded from Gnome Ubuntu recently) $lsb_release -rd Description:Ubuntu 17.10 Release:17.10 I observed that five~ error messages like these popup from time to time in dmesg: [ 6000.482060] pcieport :00:1c.4: AER: Corrected error received: id=00e4 [ 6000.482082] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e4(Transmitter ID) [ 6000.482095] pcieport :00:1c.4: device [8086:9d14] error status/mask=1000/2000 [ 6000.482105] pcieport :00:1c.4:[12] Replay Timer Timeout A similar report exists for errors like this: 1521173 but not sure if it is related to the wifi problem. Most commenters in that report runs Realtek Wifi adapters while I have ath. Removing and adding the ath_pci module or disabling and enabling wifi with network manager seems to fix the issue for a while: $ sudo modprobe -r ath10k_pci $ sudo modprobe ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niklas 3554 F pulseaudio CurrentDesktop: GNOME Date: Sat Jan 27 12:11:31 2018 HibernationDevice: RESUME=UUID=5eda62e7-dbb8-402c-b33b-311c418b4f78 InstallationDate: Installed on 2017-09-27 (121 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2018-01-20 (7 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.name: 06CC14 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769376] Re: NMI watchdog: Watchdog detected hard LOCKUP on cpu x
Kernel 4.15: May 9 00:11:01 bridge kernel: [ 18.964323] nouveau :01:00.0: bus: MMIO read of FAULT at 409800 [ TIMEOUT ] May 9 00:11:03 bridge kernel: [ 20.963754] [ cut here ] May 9 00:11:03 bridge kernel: [ 20.963755] nouveau :01:00.0: timeout May 9 00:11:03 bridge kernel: [ 20.963798] WARNING: CPU: 4 PID: 1600 at /build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1507 gf100_gr_init_ctxctl_ext+0x615/0x7a0 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963799] Modules linked in: thunderbolt(+) snd_hda_codec_hdmi arc4 cmac bnep nls_iso8859_1 hid_multitouch snd_hda_codec_rea ltek snd_hda_codec_generic intel_rapl dell_laptop dell_smbios_smm dcdbas x86_pkg_temp_thermal intel_powerclamp dell_smm_hwmon coretemp snd_hda_intel kvm_intel s nd_hda_codec snd_hda_core kvm snd_hwdep irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event pcbc ath10k_pci snd_ rawmidi aesni_intel ath10k_core aes_x86_64 crypto_simd glue_helper cryptd ath joydev intel_cstate input_leds intel_rapl_perf mac80211 serio_raw snd_seq dell_wmi dell_smbios_wmi dell_smbios rtsx_pci_ms uvcvideo btusb cfg80211 snd_seq_device memstick btrtl videobuf2_vmalloc btbcm snd_timer videobuf2_memops btintel videob uf2_v4l2 videobuf2_core snd bluetooth idma64 May 9 00:11:03 bridge kernel: [ 20.963820] videodev virt_dma processor_thermal_device mei_me wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt soundcore me dia intel_lpss_pci ecdh_generic mei intel_lpss intel_pch_thermal intel_soc_dts_iosf shpchp intel_hid mac_hid int3403_thermal int3400_thermal acpi_pad sparse_key map int340x_thermal_zone acpi_thermal_rel tpm_crb sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau i915 rtsx_pci_sdmmc mxm_wmi ttm i2 c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse nvme ahci drm rtsx_pci nvme_core libahci i2c_hid hid wmi video May 9 00:11:03 bridge kernel: [ 20.963839] CPU: 4 PID: 1600 Comm: Xorg Not tainted 4.15.0-20-generic #21-Ubuntu May 9 00:11:03 bridge kernel: [ 20.963839] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.9.4 04/23/2018 May 9 00:11:03 bridge kernel: [ 20.963858] RIP: 0010:gf100_gr_init_ctxctl_ext+0x615/0x7a0 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963858] RSP: 0018:b24285437900 EFLAGS: 00010286 May 9 00:11:03 bridge kernel: [ 20.963859] RAX: RBX: 90b799b7ae90 RCX: 0006 May 9 00:11:03 bridge kernel: [ 20.963860] RDX: 0007 RSI: 0082 RDI: 90b7be516490 May 9 00:11:03 bridge kernel: [ 20.963860] RBP: b24285437930 R08: 0001 R09: 0418 May 9 00:11:03 bridge kernel: [ 20.963861] R10: R11: R12: 7735e6a0 May 9 00:11:03 bridge kernel: [ 20.963861] R13: 90b78e1b R14: 90b78e946c00 R15: 00046a5382c0 May 9 00:11:03 bridge kernel: [ 20.963862] FS: 7fc95ad1e600() GS:90b7be50() knlGS: May 9 00:11:03 bridge kernel: [ 20.963863] CS: 0010 DS: ES: CR0: 80050033 May 9 00:11:03 bridge kernel: [ 20.963863] CR2: 55b1fb23e7d8 CR3: 00084f822002 CR4: 003606e0 May 9 00:11:03 bridge kernel: [ 20.963864] Call Trace: May 9 00:11:03 bridge kernel: [ 20.963882] gf100_gr_init_ctxctl+0x1f5/0x290 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963898] gp100_gr_init+0x70b/0x740 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963913] gf100_gr_init_+0x5b/0x60 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963928] nvkm_gr_init+0x1d/0x20 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963937] nvkm_engine_init+0x6b/0x200 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963946] nvkm_subdev_init+0xb9/0x200 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963954] nvkm_engine_ref+0x4f/0x70 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963962] nvkm_ioctl_new+0x27b/0x2c0 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963977] ? nvkm_fifo_chan_dtor+0xf0/0xf0 [nouveau] May 9 00:11:03 bridge kernel: [ 20.963992] ? gf100_gr_chsw_load+0x50/0x50 [nouveau] May 9 00:11:03 bridge kernel: [ 20.964000] nvkm_ioctl+0x11d/0x280 [nouveau] May 9 00:11:03 bridge kernel: [ 20.964040] nvkm_client_ioctl+0x12/0x20 [nouveau] May 9 00:11:03 bridge kernel: [ 20.964050] nvif_object_ioctl+0x47/0x50 [nouveau] May 9 00:11:03 bridge kernel: [ 20.964059] nvif_object_init+0xc8/0x120 [nouveau] May 9 00:11:03 bridge kernel: [ 20.964101] nouveau_abi16_ioctl_grobj_alloc+0x155/0x2f0 [nouveau] May 9 00:11:03 bridge kernel: [ 20.964116] ? nouveau_abi16_ioctl_channel_free+0x90/0x90 [nouveau] May 9 00:11:03 bridge kernel: [ 20.964123] drm_ioctl_kernel+0x5f/0xb0 [drm] May 9 00:11:03 bridge kernel: [ 20.964128] drm_ioctl+0x31b/0x3d0 [drm] May 9 00:11:03 bridge kernel: [ 20.964142] ? nouveau_abi16_ioc
[Kernel-packages] [Bug 1769376] Re: NMI watchdog: Watchdog detected hard LOCKUP on cpu x
Kernel 4.17: May 9 00:55:56 bridge kernel: [ 19.995968] nouveau :01:00.0: gr: init failed, -16 May 9 00:55:56 bridge /usr/lib/gdm3/gdm-x-session[1311]: (EE) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) May 9 00:55:56 bridge /usr/lib/gdm3/gdm-x-session[1311]: (EE) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel May 9 00:55:58 bridge kernel: [ 21.997016] [ cut here ] May 9 00:55:58 bridge kernel: [ 21.997017] nouveau :01:00.0: timeout May 9 00:55:58 bridge kernel: [ 21.997054] WARNING: CPU: 4 PID: 1313 at /home/kernel/COD/linux/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207 gf100_v mm_flush_+0x15c/0x1a0 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997054] Modules linked in: ccm thunderbolt cmac bnep arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch hid_generic snd_ hda_codec_realtek snd_hda_codec_generic intel_rapl dell_laptop x86_pkg_temp_thermal dell_smm_hwmon intel_powerclamp coretemp kvm_intel kvm irqbypass snd_hda_int el snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hda_core snd_hwdep ghash_clmulni_intel pcbc ath10k_pci snd_pcm ath10k_core aesni_intel ath aes_x86_64 uvcvide o crypto_simd cryptd glue_helper mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_wmi snd_seq_midi intel_cstate dell_smbios intel_rapl_perf dcdba s videobuf2_common snd_seq_midi_event joydev input_leds snd_rawmidi btusb serio_raw intel_wmi_thunderbolt wmi_bmof dell_wmi_descriptor rtsx_pci_ms cfg80211 btrt l videodev btbcm idma64 media virt_dma btintel May 9 00:55:58 bridge kernel: [ 21.997075] snd_seq bluetooth memstick snd_seq_device snd_timer snd ecdh_generic intel_lpss_pci mei_me processor_thermal_devi ce soundcore mei intel_lpss intel_pch_thermal intel_soc_dts_iosf shpchp acpi_pad int3403_thermal intel_hid int3400_thermal int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper p smouse rtsx_pci syscopyarea sysfillrect sysimgblt fb_sys_fops drm ahci i2c_hid libahci hid video wmi May 9 00:55:58 bridge kernel: [ 21.997093] CPU: 4 PID: 1313 Comm: Xorg Tainted: GW 4.17.0-041700rc4-generic #201805070430 May 9 00:55:58 bridge kernel: [ 21.997094] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.9.4 04/23/2018 May 9 00:55:58 bridge kernel: [ 21.997110] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997110] RSP: 0018:af7284c876c0 EFLAGS: 00010282 May 9 00:55:58 bridge kernel: [ 21.997111] RAX: RBX: 9035d9ad6090 RCX: 0006 May 9 00:55:58 bridge kernel: [ 21.997112] RDX: 0007 RSI: 0096 RDI: 9035fe5164b0 May 9 00:55:58 bridge kernel: [ 21.997112] RBP: af7284c876f8 R08: 047f R09: 0004 May 9 00:55:58 bridge kernel: [ 21.997113] R10: c04c1790 R11: 0001 R12: 9035cd827800 May 9 00:55:58 bridge kernel: [ 21.997113] R13: 9035ce502720 R14: 0004a7e9e180 R15: 9035a67b0400 May 9 00:55:58 bridge kernel: [ 21.997114] FS: 7f1537e7c600() GS:9035fe50() knlGS: May 9 00:55:58 bridge kernel: [ 21.997115] CS: 0010 DS: ES: CR0: 80050033 May 9 00:55:58 bridge kernel: [ 21.997115] CR2: 55f88b58a000 CR3: 00084e396002 CR4: 003606e0 May 9 00:55:58 bridge kernel: [ 21.997116] Call Trace: May 9 00:55:58 bridge kernel: [ 21.997131] gp100_vmm_flush+0x17/0x20 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997145] nvkm_vmm_iter.constprop.14+0x2e5/0x880 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997158] ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997171] ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997184] nvkm_vmm_map+0x21e/0x400 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997196] ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997208] nvkm_vram_map+0x57/0x80 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997221] nvkm_uvmm_mthd+0x792/0x8d0 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997229] nvkm_object_mthd+0x1a/0x30 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997237] nvkm_ioctl_mthd+0x5d/0xb0 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997246] nvkm_ioctl+0x11d/0x280 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997263] nvkm_client_ioctl+0x12/0x20 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997270] nvif_object_ioctl+0x47/0x50 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997278] nvif_object_mthd+0x129/0x150 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997294] ? gf100_grctx_generate_r406800+0xe0/0x1f0 [nouveau] May 9 00:55:58 bridge kernel: [ 21.997297] ? _cond_resched+0x19/0x40 May 9 00:55:58 bridge kernel: [ 21.997298]
[Kernel-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04
I installed cosmic daily build 0509, the alsa-lib is 1.1.6-1ubuntu1, it worked well. Waiting for the bionic 1.1.3-5ubuntu1 to be ready. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1768830 Title: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04 Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: In Progress Bug description: Steps: 1. Install the ubuntu 18.04 on the machine of Lenovo P520. 2. Login system. 3. Plug in an external headset to record and playback in front and rear panel. Expected result: Output and input audio should work in front and rear panel. Actual result: Front panel audio doesn't work at all. Just output audio working, input audio does't work in rear panel. SRU Document: [Impact] We have several Lenovo machines like Lenovo P520 which have 2 analogue audio codecs on them, the internal speaker and front headset are connected to the 1st codec, the Rear mic, Line in and Line out are connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa- lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and front headset) on the 1st codec can work. To make all audio devices work on this machine, upstream provided 3 patches for kernel audio driver and 5 patches for alsa-lib. The kernel patches are already in the linux-4.12, so this is not a problem anymore under 18.04 since we use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport them to v1.1.3-5, the 5 patches are list as below: 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card long name (it is in the alsa-lib v1.1.4) 4b9297e6 ucm: Load device-specific configuration file based on the card long name (it is in the alsa-lib v1.1.4) b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the alsa-lib v1.1.6) 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file (it is in the alsa-lib v1.1.6+) 81db276f conf/ucm: increase the input volume for LineIn (it is in the alsa-lib v1.1.6+) Some explanation for these 5 patches, to make the audio work, the alsa-lib needs to add an audio configuration file and verb conf file for lenovo machines with dual codecs, these two files are put in a folder named by card_long_name, and the name of configuration file itself is also named by card_long_name, this is implemented by the patches of NO. 3rd and 5th. But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with card_long_name, it only support searching with card_name, So we need to backport 3 patches to let alsa-lib v1.1.3-5 support to search with card_long_name, these 3 patches are No. 1st, 2nd and 4th. [Test Case] On the Lenovo machines with dual codecs (p520), I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can find the conf file and can parse the conf file successfully, and I tested the internal speaker, front headset, rear mic, line out and line in, all audio devices work well. On a HP and Dell machines without dual codecs, I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can't find conf file by card_long_name and card_name, the pulseaudio will drive the sound card as before, so all audio functions worked well as before. [Regression Potential] After adding these 5 patches, there 2 two changes introduced into the alsa-lib v1.1.3-5ubuntu1: 1) before: only have folder and conf files named by card_name; after: has one folder and conf file named by card_long_name, this folder and conf file will not affect others, 2) before: the ucm parser will search the conf file/folder by card_name only; after: the ucm parser will search the conf file/foler by card_long_name first, if it fails, it will fallback to use card_name to search again. So this change is compatible with old version. There is no regression since there is only one folder named by card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with dual codecs, it will find the conf file by card_long_name, if it runs on other machines, the search by card_long_name will definitely fail and fall back to search by card_name, then it will be same as before. So the objective of these 5 patches is to let lenovo machines with dual codecs find the conf file by card_long_name, let other machines fail to search by card_long_name, then fallback to original searching method - search by card_name. [Other Info] Since I could not find the alsa-lib repository in canonical, I just generated the debdiff with "apt-get source ...". To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1768830/+subscriptions
[Kernel-packages] [Bug 1769997] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1769993 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 10. May 2018 03:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1769993 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 10. May 2018 03:01 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1769997 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1769993 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770294] Re: linux-azure: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - kernel-stable-phase-changed:Thursday, 10. May 2018 02:04 UTC - kernel-stable-phase:Packaging - -- swm properties -- phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 10. May 2018 03:04 UTC ** Description changed: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 10. May 2018 03:04 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1770294 Title: linux-azure: 4.15.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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769927] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2018-05-09 12:56 EDT--- (In reply to comment #17) > (In reply to comment #16) > > HI Luciano, > > > > Bug is set to NEEDINFO state, may i know the pending item from my end. > > > > Regards, > > Indira > > Hi Indira, > > Yes, please confirm that the workaround Hari provided indeed allows kdump to > generate a vmcore successfully. We have a couple of other bugs this is > dependent on working to pursue gathering data for crashes reported. > > echo c > /proc/sysrq-trigger > > should tell us. Hi, Have tried the workaround 1. root@boslcp3g4:~#/etc/kernel/postinst.d/kdump-tools 4.4.0-122-generic root@boslcp3g4:~# systemctl restart kdump-tools.service [ 216.964332] kdump-tools[8867]: Stopping kdump-tools: * unloaded kdump kernel [ 217.271290] kdump-tools[8895]: Starting kdump-tools: Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.4.0-122-generic root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro ro splash quiet xmon=on irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=156800K [ 218.122135] kdump-tools[8895]: * loaded kdump kernel 2. root@boslcp3g4:~# 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.4.0-122-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.4.0-122-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.4.0-122-generic root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro ro splash quiet xmon=on irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 3. root@boslcp3g4:~# kdump-config status current state : ready to kdump root@boslcp3g4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-122-generic root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro ro splash quiet crashkernel=512M crashkernel=4096M 4. Triggered crash & it logged crash logs root@boslcp3g4:~# ls -lr /var/crash total 364 -rw-r- 1 root root 345515 May 7 06:19 _usr_bin_rsync.0.crash -rw-r- 1 root root 13690 May 9 12:45 linux-image-4.4.0-122-generic-201805091244.crash -rw-r--r-- 1 root root269 May 9 12:45 kexec_cmd drwxr-xr-x 2 root root 4096 May 9 12:44 201805091244 root@boslcp3g4:~# date Wed May 9 12:46:40 EDT 2018 Regards, Indira -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1769927 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config show' shows Not ready to kdump even after doing kdump setup. Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: Problem Description: === 'kdump-config show' shows Not ready to kdump even after doing kdump setup on ubuntu160404 guest. Steps to re-create: == 1. boslcp3 is up with BMC:1.20 & PNOR: 20180420 levels 2. Installed p8 compat guest with ubutnu160404 root@boslcp3g4:~# uname -a Linux boslcp3g4 4.4.0-122-generic #146-Ubuntu SMP Mon Apr 23 15:33:25 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g4:~# uname -r 4.4.0-122-generic 3. Installed linux-crashdump crash dump utility. 4. root@boslcp3g4:~# cat /etc/default/grub.d/kexec-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4096M" root@boslcp3g4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-116-generic root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro root@boslcp3g4:~# 5. rebooted guest and checked kdump status. root@boslcp3g4:~# /etc/init.d/kdump-tools status ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2018-05-06 04:18:37 EDT; 7min ago Process: 2317 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 2317 (code=exited, status=0/SUCCESS) Tasks: 0 Memory: 0B CPU: 0 CGroup: /system.slice/kdump-tools.service May 06 04:18:37 boslcp3g4 systemd[1]: Starting Kernel crash dump capture service... May 06 04:18:37 boslcp3g4 kdump-tools[2317]: Starting kdump-tools: * no crashkernel= parameter in the kernel cmdline May 06 04:18:37 boslcp3g4 systemd[1]: Started Kernel crash dump capture service. root@boslcp3g4:~# sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 4. kdump state root@boslcp3g4:~# kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/
[Kernel-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Thanks. Exact numbers help a lot. ** Summary changed: - [regression][bionic] Bluetooth keyboard battery reports 0% + [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770293] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
*** This bug is a duplicate of bug 1769997 *** https://bugs.launchpad.net/bugs/1769997 ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** This bug has been marked a duplicate of bug 1769997 linux-azure: 4.13.0-1017.20 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1770293 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-1017.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Thursday, 10. May 2018 01:34 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770294] Re: linux-azure: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1770294 Title: linux-azure: 4.15.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 prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Thursday, 10. May 2018 02:04 UTC kernel-stable-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769517] Re: Radeon HD 3450 acceleration not working
On: Linux mouse 4.17.0-041700rc4-generic #201805070430 SMP Mon May 7 04:31:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I still get [4.007419] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [4.007433] radeon :02:00.0: disabling GPU acceleration ** Attachment added: "Dmesg log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/+attachment/5136955/+files/dmesg.txt ** Tags added: kernel-bug-exists-upstream ** 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/1769517 Title: Radeon HD 3450 acceleration not working Status in linux package in Ubuntu: Confirmed Bug description: The Radeon HD 3450 acceleration support does not work. In the dmesg is the information: [ 13.892364] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 13.892476] radeon :02:00.0: disabling GPU acceleration ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1645 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 6 22:28:53 2018 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 154b:005b PNY Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1001 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1001:bd06/21/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769997] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1769997 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1769993 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769517] Re: Radeon HD 3450 acceleration not working
This bug also existed with Ubuntu 16.04 in kernel 4.4.0-96-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769517 Title: Radeon HD 3450 acceleration not working Status in linux package in Ubuntu: Confirmed Bug description: The Radeon HD 3450 acceleration support does not work. In the dmesg is the information: [ 13.892364] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 13.892476] radeon :02:00.0: disabling GPU acceleration ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1645 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 6 22:28:53 2018 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 154b:005b PNY Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1001 dmi.board.name: M2NPV-VM dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.xx dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1001:bd06/21/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770294] Re: linux-azure: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-stable-phase-changed:Thursday, 10. May 2018 02:04 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Thursday, 10. May 2018 02:04 UTC kernel-stable-phase:Packaging + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1770294 Title: linux-azure: 4.15.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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Thursday, 10. May 2018 02:04 UTC kernel-stable-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767406] Re: linux-azure: 4.15.0-1010.10 -proposed tracker
*** This bug is a duplicate of bug 1770294 *** https://bugs.launchpad.net/bugs/1770294 ** This bug has been marked a duplicate of bug 1770294 linux-azure: 4.15.0-1011.11 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1767406 Title: linux-azure: 4.15.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770294] [NEW] linux-azure: 4.15.0-1011.11 -proposed tracker
Public bug reported: This bug is for tracking the 4.15.0-1011.11 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importa
[Kernel-packages] [Bug 1769997] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.13.0-1017.20 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** 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) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1769997 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1769993 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770293] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug is for tracking the 4.13.0-1017.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-stable-phase:Packaging + kernel-stable-phase-changed:Thursday, 10. May 2018 01:34 UTC ** Description changed: This bug is for tracking the 4.13.0-1017.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Thursday, 10. May 2018 01:34 UTC + + -- swm properties -- + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1770293 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-1017.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Thursday, 10. May 2018 01:34 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770293] [NEW] linux-azure: 4.13.0-1017.20 -proposed tracker
Public bug reported: This bug is for tracking the 4.13.0-1017.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase:Packaging kernel-stable-phase-changed:Thursday, 10. May 2018 01:34 UTC -- swm properties -- phase: Packaging ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/sna
[Kernel-packages] [Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race
** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-azure (Ubuntu) Status: Confirmed => In Progress ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1765564 Title: fsnotify: Fix fsnotify_mark_connector race Status in Linux: New Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: New Status in linux-azure source package in Bionic: New Bug description: On Azure we have had sporadic cases of soft lockups in fsnotify that may very well be mitigated by the following fix. The LKML thread is "kernel panics with 4.14.X". This should be applied to 4.13 and 4.15 versions of the linux-azure kernel, and possibly the 4.15 generic kernel in bionic as well. - fsnotify() acquires a reference to a fsnotify_mark_connector through the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it appears that no precautions are taken in fsnotify_put_mark() to ensure that fsnotify() drops its reference to this fsnotify_mark_connector before assigning a value to its 'destroy_next' field. This can result in fsnotify_put_mark() assigning a value to a connector's 'destroy_next' field right before fsnotify() tries to traverse the linked list referenced by the connector's 'list' field. Since these two fields are members of the same union, this behavior results in a kernel panic. This issue is resolved by moving the connector's 'destroy_next' field into the object pointer union. This should work since the object pointer access is protected by both a spinlock and the value of the 'flags' field, and the 'flags' field is cleared while holding the spinlock in fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be possible for another thread to accidentally read from the object pointer after the 'destroy_next' field is updated. The offending behavior here is extremely unlikely; since fsnotify_put_mark() removes references to a connector (specifically, it ensures that the connector is unreachable from the inode it was formerly attached to) before updating its 'destroy_next' field, a sizeable chunk of code in fsnotify_put_mark() has to execute in the short window between when fsnotify() acquires the connector reference and saves the value of its 'list' field. On the HEAD kernel, I've only been able to reproduce this by inserting a udelay(1) in fsnotify(). However, I've been able to reproduce this issue without inserting a udelay(1) anywhere on older unmodified release kernels, so I believe it's worth fixing at HEAD. References: https://bugzilla.kernel.org/show_bug.cgi?id=199437 Fixes: 08991e83b7286635167bab40927665a90fb00d81 CC: sta...@vger.kernel.org Signed-off-by: Robert Kolchmeyer Signed-off-by: Jan Kara To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1765564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770291] Re: Monitor becomes unknown/undetected/low resolution
resolved. removed dkms drivers: # dkms remove nvidia-340/340.104 --all # dkms remove bbswitch/0.8 --all # dkms remove ndiswrapper/1.60 --all # dkms remove 8192cu/4.0.29 --all -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770291 Title: Monitor becomes unknown/undetected/low resolution Status in linux package in Ubuntu: Incomplete Bug description: reverting to 4.15.0-15 resolves issue. Same problem regardless of recommended or legacy nvidia drivers or open software. 4.15.0-15: $ inxi -G Graphics: Card: NVIDIA GT218 [GeForce 210] Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1280x1024@75.02hz GLX Renderer: NVA8 GLX Version: 3.0 Mesa 17.2.8 Monitor Dell 1907FPf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770291] 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 1770291 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/1770291 Title: Monitor becomes unknown/undetected/low resolution Status in linux package in Ubuntu: Incomplete Bug description: reverting to 4.15.0-15 resolves issue. Same problem regardless of recommended or legacy nvidia drivers or open software. 4.15.0-15: $ inxi -G Graphics: Card: NVIDIA GT218 [GeForce 210] Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1280x1024@75.02hz GLX Renderer: NVA8 GLX Version: 3.0 Mesa 17.2.8 Monitor Dell 1907FPf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770291] [NEW] Monitor becomes unknown/undetected/low resolution
Public bug reported: reverting to 4.15.0-15 resolves issue. Same problem regardless of recommended or legacy nvidia drivers or open software. 4.15.0-15: $ inxi -G Graphics: Card: NVIDIA GT218 [GeForce 210] Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1280x1024@75.02hz GLX Renderer: NVA8 GLX Version: 3.0 Mesa 17.2.8 Monitor Dell 1907FPf ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770291 Title: Monitor becomes unknown/undetected/low resolution Status in linux package in Ubuntu: New Bug description: reverting to 4.15.0-15 resolves issue. Same problem regardless of recommended or legacy nvidia drivers or open software. 4.15.0-15: $ inxi -G Graphics: Card: NVIDIA GT218 [GeForce 210] Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1280x1024@75.02hz GLX Renderer: NVA8 GLX Version: 3.0 Mesa 17.2.8 Monitor Dell 1907FPf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Just upgrading to 18.04 seems to fix the problem for me ! $ uname -a Linux tignasse 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in System76: Triaged Status in linux package in Ubuntu: Triaged Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770046] Re: Realtek ethernet network adapter kernel driver r8169 does not load
Test of mainline 4.17.0-041700rc4 kernel: ~/kernel $ ls -al total 64260 drwxr-xr-x2 lord lord 4096 May 9 16:09 . drwx--x---+ 103 lord lord20480 May 9 16:03 .. -rw-r--r--1 lord lord 1128092 May 9 16:09 libssl1.1_1.1.0g-2ubuntu4_amd64.deb -rw-r--r--1 lord lord 10217940 May 9 16:02 linux-headers-4.17.0-041700rc4_4.17.0-041700rc4.201805070430_all.deb -rw-r--r--1 lord lord 1065936 May 9 16:02 linux-headers-4.17.0-041700rc4-generic_4.17.0-041700rc4.201805070430_amd64.deb -rw-r--r--1 lord lord 8075016 May 9 16:03 linux-image-unsigned-4.17.0-041700rc4-generic_4.17.0-041700rc4.201805070430_amd64.deb -rw-r--r--1 lord lord 45233732 May 9 16:07 linux-modules-4.17.0-041700rc4-generic_4.17.0-041700rc4.201805070430_amd64.deb ~/kernel $ sudo dpkg -i *.deb Selecting previously unselected package libssl1.1:amd64. (Reading database ... 391867 files and directories currently installed.) Preparing to unpack libssl1.1_1.1.0g-2ubuntu4_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.0g-2ubuntu4) ... Preparing to unpack linux-headers-4.17.0-041700rc4_4.17.0-041700rc4.201805070430_all.deb ... Unpacking linux-headers-4.17.0-041700rc4 (4.17.0-041700rc4.201805070430) over (4.17.0-041700rc4.201805070430) ... Preparing to unpack linux-headers-4.17.0-041700rc4-generic_4.17.0-041700rc4.201805070430_amd64.deb ... Unpacking linux-headers-4.17.0-041700rc4-generic (4.17.0-041700rc4.201805070430) over (4.17.0-041700rc4.201805070430) ... Preparing to unpack linux-image-unsigned-4.17.0-041700rc4-generic_4.17.0-041700rc4.201805070430_amd64.deb ... Unpacking linux-image-unsigned-4.17.0-041700rc4-generic (4.17.0-041700rc4.201805070430) over (4.17.0-041700rc4.201805070430) ... Selecting previously unselected package linux-modules-4.17.0-041700rc4-generic. Preparing to unpack linux-modules-4.17.0-041700rc4-generic_4.17.0-041700rc4.201805070430_amd64.deb ... Unpacking linux-modules-4.17.0-041700rc4-generic (4.17.0-041700rc4.201805070430) ... Setting up libssl1.1:amd64 (1.1.0g-2ubuntu4) ... Setting up linux-headers-4.17.0-041700rc4 (4.17.0-041700rc4.201805070430) ... Setting up linux-headers-4.17.0-041700rc4-generic (4.17.0-041700rc4.201805070430) ... Setting up linux-modules-4.17.0-041700rc4-generic (4.17.0-041700rc4.201805070430) ... Setting up linux-image-unsigned-4.17.0-041700rc4-generic (4.17.0-041700rc4.201805070430) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.17.0-041700rc4-generic I: /initrd.img.old is now a symlink to boot/initrd.img-4.17.0-041700rc4-generic Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for linux-image-unsigned-4.17.0-041700rc4-generic (4.17.0-041700rc4.201805070430) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.17.0-041700rc4-generic Warning: No support for locale: en_US.utf8 /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.17.0-041700rc4-generic Found initrd image: /boot/initrd.img-4.17.0-041700rc4-generic Found linux image: /boot/vmlinuz-4.13.0-41-generic Found initrd image: /boot/initrd.img-4.13.0-41-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done After disabling Intel microcode and nvidia proprietary drivers and booting into 4.17.0-041700rc4: $ lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks % 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11) Subsystem: ASRock Incorporation Motherboard (one of many) Kernel driver in use: r8169 Kernel modules: r8169 $ apt-cache policy 4.17.0-041700rc4 linux-image-unsigned-4.17.0-041700rc4-generic: Installed: 4.17.0-041700rc4.201805070430 Candidate: 4.17.0-041700rc4.201805070430 Version table: *** 4.17.0-041700rc4.201805070430 100 100 /var/lib/dpkg/status linux-headers-4.17.0-041700rc4: Installed: 4.17.0-041700rc4.201805070430 Candidate: 4.17.0-041700rc4.201805070430 Version table: *** 4.17.0-041700rc4.201805070430 100 100 /var/lib/dpkg/status linux-headers-4.17.0-041700rc4-generic: Installed: 4.17.0-041700rc4.201805070430 Candidate: 4.17.0-041700rc4.201805070430 Version table: *** 4.17.0-041700rc4.201805070430 100 100 /var/lib/dpkg/status linux-modules-4.17.0-041700rc4-generic: Installed: 4.17.0-041700rc4.201805070430 Candidate: 4.17.0-041700rc4.201805070430 Version table: *** 4.17.0-041700rc4.201805070430 100 100 /var/lib/dpkg/status linux-image-4.17.0-041700rc4-generic: Installed: (none) Candidate: (none) Version table: Ethernet driver module appears to be loaded successfully. Tagging as kernel-fixed-upstream. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launch
[Kernel-packages] [Bug 1745646] Re: [PATCH] PCI / PM: Check device_may_wakeup() in pci_enable_wake()
On Wed, May 9, 2018 at 12:18 AM, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Commit 0847684cfc5f0 (PCI / PM: Simplify device wakeup settings code) > went too far and dropped the device_may_wakeup() check from > pci_enable_wake() which causes wakeup to be enabled during system > suspend, hibernation or shutdown for some PCI devices that are not > allowed by user space to wake up the system from sleep (or power off). > > As a result of this excessive power is drawn by some of the affected > systems while in sleep states or off. > > Restore the device_may_wakeup() check in pci_enable_wake(), but make > sure that the PCI bus type's runtime suspend callback will not call > device_may_wakeup() which is about system wakeup from sleep and not > about device wakeup from runtime suspend. > > Fixes: 0847684cfc5f0 (PCI / PM: Simplify device wakeup settings code) > Reported-by: Joseph Salisbury > Signed-off-by: Rafael J. Wysocki Bjorn, any concerns here? > --- > drivers/pci/pci.c | 29 +++-- > 1 file changed, 23 insertions(+), 6 deletions(-) > > Index: linux-pm/drivers/pci/pci.c > === > --- linux-pm.orig/drivers/pci/pci.c > +++ linux-pm/drivers/pci/pci.c > @@ -1910,7 +1910,7 @@ void pci_pme_active(struct pci_dev *dev, > EXPORT_SYMBOL(pci_pme_active); > > /** > - * pci_enable_wake - enable PCI device as wakeup event source > + * __pci_enable_wake - enable PCI device as wakeup event source > * @dev: PCI device affected > * @state: PCI state from which device will issue wakeup events > * @enable: True to enable event generation; false to disable > @@ -1928,7 +1928,7 @@ EXPORT_SYMBOL(pci_pme_active); > * Error code depending on the platform is returned if both the platform and > * the native mechanism fail to enable the generation of wake-up events > */ > -int pci_enable_wake(struct pci_dev *dev, pci_power_t state, bool enable) > +static int __pci_enable_wake(struct pci_dev *dev, pci_power_t state, bool > enable) > { > int ret = 0; > > @@ -1969,6 +1969,23 @@ int pci_enable_wake(struct pci_dev *dev, > > return ret; > } > + > +/** > + * pci_enable_wake - change wakeup settings for a PCI device > + * @pci_dev: Target device > + * @state: PCI state from which device will issue wakeup events > + * @enable: Whether or not to enable event generation > + * > + * If @enable is set, check device_may_wakeup() for the device before calling > + * __pci_enable_wake() for it. > + */ > +int pci_enable_wake(struct pci_dev *pci_dev, pci_power_t state, bool enable) > +{ > + if (enable && !device_may_wakeup(&pci_dev->dev)) > + return -EINVAL; > + > + return __pci_enable_wake(pci_dev, state, enable); > +} > EXPORT_SYMBOL(pci_enable_wake); > > /** > @@ -1981,9 +1998,9 @@ EXPORT_SYMBOL(pci_enable_wake); > * should not be called twice in a row to enable wake-up due to PCI PM vs > ACPI > * ordering constraints. > * > - * This function only returns error code if the device is not capable of > - * generating PME# from both D3_hot and D3_cold, and the platform is unable > to > - * enable wake-up power for it. > + * This function only returns error code if the device is not allowed to wake > + * up the system from sleep or it is not capable of generating PME# from both > + * D3_hot and D3_cold and the platform is unable to enable wake-up power for > it. > */ > int pci_wake_from_d3(struct pci_dev *dev, bool enable) > { > @@ -2114,7 +2131,7 @@ int pci_finish_runtime_suspend(struct pc > > dev->runtime_d3cold = target_state == PCI_D3cold; > > - pci_enable_wake(dev, target_state, pci_dev_run_wake(dev)); > + __pci_enable_wake(dev, target_state, pci_dev_run_wake(dev)); > > error = pci_set_power_state(dev, target_state); > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.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/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Status in acpi source package in Bionic: Confirmed Status in linux source package in Bionic: In Progress Status in acpi source package in Cosmic: Confirmed Status in linux source package in Cosmic: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device
[Kernel-packages] [Bug 1770003] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-09 18:25 EDT--- (In reply to comment #25) > I installed this kernel image and it overwrote the stock 4.15.0-20-generic > kernel image, wiping out any chance to boot the original kernel if something > goes wrong. This isn't the way the package was supposed to work, is it? Looks like it actually failed to install as well, so I'm looking at what happened. --- Comment From dougm...@us.ibm.com 2018-05-09 18:29 EDT--- Here are the pertinent messages from dpkg: --- Selecting previously unselected package linux-image-unsigned-4.15.0-20-generic. dpkg: regarding linux-image-unsigned-4.15.0-20-generic_4.15.0-20.21~lp1770003+build.6_ppc64el.deb containing linux-image-unsigned-4.15.0-20-generic: linux-image-unsigned-4.15.0-20-generic conflicts with linux-image-4.15.0-20-generic linux-image-4.15.0-20-generic (version 4.15.0-20.21) is present and installed. dpkg: error processing archive linux-image-unsigned-4.15.0-20-generic_4.15.0-20.21~lp1770003+build.6_ppc64el.deb (--install): conflicting packages - not installing linux-image-unsigned-4.15.0-20-generic I would have expected this kernel to be installed along side the default 18.04 kernel. Is there something wrong with the packages or my setup? This was on a scratch install of 18.04 -proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770003 Title: qla2xxx: Fix page fault at kmem_cache_alloc_node() Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Dear Canonical, We found that the current Ubuntu kernel contains a problem related to qla2xxx driver which causes: [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.20) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace We were able to get rid of this problem cherry picking some of the upstream patches. Do you think they might fit in the SRU criteria? The commit ids are below and they were easily cherry picked. eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug after firmware timeout 6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin trigger from sending too many commands 7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout() 045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled. 1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session free in qlt_free_session_done d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session deletion by using work_lock Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: Fixup locking for session deletion') 94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_dele? 9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup for N2N To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions -- Mailing list: https://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 1764040] Re: Synaptics Touchpad not Detected
Hi, This is now solved. Grub had somehow been changed to disable ACPI. Enabling that solved the problem. Thanks for your help. Cheers, Dave On 27 April 2018 at 15:55, Kai-Heng Feng wrote: > You can also try other i8042 parameters: > > i8042.unmask_kbd_data > [HW] Enable printing of interrupt data from the > KBD port > (disabled by default, and as a pre-condition > requires that i8042.debug=1 be enabled) > i8042.direct[HW] Put keyboard port into non-translated mode > i8042.dumbkbd [HW] Pretend that controller can only read data > from > keyboard and cannot control its state > (Don't attempt to blink the leds) > i8042.noaux [HW] Don't check for auxiliary (== mouse) port > i8042.nokbd [HW] Don't check/create keyboard port > i8042.noloop[HW] Disable the AUX Loopback command while > probing > for the AUX port > i8042.nomux [HW] Don't check presence of an active > multiplexing > controller > i8042.nopnp [HW] Don't use ACPIPnP / PnPBIOS to discover > KBD/AUX > controllers > i8042.notimeout [HW] Ignore timeout condition signalled by > controller > i8042.reset [HW] Reset the controller during init, cleanup and > suspend-to-ram transitions, only during s2r > transitions, or never reset > Format: { 1 | Y | y | 0 | N | n } > 1, Y, y: always reset controller > 0, N, n: don't ever reset controller > Default: only on s2r transitions on x86; most > other > architectures force reset to be always executed > i8042.unlock[HW] Unlock (ignore) the keylock > i8042.kbdreset [HW] Reset device connected to KBD port > > Kai-Heng > > > On Apr 27, 2018, at 1:31 PM, Dave Harton <1764...@bugs.launchpad.net> > > wrote: > > > > Hi, > > > > No luck. Still no touchpad :( > > > > I was going to do a clean install of 18.04. Is this an idea? > > > > Cheers > > > > On 25 April 2018 at 20:17, Kai-Heng Feng > > wrote: > > > >> Please try if kernel parameter "i8042.noloop=1" works for you. > >> > >> -- > >> You received this bug notification because you are subscribed to the bug > >> report. > >> https://bugs.launchpad.net/bugs/1764040 > >> > >> Title: > >> Synaptics Touchpad not Detected > >> > >> Status in linux package in Ubuntu: > >> Incomplete > >> > >> Bug description: > >> Using Cinnamon on 18.04 Beta 2. (Description: Ubuntu Bionic Beaver > >> (development branch) Release: 18.04) > >> > >> Touchpad not detected. Was also not detected in 17.10 but I thought > >> that this was a Wayland problem, but obviously not... > >> > >> $ cat /proc/bus/input/devices > >> I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 > >> N: Name="AT Translated Set 2 keyboard" > >> P: Phys=isa0060/serio0/input0 > >> S: Sysfs=/devices/platform/i8042/serio0/input/input0 > >> U: Uniq= > >> H: Handlers=sysrq kbd event0 leds > >> B: PROP=0 > >> B: EV=120013 > >> B: KEY=40200 3803078f800d001 fedfffef fffe > >> B: MSC=10 > >> B: LED=7 > >> > >> I: Bus=0003 Vendor=046d Product=c077 Version=0111 > >> N: Name="Logitech USB Optical Mouse" > >> P: Phys=usb-:00:04.0-4/input0 > >> S: Sysfs=/devices/pci:00/:00:04.0/usb2/2-4/2-4:1.0/ > >> 0003:046D:C077.0001/input/input1 > >> U: Uniq= > >> H: Handlers=mouse0 event1 > >> B: PROP=0 > >> B: EV=17 > >> B: KEY=ff 0 0 0 0 > >> B: REL=103 > >> B: MSC=10 > >> > >> I: Bus=0003 Vendor=04f2 Product=b012 Version=0346 > >> N: Name="USB2.0 1.3M UVC WebCam : USB2.0" > >> P: Phys=usb-:00:04.1-7/button > >> S: Sysfs=/devices/pci:00/:00:04.1/usb1/1-7/1-7:1.0/ > input/input2 > >> U: Uniq= > >> H: Handlers=kbd event2 > >> B: PROP=0 > >> B: EV=3 > >> B: KEY=10 0 0 0 > >> > >> I: Bus= Vendor= Product= Version= > >> N: Name="HDA NVidia Mic" > >> P: Phys=ALSA > >> S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input3 > >> U: Uniq= > >> H: Handlers=event3 > >> B: PROP=0 > >> B: EV=21 > >> B: SW=10 > >> > >> I: Bus= Vendor= Product= Version= > >> N: Name="HDA NVidia Headphone" > >> P: Phys=ALSA > >> S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input4 > >> U: Uniq= > >> H: Handlers=event4 > >> B: PROP=0 > >> B: EV=21 > >> B: SW=4 > >> > >> ProblemType: Bug > >> DistroRelease: Ubuntu 18.04 > >> Package: linux-image-4.15.0-15-generic 4.15.0-15.16 > >> ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 > >> Uname: Linux 4.15.0-15-generic x86_64 > >> NonfreeKernelModules:
[Kernel-packages] [Bug 1770003] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-09 18:14 EDT--- I installed this kernel image and it overwrote the stock 4.15.0-20-generic kernel image, wiping out any chance to boot the original kernel if something goes wrong. This isn't the way the package was supposed to work, is it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770003 Title: qla2xxx: Fix page fault at kmem_cache_alloc_node() Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Dear Canonical, We found that the current Ubuntu kernel contains a problem related to qla2xxx driver which causes: [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.20) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace We were able to get rid of this problem cherry picking some of the upstream patches. Do you think they might fit in the SRU criteria? The commit ids are below and they were easily cherry picked. eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug after firmware timeout 6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin trigger from sending too many commands 7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout() 045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled. 1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session free in qlt_free_session_done d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session deletion by using work_lock Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: Fixup locking for session deletion') 94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_dele? 9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup for N2N To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.
--- Comment From jos...@br.ibm.com 2018-05-09 18:03 EDT--- addendum: According to my last investigation[1] the problem is in the blk_mq only. If we don't use blk_mq devices we can hotplug and hot-unplug CPUs without any problem. [1] https://bugzilla.linux.ibm.com/show_bug.cgi?id=167294 comments 47, 48, and 49. ** Bug watch added: bugzilla.linux.ibm.com/ #167294 https://bugzilla.linux.ibm.com/show_bug.cgi?id=167294 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3746.978534] Tainted: GW4.15.0-12
[Kernel-packages] [Bug 1770240] Re: Can't install kernel 4.15.0-19
Unable to run this command. ** 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/1770240 Title: Can't install kernel 4.15.0-19 Status in linux package in Ubuntu: Confirmed Bug description: Running ubuntu 18.04 with kernel 4.15.0-20, but would like to reinstall the -19 to test issues and compare: linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770046] Re: Realtek ethernet network adapter kernel driver r8169 does not load
Issue does not exist in kernel 4.15.0-15 and earlier, it is only present in kernel 4.15.0-20. Due to other issues not relevant to this bug report, the most current and completely working kernel I am using is 4.13.0-41. I will attempt to test a kernel from the 4.17 range and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770046 Title: Realtek ethernet network adapter kernel driver r8169 does not load Status in linux package in Ubuntu: Incomplete Bug description: Realtek kernel driver r8169 does not load on kernel 4.15.0-20. $ lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks % 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11) Subsystem: ASRock Incorporation Motherboard (one of many) $ lsb_release -rd Description: Linux Mint 18.3 Sylvia Release: 18.3 $ apt-cache policy 4.15.0-20 linux-headers-4.15.0-20: Installed: 4.15.0-20.21~16.04.1 Candidate: 4.15.0-20.21~16.04.1 Version table: *** 4.15.0-20.21~16.04.1 500 500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status linux-modules-4.15.0-20-generic: Installed: 4.15.0-20.21~16.04.1 Candidate: 4.15.0-20.21~16.04.1 Version table: *** 4.15.0-20.21~16.04.1 500 500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status linux-headers-4.15.0-20-generic: Installed: 4.15.0-20.21~16.04.1 Candidate: 4.15.0-20.21~16.04.1 Version table: *** 4.15.0-20.21~16.04.1 500 500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21~16.04.1 Candidate: 4.15.0-20.21~16.04.1 Version table: *** 4.15.0-20.21~16.04.1 500 500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
Also fails (4.4.0-124 kernel) when trying to boot from xubuntu-18.04-desktop-i386 ISO - same result (black screen displays and qemu-system-x86 runs at 100% cpu indefinitely). qemu-system-i386 -name xubuntu-18.04-desktop-i386 -pidfile /tmp/xubuntu-18.04-desktop-i386.pid -m 2047M -cpu host -smp 1 -enable- kvm -rtc clock=host,base=localtime -machine type=ubuntu,accel=kvm -k en- us -boot d -cdrom /media/Shared/E/ISO/xubuntu-18.04-desktop-i386.iso -hda /media/V-BOX/KVM/Win10/Win10-VM.qcow2 -hdb /media/Big_NTFS/G/Backup/KVM/Win10/Win10-VM_Backup_Disk.qcow2 -usb -device usb-ehci,id=ehci -device piix3-usb-uhci -device usb-tablet ergo - not related to guest being Windows 10. Works fine when host booted with 4.4.0-119 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu- system-x86: black screen displays and qemu-system-x86 runs at 100% cpu indefinitely. Boot the same system with kernel 4.4.0-119 and qemu- system-x86 works fine running a Windows 10 VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic i686 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 29 15:58:25 2018 InstallationDate: Installed on 2014-04-29 (1460 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 394 2 0.0 [kvm-irqfd-clean] MachineType: Dell Inc. Inspiron 518 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash nmi_watchdog=0 SourcePackage: qemu UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago) dmi.bios.date: 03/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.8 dmi.board.name: 0K068D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 518 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)
4.15.0-20-generic #21~lp1745646FinalPatch is good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Status in acpi source package in Bionic: Confirmed Status in linux source package in Bionic: In Progress Status in acpi source package in Cosmic: Confirmed Status in linux source package in Cosmic: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 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.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767400] Re: linux-gcp: 4.15.0-1007.7 -proposed tracker
** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1767400 Title: linux-gcp: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1695093] Re: arm64: "unsupported RELA relocation: 275" loading certain modules
** Changed in: linux (Ubuntu Zesty) Status: Fix Committed => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: gcc-6 (Ubuntu Zesty) Status: Triaged => Won't Fix ** Changed in: gcc-5 (Ubuntu Zesty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695093 Title: arm64: "unsupported RELA relocation: 275" loading certain modules Status in Linux: In Progress Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-5 source package in Xenial: Fix Released Status in gcc-6 source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in gcc-5 source package in Yakkety: Won't Fix Status in gcc-6 source package in Yakkety: Won't Fix Status in linux source package in Yakkety: Won't Fix Status in gcc-5 source package in Zesty: Won't Fix Status in gcc-6 source package in Zesty: Won't Fix Status in linux source package in Zesty: Won't Fix Bug description: [Impact] Certain kernel modules are unloadable (libceph & scsi_debug) due to the compiler generating unsupported relocations. This symptom is similar to LP: #1533009 but, in that case it impacted all modules, and the fix for that appears to remain in place. [Test Case] With the hwe-z kernel: ubuntu@grotian:~$ sudo modprobe libceph modprobe: ERROR: could not insert 'libceph': Exec format error ubuntu@grotian:~$ dmesg [66988.470307] module libceph: unsupported RELA relocation: 275 [Regression Risk] The scope of the fix is restricted to aarch64, so regressions should only impact the arm64 port of Ubuntu. Regressions could impact when literal loads are used - which may have performance impacts or possibly cause software to fail to build/run where it previously did. This is somewhat mitigated by the fact that this has been fixed in artful gcc-5/gcc-6 and used on our buildds for some time. Only "somewhat", because gcc-7 is now the default. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1695093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770240] 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 1770240 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/1770240 Title: Can't install kernel 4.15.0-19 Status in linux package in Ubuntu: Incomplete Bug description: Running ubuntu 18.04 with kernel 4.15.0-20, but would like to reinstall the -19 to test issues and compare: linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767403] Re: linux-aws: 4.15.0-1008.8 -proposed tracker
** Changed in: linux-aws (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1767403 Title: linux-aws: 4.15.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767406] Re: linux-azure: 4.15.0-1010.10 -proposed tracker
** Changed in: linux-azure (Ubuntu Bionic) Status: Invalid => Confirmed ** Tags added: kernel-block-ppa ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1767406 Title: linux-azure: 4.15.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767409] Re: linux-kvm: 4.15.0-1009.9 -proposed tracker
** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1767409 Title: linux-kvm: 4.15.0-1009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770244] Re: Decode ARM CPER records in kernel
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Description changed: [Impact] TBD [Test Case] TBD [Fix] - TBD + c6d8c8ef1d0d94fdae9f5d72982963db89f9cdad efi: Move ARM CPER code to new file + 301f55b1a9177132d2b9ce8a90bf0ae4b37bb850 efi: Parse ARM error information value [Regression Risk] TBD ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) 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/1770244 Title: Decode ARM CPER records in kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] TBD [Test Case] TBD [Fix] c6d8c8ef1d0d94fdae9f5d72982963db89f9cdad efi: Move ARM CPER code to new file 301f55b1a9177132d2b9ce8a90bf0ae4b37bb850 efi: Parse ARM error information value [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767927] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2018-05-09 17:11 EDT--- @haochanh please verify and close. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767927 Title: ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU ATTEMPT TO RE-ENTER FIRMWARE! Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Application Cdeadmin - 2018-03-20 14:10:53 == == Comment: #1 - Application Cdeadmin - 2018-03-20 14:10:54 == == Comment: #2 - Application Cdeadmin - 2018-03-20 14:10:56 == --- Comment From dougmill-ibm 2018-03-20 13:51:47 EDT --- This problem is not tied to a Linux distro. It will be fixed in firmware, as I understand it. Let us close any redundant issues for this same problem. Mark them as duplicate. == Comment: #3 - Application Cdeadmin - 2018-03-20 15:50:54 == --- Comment From mzipse 2018-03-20 15:44:26 EDT --- @stewart-ibm @svaidy , I need to you take a first look. The stop fixes that Vaidy had previously highlighted in a recent note are included in the 3/15 PNOR. == Comment: #5 - Application Cdeadmin - 2018-04-04 16:10:56 == --- Comment From haochanh 2018-04-04 16:04:07 EDT --- We update to 0330, bmc=1.18, then we hit bug 1134. Currently we are running with disable stop5 but still see the watchdog: hard lockup. After 2 hours of test run, I am seeing the "Watchdog: Lockup' and "became unstuck" [Wed Apr 4 13:38:25 2018] Watchdog CPU:42 Hard LOCKUP [Wed Apr 4 13:38:25 2018] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) cxl pnv_php mlx4_en(OE) mlx4_ib(OE) ib_core(OE) mlx4_core(OE) devlink mlx_compat(OE) kvm_hv kvm binfmt_misc dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds joydev mac_hid idt_89hpesx ipmi_powernv [Wed Apr 4 13:38:25 2018] vmx_crypto ipmi_devintf at24 ofpart uio_pdrv_genirq cmdlinepart uio powernv_flash ipmi_msghandler mtd crct10dif_vpmsum opal_prd ibmpowernv nfsd sch_fq_codel auth_rpcgss nfs_acl lockd grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq ses enclosure scsi_transport_sas hid_generic usbhid hid lpfc ast i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea sysfillrect nvmet sysimgblt fb_sys_fops nvme_fc nvme_fabrics crc32c_vpmsum drm i40e scsi_transport_fc aacraid [last unloaded: mlxfw] [Wed Apr 4 13:38:25 2018] CPU: 42 PID: 0 Comm: swapper/42 Tainted: G OE4.15.0-12-generic #13 [Wed Apr 4 13:38:25 2018] NIP: c00a3ca4 LR: c00a3ca4 CTR: c0008000 [Wed Apr 4 13:38:25 2018] REGS: c00ff596fc40 TRAP: 0100 Tainted: G OE (4.15.0-12-generic) [Wed Apr 4 13:38:25 2018] MSR: 90001033 CR: 24004482 XER: 2004 [Wed Apr 4 13:38:25 2018] CFAR: c00ff596fda0 SOFTE: 42 GPR00: c00a3ca4 c00ff596fda0 c16eb200 c00ff596fc40 GPR04: b0001033 c00a3690 24004484 000ffa45 GPR08: 0001 c0d10ed8 00ff GPR12: 90121033 c7a3ce00 c00ff596ff90 GPR16: c0047840 c0047810 c11b5380 GPR20: 0800 c1722484 002a GPR24: 00a8 0007 0007 GPR28: c161d270 c00ffb666fd8 c161d528 0007 [Wed Apr 4 13:38:25 2018] NIP [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] LR [c00a3ca4] power9_idle_type+0x24/0x40 [Wed Apr 4 13:38:25 2018] Call Trace: [Wed Apr 4 13:38:25 2018] [c00ff596fda0] [c00a3ca4] power9_idle_type+0x24/0x40 (unreliable) [Wed Apr 4 13:38:25 2018] [c00ff596fdc0] [c0ad1240] stop_loop+0x40/0x5c [Wed Apr 4 13:38:25 2018] [c00ff596fdf0] [c0acd9a4] cpuidle_enter_state+0xa4/0x450 [Wed Apr 4 13:38:25 2018] [c00ff596fe50] [c01719
[Kernel-packages] [Bug 1747492] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering
setting `nomodeset` in the grub kernel line allows it to display in a lower resolution -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747492 Title: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering Status in linux package in Ubuntu: Incomplete Bug description: After installing 17.10.1, plugging in the 15m DisplayPort cable, it works, however, there is an unusable amount of screen tearing and flickering, and pixelated lines across the screen --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: eric 2029 F pulseaudio /dev/snd/controlC1: eric 2029 F pulseaudio /dev/snd/pcmC0D0p: eric 2029 F...m pulseaudio /dev/snd/controlC0: eric 2029 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff InstallationDate: Installed on 2018-02-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: artful Uname: Linux 4.13.0-32-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/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: X299 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference
Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413440. When I use the workaround described in comment 29 in bug 1413440 (booting with GRUB options 'pci=nomsi iommu=soft') then XHCI doesn't hang, and when I run the reset script described in this bug report, it doesn't cause a kernel bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763594 Title: xhci hangs; reset results in NULL pointer dereference Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Now and then, my xhci bus will hang, resulting in these kinds of messages in dmesg: [252220.002102] xhci_hcd :00:14.0: xHC is not running. [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up [252220.133794] usb 1-2: USB disconnect, device number 2 [252220.135042] usb 1-7: USB disconnect, device number 3 [252220.137455] usb 1-8: USB disconnect, device number 4 [252220.243317] usb 1-9: USB disconnect, device number 5 Usually, I can fix this bij resetting the bus by calling a script reset-xhci: for xhci in /sys/bus/pci/drivers/?hci_hcd ; do cd $xhci echo Resetting devices from $xhci... for i in :??:??.? ; do echo -n "$i" > unbind echo -n "$i" > bind done done But doing this today resulted in a kernel bug: [252243.401814] xhci_hcd :00:14.0: remove, state 4 [252243.401887] usb usb2: USB disconnect, device number 1 [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered [252243.470378] xhci_hcd :00:14.0: remove, state 4 [252243.470383] usb usb1: USB disconnect, device number 1 [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19 [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed. [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered [252243.475938] [ cut here ] [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device [252243.475951] WARNING: CPU: 2 PID: 1787 at /build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 pci_disable_device+0x9c/0xc0 [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE nf_nat_masquerade_ipv4 [252243.475984] xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq btrtl [252243.476023] iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 [252243.476067] raid0 multipath linear dm_mirror dm_region_hash dm_log usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfi
[Kernel-packages] [Bug 1770254] 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 1770254 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: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770254 Title: [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. This is triggered by issuing a bus or a slot reset on the PCI device. [Fix] The following patches checks indicate that the reset is not possible preventing the kernel panic. 357027786f35 PCI: Avoid bus reset if bridge itself is broken 822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset 33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken These patches are already in Bionic, we need these patches in Artful so that xenial linux-hwe also has the fix. The platforms of interest were certified with Xenial and linux-hwe, so we are interested in fixing this only in Artful. [Test] - Artful Host with Artful/bionic guests - Pass though PCI device (vfio-pci) from Artful to bionic and make sure its usable. - The device should pass through and not cause a kernel panic. [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770240] Re: Can't install kernel 4.15.0-19
** Attachment added: "downgrade-kernel.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+attachment/5136911/+files/downgrade-kernel.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770240 Title: Can't install kernel 4.15.0-19 Status in linux package in Ubuntu: New Bug description: Running ubuntu 18.04 with kernel 4.15.0-20, but would like to reinstall the -19 to test issues and compare: linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
The workaround in comment #26 works for me on a Lenovo Yoga 720-15 running kernel 4.17.0-041700rc3-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in System76: Triaged Status in linux package in Ubuntu: Triaged Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1413440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770254] [NEW] [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic.
Public bug reported: [Impact] Using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. This is triggered by issuing a bus or a slot reset on the PCI device. [Fix] The following patches checks indicate that the reset is not possible preventing the kernel panic. 357027786f35 PCI: Avoid bus reset if bridge itself is broken 822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset 33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken These patches are already in Bionic, we need these patches in Artful so that xenial linux-hwe also has the fix. The platforms of interest were certified with Xenial and linux-hwe, so we are interested in fixing this only in Artful. [Test] - Artful Host with Artful/bionic guests - Pass though PCI device (vfio-pci) from Artful to bionic and make sure its usable. - The device should pass through and not cause a kernel panic. [Regression Potential] None. ** Affects: linux (Ubuntu) Importance: Critical Status: New ** Tags: cn88xx ** Description changed: [Impact] Using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. This is triggered by issuing a bus or a slot reset on the PCI device. [Fix] The following patches checks indicate that the reset is not possible preventing the kernel panic. 357027786f35 PCI: Avoid bus reset if bridge itself is broken 822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset 33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken These patches are already in Bionic, we need these patches in Artful so - that xenial linux-hwe also has the fix. + that xenial linux-hwe also has the fix. The platforms of interest were + certified with Xenial and linux-hwe, so we are interested in fixing this + only in Artful. [Test] - Artful Host with Artful/bionic guests - Pass though PCI device (vfio-pci) from Artful to bionic and make sure its usable. - The device should pass through and not cause a kernel panic. [Regression Potential] None. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770254 Title: [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. Status in linux package in Ubuntu: New Bug description: [Impact] Using vfio-pci on a combination of cn8xxx and some PCI devices results in a kernel panic. This is triggered by issuing a bus or a slot reset on the PCI device. [Fix] The following patches checks indicate that the reset is not possible preventing the kernel panic. 357027786f35 PCI: Avoid bus reset if bridge itself is broken 822155100e58 PCI: Mark Cavium CN8xxx to avoid bus reset 33ba90aa4d44 PCI: Avoid slot reset if bridge itself is broken These patches are already in Bionic, we need these patches in Artful so that xenial linux-hwe also has the fix. The platforms of interest were certified with Xenial and linux-hwe, so we are interested in fixing this only in Artful. [Test] - Artful Host with Artful/bionic guests - Pass though PCI device (vfio-pci) from Artful to bionic and make sure its usable. - The device should pass through and not cause a kernel panic. [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770256] [NEW] linux packages should own /usr/lib/linux/triggers
Public bug reported: Rather than randomly mkdir/rmdir'ing /usr/lib/linux/triggers all of the binary packages that use triggers should contain this directory. This will allow dpkg to reference count the directory and detect left over files correctly. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770256 Title: linux packages should own /usr/lib/linux/triggers Status in linux package in Ubuntu: In Progress Bug description: Rather than randomly mkdir/rmdir'ing /usr/lib/linux/triggers all of the binary packages that use triggers should contain this directory. This will allow dpkg to reference count the directory and detect left over files correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770240] Re: Can't install kernel 4.15.0-19
root@ubuntu:~# sudo apt install linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-modules-extra-4.15.0-19-generic:amd64 E: Couldn't find any package by glob 'linux-modules-extra-4.15.0-19-generic' E: Couldn't find any package by regex 'linux-modules-extra-4.15.0-19-generic' E: Unable to locate package linux-modules-4.15.0-19-generic:amd64 E: Couldn't find any package by glob 'linux-modules-4.15.0-19-generic' E: Couldn't find any package by regex 'linux-modules-4.15.0-19-generic' E: Unable to locate package linux-headers-4.15.0-19-generic:amd64 E: Couldn't find any package by glob 'linux-headers-4.15.0-19-generic' E: Couldn't find any package by regex 'linux-headers-4.15.0-19-generic' E: Unable to locate package linux-headers-4.15.0-19:amd64 E: Couldn't find any package by glob 'linux-headers-4.15.0-19' E: Couldn't find any package by regex 'linux-headers-4.15.0-19' E: Unable to locate package linux-image-4.15.0-19-generic:amd64 E: Couldn't find any package by glob 'linux-image-4.15.0-19-generic' E: Couldn't find any package by regex 'linux-image-4.15.0-19-generic' root@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/1770240 Title: Can't install kernel 4.15.0-19 Status in linux package in Ubuntu: Incomplete Bug description: Running ubuntu 18.04 with kernel 4.15.0-20, but would like to reinstall the -19 to test issues and compare: linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload policy modification 0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support starting an adapter context bef2014e8bd6391988b588acb969b48133072f17 scsi: cxlflash: Support process specific mappings 58b43437bd85565c74c2b6975cc71003b93f3559 scsi: cxlflash: Supp
[Kernel-packages] [Bug 1763189] Re: kernel 4.15 breaks nouveau on Lenovo P50
https://bugs.freedesktop.org/show_bug.cgi?id=106456 ** Bug watch added: freedesktop.org Bugzilla #106456 https://bugs.freedesktop.org/show_bug.cgi?id=106456 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763189 Title: kernel 4.15 breaks nouveau on Lenovo P50 Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux 4.15.0-13-generic, the system freezes at boot, apparently when the nouveau driver tries to start. The console is still in 80x25 text mode at this point. No panic or error message is displayed, only unrelated log messages (screenshot attached). Booting in recovery mode is possible and allows X11 to start using the vesa driver. nouveau still works fine when booting an older kernel (4.13.0-36-generic) so this problem seems to be specific to 4.15.0. ProblemType: Bug ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Apr 11 17:25:27 2018 Dependencies: adduser 3.113+nmu3ubuntu4 apt 1.2.26 apt-utils 1.2.26 busybox-initramfs 1:1.22.0-15ubuntu1 coreutils 8.25-2ubuntu3~16.04 cpio 2.11+dfsg-5ubuntu1 debconf 1.5.58ubuntu1 debianutils 4.7 dpkg 1.18.4ubuntu1.4 e2fslibs 1.42.13-1ubuntu1 e2fsprogs 1.42.13-1ubuntu1 gcc-5-base 5.4.0-6ubuntu1~16.04.9 gcc-6-base 6.0.1-0ubuntu1 gettext-base 0.19.7-2ubuntu3 gnupg 1.4.20-1ubuntu3.1 gpgv 1.4.20-1ubuntu3.1 grub-common 2.02~beta2-36ubuntu3.17 grub-gfxpayload-lists 0.7 grub-pc 2.02~beta2-36ubuntu3.17 grub-pc-bin 2.02~beta2-36ubuntu3.17 grub2-common 2.02~beta2-36ubuntu3.17 init-system-helpers 1.29ubuntu4 initramfs-tools 0.122ubuntu8.11 initramfs-tools-bin 0.122ubuntu8.11 initramfs-tools-core 0.122ubuntu8.11 initscripts 2.88dsf-59.3ubuntu2 insserv 1.14.0-5ubuntu3 klibc-utils 2.0.4-8ubuntu1.16.04.4 kmod 22-1ubuntu5 libacl1 2.2.52-3 libapt-inst2.0 1.2.26 libapt-pkg5.0 1.2.26 libasprintf0v5 0.19.7-2ubuntu3 libattr1 1:2.4.47-2 libaudit-common 1:2.4.5-1ubuntu2.1 libaudit1 1:2.4.5-1ubuntu2.1 libblkid1 2.27.1-6ubuntu3.4 libbz2-1.0 1.0.6-8 libc6 2.23-0ubuntu10 libcomerr2 1.42.13-1ubuntu1 libdb5.3 5.3.28-11ubuntu0.1 libdevmapper1.02.1 2:1.02.110-1ubuntu10 libfdisk1 2.27.1-6ubuntu3.4 libfreetype6 2.6.1-0.1ubuntu2.3 libfuse2 2.9.4-1ubuntu3.1 libgcc1 1:6.0.1-0ubuntu1 libgcrypt20 1.6.5-2ubuntu0.4 libgpg-error0 1.21-2ubuntu1 libgpm2 1.20.4-6.1 libklibc 2.0.4-8ubuntu1.16.04.4 libkmod2 22-1ubuntu5 liblz4-1 0.0~r131-2ubuntu2 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.27.1-6ubuntu3.4 libncurses5 6.0+20160213-1ubuntu1 libncursesw5 6.0+20160213-1ubuntu1 libpam-modules 1.1.8-3.2ubuntu2 libpam-modules-bin 1.1.8-3.2ubuntu2 libpam0g 1.1.8-3.2ubuntu2 libpcre3 2:8.38-3.1 libpng12-0 1.2.54-1ubuntu1 libprocps4 2:3.3.10-4ubuntu2.3 libreadline6 6.3-8ubuntu2 libselinux1 2.4-3build2 libsemanage-common 2.3-1build3 libsemanage1 2.3-1build3 libsepol1 2.4-2 libsmartcols1 2.27.1-6ubuntu3.4 libss2 1.42.13-1ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.9 libsystemd0 229-4ubuntu21.2 libtinfo5 6.0+20160213-1ubuntu1 libudev1 229-4ubuntu21.2 libusb-0.1-4 2:0.1.12-28 libustr-1.0-1 1.0.4-5 libuuid1 2.27.1-6ubuntu3.4 linux-base 4.0ubuntu1 lsb-base 9.20160110ubuntu0.2 mount 2.27.1-6ubuntu3.4 multiarch-support 2.23-0ubuntu10 os-prober 1.70ubuntu3.3 passwd 1:4.2-3.1ubuntu5.3 perl-base 5.22.1-9ubuntu0.2 procps 2:3.3.10-4ubuntu2.3 psmisc 22.21-2.1build1 readline-common 6.3-8ubuntu2 sensible-utils 0.0.9ubuntu0.16.04.1 sysv-rc 2.88dsf-59.3ubuntu2 sysvinit-utils 2.88dsf-59.3ubuntu2 tar 1.28-2.1ubuntu0.1 ubuntu-keyring 2012.05.19 ucf 3.0036 udev 229-4ubuntu21.2 util-linux 2.27.1-6ubuntu3.4 uuid-runtime 2.27.1-6ubuntu3.4 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-02-01 (434 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: -- Logs begin at Wed 2018-04-11 17:25:19 EDT, end at Wed 2018-04-11 17:25:22 EDT. -- Apr 11 17:25:19 hostname kernel: Intel Spectre v2 broken microcode detected; disabling Speculation Control Apr 11 17:25:19 hostname kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Apr 11 17:25:19 hostname kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) Apr 11 17:25:19 hostname kernel: resource sanity check: requesting [mem 0xfed1-0xfed15fff], which spans more than pnp 00:01 [mem 0xfed1-0xfed13fff] Apr 11 17:25:19 hostname kernel: caller snb_uncore_imc_init_box+0x6b/0xb0 mapping multiple BARs Apr 11 17:25:19 hostname kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). Apr 11 17:25:19
[Kernel-packages] [Bug 1768849] Re: Battery power depleting rapidly
** Description changed: - Percentage battery power left depletes rapidly with regular use of the PC. + Percentage battery power left depletes rapidly with regular use of the PC, when the computer is on. This issue does not occur on such a scale in Windows, leaving me to believe this is an issue with something in Linux using too many resources. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 09:34:17 2018 InstallationDate: Installed on 2018-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768849 Title: Battery power depleting rapidly Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Percentage battery power left depletes rapidly with regular use of the PC, when the computer is on. This issue does not occur on such a scale in Windows, leaving me to believe this is an issue with something in Linux using too many resources. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 09:34:17 2018 InstallationDate: Installed on 2018-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1768849/+subscriptions -- Mailing list: https://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 1769376] Re: NMI watchdog: Watchdog detected hard LOCKUP on cpu x
The version that is currently working and has worked in the past is 16.04 LTS. Both 17.10 and 18.04 were non-functional for me. Tried multiple installs, each with the same results. Unfortunately, I can't test anything else on this machine atm as it's my work machine and I need it to be available pretty much constantly. On Mon, May 7, 2018 at 10:08 AM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.17 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4 > > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1769376 > > Title: > NMI watchdog: Watchdog detected hard LOCKUP on cpu x > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Machine: > > ASUS ROG GL753VE Laptop > > Clean install of Ubuntu 18.04 LTS (I've reinstalled several times and > get same error). > > This is the error: > > NMI watchdog: Watchdog detected hard LOCKUP on cpu x (where x is some > cpu #) > > I am also seeing the following errors at random: > > watchdog: BUG: soft lockup - CPU#X stuck for 23s! [kworker/3:0:29] > watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:335] > watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:575] > > > Unfortunately due to the nature of this bug, I cannot gather any logs or > report using the Terminal. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1769376/+subscriptions > -- Blair -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769376 Title: NMI watchdog: Watchdog detected hard LOCKUP on cpu x Status in linux package in Ubuntu: Incomplete Bug description: Machine: ASUS ROG GL753VE Laptop Clean install of Ubuntu 18.04 LTS (I've reinstalled several times and get same error). This is the error: NMI watchdog: Watchdog detected hard LOCKUP on cpu x (where x is some cpu #) I am also seeing the following errors at random: watchdog: BUG: soft lockup - CPU#X stuck for 23s! [kworker/3:0:29] watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:335] watchdog: BUG: soft lockup - CPU#X stuck for 23s! [systemd-udevd:575] Unfortunately due to the nature of this bug, I cannot gather any logs or report using the Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1247806] Re: Kernel resetting SATA link
Yup changing the SATA mode to 'Compatibility' solved this issue for me. No more error logs indicating failed SATA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247806 Title: Kernel resetting SATA link Status in linux package in Ubuntu: Expired Bug description: On Ubuntu 13.10 I encounter kernel reseting SATA link in connection with temporary system freezes (KDE lags). Such a bug has previously been reported here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/888764 for the same hardware but older software. This behavior has also been reported here https://lkml.org/lkml/2011/10/26/11 for same hardware and in connection with unresponsive KDE. For me it occurs if the system is under high load. In such situations dmesg says repeatedly: [23391.818508] ata4: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe frozen [23391.818513] ata4: irq_stat 0x0040, connection status changed [23391.818516] ata4: SError: { CommWake DevExch } [23391.818523] ata4: limiting SATA link speed to 1.5 Gbps [23391.818525] ata4: hard resetting link [23392.538993] ata4: SATA link down (SStatus 0 SControl 310) [23392.554893] ata4: EH complete Smart does not report any critical errors: === START OF INFORMATION SECTION === Model Family: Seagate Momentus Thin Device Model: ST320LT007-9ZV142 Serial Number:W0Q4FQRR LU WWN Device Id: 5 000c50 04998da73 Firmware Version: 0004LVM1 User Capacity:320'072'933'376 bytes [320 GB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:7242 rpm Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s) Local Time is:Mon Nov 4 12:55:25 2013 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:(0) seconds. Offline data collection capabilities:(0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 63) minutes. Conveyance self-test routine recommended polling time:( 2) minutes. SCT capabilities: (0x303b) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 113 099 034Pre-fail Always - 55387800 3 Spin_Up_Time0x0003 098 098 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 768 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 074 060 030Pre-fail Always - 8647632770 9 Power_On_Hours 0x0032 097 097 000Old_age Always - 3216 (255
[Kernel-packages] [Bug 1770240] Re: Can't install kernel 4.15.0-19
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770240 Title: Can't install kernel 4.15.0-19 Status in linux package in Ubuntu: Incomplete Bug description: Running ubuntu 18.04 with kernel 4.15.0-20, but would like to reinstall the -19 to test issues and compare: linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763189] Re: kernel 4.15 breaks nouveau on Lenovo P50
Bisected: af2405af07d168e2905f2ac9494d3a804a549f0f is the first bad commit commit af2405af07d168e2905f2ac9494d3a804a549f0f Author: Thierry Reding Date: Tue Jul 4 17:18:21 2017 +0200 drm/fb-helper: Push down modeset lock into FB helpers Move the modeset locking from drivers into FB helpers. v2: Also handle intel_connector_add_to_fbdev. v3: Prevent race in intel_dp_mst with ->detect (Maarten) Cc: Maarten Lankhorst Cc: Alex Deucher Cc: Christian König Tested-by: John Stultz Signed-off-by: Thierry Reding (v1) Reviewed-by: Maarten Lankhorst Signed-off-by: Daniel Vetter Link: http://patchwork.freedesktop.org/patch/msgid/20170704151833.17304-2-daniel.vet...@ffwll.ch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763189 Title: kernel 4.15 breaks nouveau on Lenovo P50 Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux 4.15.0-13-generic, the system freezes at boot, apparently when the nouveau driver tries to start. The console is still in 80x25 text mode at this point. No panic or error message is displayed, only unrelated log messages (screenshot attached). Booting in recovery mode is possible and allows X11 to start using the vesa driver. nouveau still works fine when booting an older kernel (4.13.0-36-generic) so this problem seems to be specific to 4.15.0. ProblemType: Bug ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Apr 11 17:25:27 2018 Dependencies: adduser 3.113+nmu3ubuntu4 apt 1.2.26 apt-utils 1.2.26 busybox-initramfs 1:1.22.0-15ubuntu1 coreutils 8.25-2ubuntu3~16.04 cpio 2.11+dfsg-5ubuntu1 debconf 1.5.58ubuntu1 debianutils 4.7 dpkg 1.18.4ubuntu1.4 e2fslibs 1.42.13-1ubuntu1 e2fsprogs 1.42.13-1ubuntu1 gcc-5-base 5.4.0-6ubuntu1~16.04.9 gcc-6-base 6.0.1-0ubuntu1 gettext-base 0.19.7-2ubuntu3 gnupg 1.4.20-1ubuntu3.1 gpgv 1.4.20-1ubuntu3.1 grub-common 2.02~beta2-36ubuntu3.17 grub-gfxpayload-lists 0.7 grub-pc 2.02~beta2-36ubuntu3.17 grub-pc-bin 2.02~beta2-36ubuntu3.17 grub2-common 2.02~beta2-36ubuntu3.17 init-system-helpers 1.29ubuntu4 initramfs-tools 0.122ubuntu8.11 initramfs-tools-bin 0.122ubuntu8.11 initramfs-tools-core 0.122ubuntu8.11 initscripts 2.88dsf-59.3ubuntu2 insserv 1.14.0-5ubuntu3 klibc-utils 2.0.4-8ubuntu1.16.04.4 kmod 22-1ubuntu5 libacl1 2.2.52-3 libapt-inst2.0 1.2.26 libapt-pkg5.0 1.2.26 libasprintf0v5 0.19.7-2ubuntu3 libattr1 1:2.4.47-2 libaudit-common 1:2.4.5-1ubuntu2.1 libaudit1 1:2.4.5-1ubuntu2.1 libblkid1 2.27.1-6ubuntu3.4 libbz2-1.0 1.0.6-8 libc6 2.23-0ubuntu10 libcomerr2 1.42.13-1ubuntu1 libdb5.3 5.3.28-11ubuntu0.1 libdevmapper1.02.1 2:1.02.110-1ubuntu10 libfdisk1 2.27.1-6ubuntu3.4 libfreetype6 2.6.1-0.1ubuntu2.3 libfuse2 2.9.4-1ubuntu3.1 libgcc1 1:6.0.1-0ubuntu1 libgcrypt20 1.6.5-2ubuntu0.4 libgpg-error0 1.21-2ubuntu1 libgpm2 1.20.4-6.1 libklibc 2.0.4-8ubuntu1.16.04.4 libkmod2 22-1ubuntu5 liblz4-1 0.0~r131-2ubuntu2 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.27.1-6ubuntu3.4 libncurses5 6.0+20160213-1ubuntu1 libncursesw5 6.0+20160213-1ubuntu1 libpam-modules 1.1.8-3.2ubuntu2 libpam-modules-bin 1.1.8-3.2ubuntu2 libpam0g 1.1.8-3.2ubuntu2 libpcre3 2:8.38-3.1 libpng12-0 1.2.54-1ubuntu1 libprocps4 2:3.3.10-4ubuntu2.3 libreadline6 6.3-8ubuntu2 libselinux1 2.4-3build2 libsemanage-common 2.3-1build3 libsemanage1 2.3-1build3 libsepol1 2.4-2 libsmartcols1 2.27.1-6ubuntu3.4 libss2 1.42.13-1ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.9 libsystemd0 229-4ubuntu21.2 libtinfo5 6.0+20160213-1ubuntu1 libudev1 229-4ubuntu21.2 libusb-0.1-4 2:0.1.12-28 libustr-1.0-1 1.0.4-5 libuuid1 2.27.1-6ubuntu3.4 linux-base 4.0ubuntu1 lsb-base 9.20160110ubuntu0.2 mount 2.27.1-6ubuntu3.4 multiarch-support 2.23-0ubuntu10 os-prober 1.70ubuntu3.3 passwd 1:4.2-3.1ubuntu5.3 perl-base 5.22.1-9ubuntu0.2 procps 2:3.3.10-4ubuntu2.3 psmisc 22.21-2.1build1 readline-common 6.3-8ubuntu2 sensible-utils 0.0.9ubuntu0.16.04.1 sysv-rc 2.88dsf-59.3ubuntu2 sysvinit-utils 2.88dsf-59.3ubuntu2 tar 1.28-2.1ubuntu0.1 ubuntu-keyring 2012.05.19 ucf 3.0036 udev 229-4ubuntu21.2 util-linux 2.27.1-6ubuntu3.4 uuid-runtime 2.27.1-6ubuntu3.4 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-02-01 (434 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: -- Logs begin at Wed 2018-04-11 17:25:19 EDT, end at Wed 2018-04-11 17:25:22 EDT. -- Apr 11 17:25:19 hostname kernel: Intel Spectre v2 broken microcode detected; disabling Speculation Control Apr 11 17:25:19 hostname kernel: ENERGY_PE
[Kernel-packages] [Bug 1770240] 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 1770240 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/1770240 Title: Can't install kernel 4.15.0-19 Status in linux package in Ubuntu: Incomplete Bug description: Running ubuntu 18.04 with kernel 4.15.0-20, but would like to reinstall the -19 to test issues and compare: linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136903/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136900/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136898/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136899/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136901/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136904/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136902/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136897/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136895/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
I built a Bionic test kernel with the three commits reverted and three new patches posted in comment #2. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1768431 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cf
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
** Patch added: "0002-Revert-UBUNTU-SAUCE-cxlflash-Read-host-AFU-configura.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768431/+attachment/5136888/+files/0002-Revert-UBUNTU-SAUCE-cxlflash-Read-host-AFU-configura.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload policy modification 0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support starting an adapter context bef2014e8bd6391988b588acb969b48133072f17 scsi: cxlflash: Support pro
[Kernel-packages] [Bug 1668080] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136893/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136894/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
Also, the three reverts did not revert cleanly, so I had to backport them. I attached them to this bug for review. ** Patch added: "0001-Revert-UBUNTU-SAUCE-cxlflash-Use-IDR-to-ma.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768431/+attachment/5136887/+files/0001-Revert-UBUNTU-SAUCE-cxlflash-Use-IDR-to-ma.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload policy modification 0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support sta
[Kernel-packages] [Bug 1668080] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136892/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668080] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136896/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
** Patch added: "0003-Revert-UBUNTU-SAUCE-cxlflash-Read-host-function-conf.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768431/+attachment/5136889/+files/0003-Revert-UBUNTU-SAUCE-cxlflash-Read-host-function-conf.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768431 Title: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c914269c58a6000 scsi: cxlflash: Setup AFU acTag range b42d68d728a63337bcb7860b59e6458946d94a84 scsi: cxlflash: Setup AFU PASID de25ec59a75802584aac97aed05fd94094dbbb58 scsi: cxlflash: Adapter context support for OCXL a76fc993e399f54b37f46107a31e817c779f2b82 scsi: cxlflash: Use IDR to manage adapter contexts 09f35da5fe218baf73f7b4efd281e2c19490512c scsi: cxlflash: Support adapter file descriptors for OCXL 17f9335bc59c1cf8f93617eee137e745abd71a3f scsi: cxlflash: Support adapter context discovery a5cfe355f23d4410d69af0e5b196b095463a0b4b scsi: cxlflash: Support image reload policy modification 0c62e7c091a4e0a01a7c6027fe719625ab2f521e scsi: cxlflash: MMIO map the AFU f39bab766ea4f0b3d5888fdd7d66babd7bef3966 scsi: cxlflash: Support starting an adapter context bef2014e8bd6391988b588acb969b48133072f17 scsi: cxlflash: Support pro
[Kernel-packages] [Bug 1668080] Re: Sporadically no wireless connection after resume from STR with Intel 7265D
apport information ** Tags added: apport-collected ** Description changed: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: bor2230 F pulseaudio + /dev/snd/controlC0: bor2230 F pulseaudio + CurrentDesktop: Unity + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-trusty-amd64-20140620-0 + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 + InstallationDate: Installed on 2015-07-02 (1042 days ago) + InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 + MachineType: Dell Inc. Latitude E5450 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M + ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-41-generic N/A + linux-backports-modules-4.13.0-41-generic N/A + linux-firmware 1.157.17 + Tags: xenial + Uname: Linux 4.13.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/23/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A19 + dmi.board.name: 06J17N + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E5450 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136890/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1668080] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1668080/+attachment/5136891/+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/1668080 Title: Sporadically no wireless connection after resume from STR with Intel 7265D Status in linux package in Ubuntu: Confirmed Bug description: Sporadically after resume from suspend to RAM there is no wifi connection. There are no errors in kernel log, just no connection: [101937.000998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.003094] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.003257] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067718] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.067879] iwlwifi :02:00.0: L1 Disabled - LTR Enabled [101937.082365] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [101937.189536] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Reloading iwlwifi + iwlmvm modules clears it and connection is established immediately. Several times connection also dropped during normal activity; not sure whether this is related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-39-generic 4.8.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 26 19:58:12 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (605 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-10-29 (120 days ago) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bor2230 F pulseaudio /dev/snd/controlC0: bor2230 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93 InstallationDate: Installed on 2015-07-02 (1042 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-41-generic N/A linux-backports-modules-4.13.0-41-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd01/23/2018:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770003] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-09 15:31 EDT--- We are focusing on P9 now, but we believe this exists on all platforms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770003 Title: qla2xxx: Fix page fault at kmem_cache_alloc_node() Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Dear Canonical, We found that the current Ubuntu kernel contains a problem related to qla2xxx driver which causes: [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.20) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace We were able to get rid of this problem cherry picking some of the upstream patches. Do you think they might fit in the SRU criteria? The commit ids are below and they were easily cherry picked. eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug after firmware timeout 6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin trigger from sending too many commands 7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout() 045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled. 1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session free in qlt_free_session_done d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session deletion by using work_lock Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: Fixup locking for session deletion') 94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_dele? 9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup for N2N To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770240] 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 1770240 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/1770240 Title: Can't install kernel 4.15.0-19 Status in linux package in Ubuntu: Incomplete Bug description: Running ubuntu 18.04 with kernel 4.15.0-20, but would like to reinstall the -19 to test issues and compare: linux-modules-extra-4.15.0-19-generic:amd64 linux-modules-4.15.0-19-generic:amd64 linux-headers-4.15.0-19-generic:amd64 linux-headers-4.15.0-19:amd64 linux-image-4.15.0-19-generic:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769996] Re: linux-oem: 4.13.0-1027.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1769996 Title: linux-oem: 4.13.0-1027.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770003] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2018-05-09 15:26 EDT--- >bug does not say if this was found in P8 or P9 Sorry, it was identified and it is being debugged on a POWER9 machine. Not sure if this happen or not on POWER8 yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770003 Title: qla2xxx: Fix page fault at kmem_cache_alloc_node() Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Dear Canonical, We found that the current Ubuntu kernel contains a problem related to qla2xxx driver which causes: [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.20) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace We were able to get rid of this problem cherry picking some of the upstream patches. Do you think they might fit in the SRU criteria? The commit ids are below and they were easily cherry picked. eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug after firmware timeout 6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin trigger from sending too many commands 7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout() 045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled. 1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session free in qlt_free_session_done d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session deletion by using work_lock Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: Fixup locking for session deletion') 94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_dele? 9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup for N2N To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770244] 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 1770244 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770244 Title: Decode ARM CPER records in kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] TBD [Test Case] TBD [Fix] TBD [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768647] Re: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password
Finally enabled bionic-proposed, and newest kernel 4.15.0-21-generic works again, so I guess it's fixed upstream. This is part of the update log for future reference: root@ubuntu:/var/log/apt# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-image-4.15.0-20-generic linux-modules-4.15.0-20-generic linux-modules-extra-4.15.0-20-generic Use 'apt autoremove' to remove them. The following NEW packages will be installed: linux-headers-4.15.0-21 linux-headers-4.15.0-21-generic linux-image-4.15.0-21-generic linux-modules-4.15.0-21-generic linux-modules-extra-4.15.0-21-generic The following packages will be upgraded: gnome-initial-setup gnome-session-bin gnome-session-common gnome-startup-applications ifupdown libgtop-2.0-11 libgtop2-common linux-generic linux-headers-generic linux-image-generic linux-libc-dev linux-signed-generic linux-signed-image-generic linux-source linux-source-4.15.0 netplan.io nplan python3-software-properties software-properties-common software-properties-gtk software-properties-kde ubuntu-session 22 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. Need to get 197 MB of archives. After this operation, 335 MB of additional disk space will be used. Do you want to continue? [Y/n] ** Tags added: kernel-fixed-upstream ** Tags removed: kernel-da-key ** Tags added: kernel-da-key. ** Tags removed: kernel-da-key. ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768647 Title: linux 4.15.0-20-generic messes up plymouth and no prompt for luks password Status in linux package in Ubuntu: Confirmed Bug description: With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment. If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT= && update-initramfs -u it boots in text- only mode and then can enter the password perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770245] [NEW] getlogin will fail to open /proc/self/loginuid
Public bug reported: python os.getlogin() uses glibc getlogin(), which reads /proc/self/loginuid. That file depends on CONFIG_AUDITSYSCALL. It has been there since early Linux 2.6. All our kernels should have it enabled. Cascardo. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Xenial) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-kvm (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1770245 Title: getlogin will fail to open /proc/self/loginuid Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: In Progress Bug description: python os.getlogin() uses glibc getlogin(), which reads /proc/self/loginuid. That file depends on CONFIG_AUDITSYSCALL. It has been there since early Linux 2.6. All our kernels should have it enabled. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1770245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767400] Re: linux-gcp: 4.15.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1767400 Title: linux-gcp: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()
Here is the set of patches I needed to backport/cherry-pick to get a kernel that would build. 2853192e154b scsi: qla2xxx: Use IOCB path to submit Control VP MBX command 11aea16ab3f5 scsi: qla2xxx: Add ability to send PRLO 1c6cacf4ea6c scsi: qla2xxx: Fixup locking for session deletion eaf75d1815da scsi: qla2xxx: Fix double free bug after firmware timeout 6d67492764b3 scsi: qla2xxx: Prevent relogin trigger from sending too many commands 7ac0c332f96b scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout() 045d6ea200af scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled. 1ae634eb2853 scsi: qla2xxx: Serialize session free in qlt_free_session_done d8630bb95f46 scsi: qla2xxx: Serialize session deletion by using work_lock 94cff6e114df scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_deletion() a4239945b8ad scsi: qla2xxx: Add switch command to simplify fabric discovery 040036bb0bc1 scsi: qla2xxx: Delay loop id allocation at login 9cd883f07a54 scsi: qla2xxx: Fix session cleanup for N2N f13515acdcb5 scsi: qla2xxx: Replace GPDB with async ADISC command I have this kernel built in a PPA: ppa:ubuntu-power-triage/lp1770003. This kernel needs to be tested on the platform (bug does not say if this was found in P8 or P9) where the issue was reported, and will also need to be tested on Cavium (ARM64) to make sure there are no regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770003 Title: qla2xxx: Fix page fault at kmem_cache_alloc_node() Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Dear Canonical, We found that the current Ubuntu kernel contains a problem related to qla2xxx driver which causes: [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.20) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace We were able to get rid of this problem cherry picking some of the upstream patches. Do you think they might fit in the SRU criteria? The commit ids are below and they were easily cherry picked. eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug after firmware timeout 6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin trigger from sending too many commands 7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout() 045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled. 1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session free in qlt_free_session_done d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session deletion by using work_lock Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: Fixup locking for session deletion') 94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_dele? 9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup for N2N To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp