[Kernel-packages] [Bug 1806422] Re: linux-azure: 4.18.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806409 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 07:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing 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/1806422 Title: linux-azure: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: 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: 1806409 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 07:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806665] Re: linux-azure: 4.15.0-1036.38 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing 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/1806665 Title: linux-azure: 4.15.0-1036.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808102] Re: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808102 Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: Unknown problem. Other reports submitted by system in last 5 mins. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stewart1606 F...m pulseaudio /dev/snd/controlC0: stewart1606 F pulseaudio Date: Tue Dec 11 17:03:13 2018 DuplicateSignature: package:linux-image-extra-4.4.0-89-generic:4.4.0-89.112 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-image-extra-4.4.0-89-generic (--configure): package linux-image-extra-4.4.0-89-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (665 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2009:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808102] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808102 Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: Unknown problem. Other reports submitted by system in last 5 mins. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stewart1606 F...m pulseaudio /dev/snd/controlC0: stewart1606 F pulseaudio Date: Tue Dec 11 17:03:13 2018 DuplicateSignature: package:linux-image-extra-4.4.0-89-generic:4.4.0-89.112 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-image-extra-4.4.0-89-generic (--configure): package linux-image-extra-4.4.0-89-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (665 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2009:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802834] Re: Dim screen after first boot on Thinkpad A285
After I resume from suspend, I found the backlight is normal, and here is the log. ** Attachment added: "a285.journal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802834/+attachment/5221571/+files/a285.journal.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802834 Title: Dim screen after first boot on Thinkpad A285 Status in linux package in Ubuntu: Confirmed Bug description: We installed the 18.04 daily image on ThinkPad A285, found the screen is dim at the first boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1481 F pulseaudio /dev/snd/controlC0: u 1481 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20MWZ47RUS Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=347498ab-8eae-42d3-a1e3-74e9be6b6ba3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0XET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MWZ47RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0XET30W(1.07):bd09/21/2018:svnLENOVO:pn20MWZ47RUS:pvrThinkPadA285:rvnLENOVO:rn20MWZ47RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad A285 dmi.product.name: 20MWZ47RUS dmi.product.version: ThinkPad A285 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808102] [NEW] package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration canno
Public bug reported: Unknown problem. Other reports submitted by system in last 5 mins. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stewart1606 F...m pulseaudio /dev/snd/controlC0: stewart1606 F pulseaudio Date: Tue Dec 11 17:03:13 2018 DuplicateSignature: package:linux-image-extra-4.4.0-89-generic:4.4.0-89.112 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-image-extra-4.4.0-89-generic (--configure): package linux-image-extra-4.4.0-89-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (665 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/05/2009:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808102 Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Confirmed Bug description: Unknown problem. Other reports submitted by system in last 5 mins. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-89-generic 4.4.0-89.112 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stewart1606 F...m pulseaudio /dev/snd/controlC0: stewart1606 F pulseaudio Date: Tue Dec 11 17:03:13 2018 DuplicateSignature: package:linux-image-extra-4.4.0-89-generic:4.4.0-89.112 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-image-extra-4.4.0-89-generic (--configure): package linux-image-extra-4.4.0-89-generic is not ready for configuration ErrorMessage: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2359cbc7-0ac6-4d11-a02f-df73f23283fe InstallationDate: Installed on 2017-02-14 (665 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: OEM OEM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic root=UUID=868abb4a-f10f-42b4-8c2c-ec7686786f70 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19 RfKill: SourcePackage: linux Title: package linux-image-extra-4.4.0-89-generic 4.4.0-89.112 failed to install/upgrade: package linux-image-extra-4.4.0-89-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.
[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1807339 Title: Add HMS CAN driver for Dell Edge Gateways Status in HWE Next: New Status in linux-oem package in Ubuntu: In Progress Bug description: == Impact == The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 4.15 there's a new release for that. == Fix == Integrate the new release from IHV. == Test Case == Check if the device binds to a driver. == Risk of Regression == The driver binds to certain USB IDs thus should be reasonably low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1807339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Well, i used your tables and they work like pci=noacpi, they disable my dgpu and suspend doesnt work. If you have patched your tables again, against bios 1.11 please send them again for testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802834] Re: Dim screen after first boot on Thinkpad A285
So it looks like the initial brightness is got from atombios of graphic card, so it is atombios issue or the code can't correctly parse the atombios. it is highly possible that this is an atombios issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802834 Title: Dim screen after first boot on Thinkpad A285 Status in linux package in Ubuntu: Confirmed Bug description: We installed the 18.04 daily image on ThinkPad A285, found the screen is dim at the first boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1481 F pulseaudio /dev/snd/controlC0: u 1481 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20MWZ47RUS Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=347498ab-8eae-42d3-a1e3-74e9be6b6ba3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0XET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MWZ47RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0XET30W(1.07):bd09/21/2018:svnLENOVO:pn20MWZ47RUS:pvrThinkPadA285:rvnLENOVO:rn20MWZ47RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad A285 dmi.product.name: 20MWZ47RUS dmi.product.version: ThinkPad A285 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802834] Re: Dim screen after first boot on Thinkpad A285
backlight_level = amdgpu_atombios_encoder_get_backlight_level_from_reg(adev); dig = amdgpu_encoder->enc_priv; dig->bl_dev = bd; bd->props.brightness = amdgpu_atombios_encoder_get_backlight_brightness(bd); bd->props.power = FB_BLANK_UNBLANK; backlight_update_status(bd); DRM_INFO("amdgpu atom DIG backlight initialized\n"); u8 amdgpu_atombios_encoder_get_backlight_level_from_reg(struct amdgpu_device *adev) { u8 backlight_level; u32 bios_2_scratch; bios_2_scratch = RREG32(mmBIOS_SCRATCH_2); backlight_level = ((bios_2_scratch & ATOM_S2_CURRENT_BL_LEVEL_MASK) >> ATOM_S2_CURRENT_BL_LEVEL_SHIFT); return backlight_level; } -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802834 Title: Dim screen after first boot on Thinkpad A285 Status in linux package in Ubuntu: Confirmed Bug description: We installed the 18.04 daily image on ThinkPad A285, found the screen is dim at the first boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1481 F pulseaudio /dev/snd/controlC0: u 1481 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20MWZ47RUS Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=347498ab-8eae-42d3-a1e3-74e9be6b6ba3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0XET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MWZ47RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0XET30W(1.07):bd09/21/2018:svnLENOVO:pn20MWZ47RUS:pvrThinkPadA285:rvnLENOVO:rn20MWZ47RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad A285 dmi.product.name: 20MWZ47RUS dmi.product.version: ThinkPad A285 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808097] Re: Console got stuck using serial tty after logout
** Description changed: [Impact] - The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. + The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] - The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit link is provided by + The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit is cherry-picked by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6&id=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808097 Title: Console got stuck using serial tty after logout Status in linux package in Ubuntu: Confirmed Bug description: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit is cherry-picked by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6&id=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808097] [NEW] Console got stuck using serial tty after logout
Public bug reported: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit link is provided by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6&id=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Woodrow Shen (woodrow-shen) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Woodrow Shen (woodrow-shen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808097 Title: Console got stuck using serial tty after logout Status in linux package in Ubuntu: Confirmed Bug description: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit link is provided by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6&id=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806666] Re: linux-gcp: 4.15.0-1026.27 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED verification-testing: Testing in progress -- 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/180 Title: linux-gcp: 4.15.0-1026.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530
I can confirm kernel in #34 works for Latitude 5495 which also uses AMDI0011. Please try the kernel out so I can update the driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot
Tested on ThinkPad X240s: ThinkPad BIOS GIET52WW (2.00 ) Lenovo ThinkPad X240s, model 333 Hang issue is not reproduced. Loading i2c_i801 runtime didn't cause any issue. Booting with touchpad in smbus which using i2c_i801 module, Ubuntu 18.04 works fine, touchpad works fine. Log attached. Could you provide more details, like dmesg, call trace when system hang? ** Attachment added: "x240s-boot-i2c-rmi.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802689/+attachment/5221547/+files/x240s-boot-i2c-rmi.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802689 Title: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in kmod source package in Xenial: Fix Committed Status in linux source package in Xenial: Incomplete Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Incomplete Status in kmod source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Incomplete Bug description: After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs on boot. After blacklisting i2c_i801 everything works great again. I realize that this was a fix for bug 1786574, and that helps some other folks out. I'm not sure what the right fix is but there's got to be something that works for everyone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806663] Re: linux-oem: 4.15.0-1030.35 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 12:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing in progress certification-testing: Testing in progress - regression-testing: Testing in progress verification-testing: Testing in progress -- 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/1806663 Title: linux-oem: 4.15.0-1030.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 12:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED verification-testing: Testing in progress -- 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/1806664 Title: linux-aws: 4.15.0-1031.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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-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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806663] Re: linux-oem: 4.15.0-1030.35 -proposed tracker
4.15.0-1030.35 - oem Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - 29 failed on amaura, 25 faile on pepe ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09 (bug 1804594) fanotify10 (bug 1802454) ubuntu_lxc - package from -proposed and from -update casuing apt issue (bug 1805978) xfstests - timed out on ext4 generic/430 test (bug 1755999) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1806663 Title: linux-oem: 4.15.0-1030.35 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 12:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress certification-testing: Testing in progress regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797420] Re: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04
[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/1797420 Title: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04 Status in linux package in Ubuntu: Expired Bug description: In the Linux kernel version 4.15.0-36-generic with the D-Link DWA-121 mini USB WiFi using the rtl8192cu driver on Ubuntu 18.04, it appears that the driver is not controlling the blue LED that blinks when there is download/upload going on, so the LED keeps on. This will cause users of this dongle to open network statistics to see if there is download/upload going on rather than simply looking at the LED. It's time consuming. The driver works fine on Windows, so it's a driver issue. It didn't affect my AP performance. It's just the LED that doesn't blink. - Steps to reproduce: 1. Install Ubuntu 18.04 on a system that has D-Link DWA-121 mini USB WiFi dongle or try it live 2. Look at the statistics light (blue LED) on the dongle. It's not blinking, whether there is download/upload or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-36-generic. ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eofla 1001 F pulseaudio Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0xe000, irq 22' Mixer name : 'Realtek ALC650F' Components : 'AC97a:414c4723' Controls : 62 Simple ctrls : 36 CurrentDesktop: LXDE Date: Thu Oct 11 19:15:25 2018 InstallationDate: Installed on 2018-09-28 (13 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: MSI MS-6712 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e0d9a13c-6776-4241-b61f-164ae076b371 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: irda via_ircc UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6712 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: Uknown Chassis Manufacture dmi.chassis.version: Version 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6712:pvr1.0:rvnMSI:rnMS-6712:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: dmi.product.name: MS-6712 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797369] Re: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetoo
[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/1797369 Title: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: happened before with libnvidia and libreoffice as well, packaes manually removed from status helped temporarily ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-36-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Oct 11 14:29:03 2018 DuplicateSignature: package:linux-modules-extra-4.15.0-36-generic:(not installed) Unpacking linux-modules-extra-4.15.0-36-generic (4.15.0-36.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-1kn4XQ/2-linux-modules-extra-4.15.0-36-generic_4.15.0-36.39_amd64.deb (--unpack): unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-09-10 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: FUJITSU ESPRIMO P957 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=04bd5b82-6066-4b72-8f40-b307ecf4391e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4 RfKill: SourcePackage: linux Title: package linux-modules-extra-4.15.0-36-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-36-generic/kernel/net/bluetooth/bluetooth_6lowpan.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2018 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.18.0 for D3502-A1x dmi.board.name: D3502-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3502-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.18.0forD3502-A1x:bd06/11/2018:svnFUJITSU:pnESPRIMOP957:pvr:rvnFUJITSU:rnD3502-A1:rvrS26361-D3502-A1:cvnFUJITSU:ct3:cvr: dmi.product.family: ESPRIMO-FTS dmi.product.name: ESPRIMO P957 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797086] Re: Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted
[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/1797086 Title: Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted Status in linux package in Ubuntu: Expired Bug description: I am using Ubuntu 18.04.1 LTS, and have set up hard disk encryption during installation. With new automatic software update that installed linux-image-4.15.0-36-generic kernel my password for disk encryption was rejected. The only way I could log in was through choosing the old kernel (linux-image-4.15.0-29-generic) advanced options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797349] Re: GPU hang, full freeze / lockup
[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/1797349 Title: GPU hang, full freeze / lockup Status in linux package in Ubuntu: Expired Bug description: Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830646] [drm] GPU HANG: ecode 9:0:0x85db, in Xorg [1101], reason: Hang on rcs0, action: reset Oct 11 10:48:38 L-UXX0MPSM3 kernel: [10459.830652] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:48:39 L-UXX0MPSM3 kernel: [10460.844423] asynchronous wait on fence i915:kwin_x11[2217]/1:2888a timed out Oct 11 10:48:39 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 91.121.7.182 Oct 11 10:48:40 L-UXX0MPSM3 ntpd[2505]: Soliciting pool server 129.250.35.251 Oct 11 10:48:46 L-UXX0MPSM3 kernel: [10467.788461] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:48:54 L-UXX0MPSM3 kernel: [10475.756465] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:49:02 L-UXX0MPSM3 kernel: [10483.756405] i915 :00:02.0: Resetting rcs0 after gpu hang Oct 11 10:49:02 L-UXX0MPSM3 systemd[1]: Started Getty on tty6. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Received SIGINT. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Timers. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Sound Card. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt upgrade and clean activities. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Disk Manager... Oct 11 10:49:04 L-UXX0MPSM3 obexd[2425]: Terminating Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed" Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper crashed (exit code 15) Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Authentication error: "Process crashed" Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Auth: sddm-helper exited with 15 Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopping... Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Socket server stopped. Oct 11 10:49:04 L-UXX0MPSM3 sddm[1036]: Display server stopping... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Session 2 of user manu. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily Cleanup of Temporary Directories. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for power management... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Daily apt download activities. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Daemon for generating UUIDs... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping User Manager for UID 1002... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup. Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopping ACPI event daemon... Oct 11 10:49:04 L-UXX0MPSM3 systemd[1]: Stopped target Graphical Interface. Oct 11 10:49:04 L-UXX0MPSM3 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="870" x-info="http://www.rsyslog.com";] exiting on signal 15. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Oct 11 10:52:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5062] InstallationDate: Installed on 2018-04-20 (173 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20K5S0T200 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET36W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20K5S0T200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET36W(1.14):bd05/02/2017:svnLENOVO:pn20K5S0T200:pvrThinkPadX270W10DG:rvnLENOVO:rn20K5S
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
@Sebastien, The kernel patches for cosmic and disco already got ack from ubuntu kernel team, and they are enqueued in the next release of kernel. And it is safe to SRU alsa-lib first even without kernel patches. If the kernel doesn't contain those patches, the alsa-lib will work as before, the new added patches for alsa-lib will not introduce any side effect. And after the new alsa-lib is ready, I will build a kernel myself to verify it if the ubuntu formal kernel is not ready. thanks. -- 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/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785464] Re: Computer fails to wake up from sleep, about 10% of attempts
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785464 Title: Computer fails to wake up from sleep, about 10% of attempts Status in linux package in Ubuntu: Confirmed Bug description: About 1 out 10 attempts, my computer fails to wake up from sleep. Instead of waking up, it switches off. It doesn't matter if I wake from power button or keyboard. Looks like this is a recent development, as this worked okay until a few months ago. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: izak 2687 F pulseaudio /dev/snd/controlC1: izak 2687 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 5 11:37:57 2018 HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763 InstallationDate: Installed on 2014-10-24 (1380 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--vg-root ro acpi_enforce_resources=lax quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-27 (99 days ago) dmi.bios.date: 06/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2501:bd06/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume
The patch isn't in upstream Linux though... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769792 Title: Keyboard and Touchpad do not work after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: My laptop is a Toshiba Satellite C850D with updated 18.04 installed. When resuming from suspend, I have no keyboard and touchpad. dmesg shows "i8042: Can't reactivate KBD port" This looks like a recurring problem, and is just like these: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118 Here's the dmesg output from before and after suspending. https://paste.ubuntu.com/p/rsFX9Yw7Xh/ This post also talks about this bit failing for a lot of people! http://lightrush.ndoytchev.com/random-1/i8042quirkoptions Some of the function keys work, such as changing the screen brightness, but the key (fn+F5) does not turn the touchpad back on. I have not yet tried any of the suggested options, as results have been mixed, but I will. 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: Mon May 7 22:01:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.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/ubuntu/+source/linux/+bug/1769792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784585] Re: CPUs stall
Sorry for the late reply. Does this also happen to Disco (19.04) daily image? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784585 Title: CPUs stall Status in linux package in Ubuntu: Confirmed Bug description: Frequently on boot system freezes. Investigation reveals both CPUs stall. Full log attached. It’s a pretty old laptop, but all else seems to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806335] Re: Enable new Realtek card reader
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1806335 Title: Enable new Realtek card reader Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: [Impact] USB Storage based Realtek card reader doesn't work, because the usb-storage module tries to use it in UAS mode instead of using "ums-realtek". [Fix] Add new IDs to ums-realtek driver. In addition to that, we add a new module knob, "enable_mmc=", to enable/disable MMC, as vendors may not pay MMC royalties. "enable_mmc" defaults to 1. [Test] After applying the patch, the card reader works, and verified "enable_mmc=" can enable/disable MMC support. [Regression Potential] Minimal. This SRU enables two specific card readers that don't work as UAS, the new module knob only introduces new behavior when enable_mmc=0. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1806850 Title: Fix Terminus USB hub that may breaks connected USB devices after S3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: [Impact] USB devices connected to Terminus USB hub stop working after S3. [Fix] The Terminus hub seems to have a rather slow reset command, so we need to wait for extra time before doing any further action. [Test] After applying the fix, USB devices connected to the HUB no longer stop functioning after S3. [Regression Potential] Low. Although the fix affects all devices connect to the HUB, it has no functional change other than imposes longer delay time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806395]
Created attachment 279957 dmesg 4.20.0-042000rc6-generic (Many messages from i2c...) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806395 Title: i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.337762] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:19:29 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806397]
Created attachment 279937 dmesg 4.20.0-042000rc6-generic Fix: [ 15.133672] acer_wmi: Acer Laptop ACPI-WMI Extras -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806397 Title: acer_wmi: Unsupported machine has AMW0_GUID1, unable to load Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 17.265418] acer_wmi: Unsupported machine has AMW0_GUID1, unable to load Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:24:35 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806439]
Created attachment 279943 dmesg 4.20.0-042000rc6-generic [1.931641] wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control method not found -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806439 Title: wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control method not found Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390763] wmi_bus wmi_bus-PNP0C14:02: WQBJ data block query control method not found Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:54:51 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806395]
Created attachment 279933 dmesg 4.20.0-042000rc6-generic [1.976160] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (64/65535) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806395 Title: i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.337762] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:19:29 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806436]
Created attachment 279939 dmesg 4.20.0-042000rc6-generic [ 14.569645] hp_accel: laptop model unknown, using default axes configuration [ 14.588059] hp_accel: probe of HPQ6007:00 failed with error -22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806436 Title: hp_accel: probe of HPQ6007:00 failed with error -22 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.386720] hp_accel: probe of HPQ6007:00 failed with error -22 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:42:13 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Testing in progress verification-testing: Testing in progress -- 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/1806673 Title: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker
** Tags added: regression-testing-passed -- 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/1806673 Title: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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 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: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1807339 Title: Add HMS CAN driver for Dell Edge Gateways Status in HWE Next: New Status in linux-oem package in Ubuntu: In Progress Bug description: == Impact == The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 4.15 there's a new release for that. == Fix == Integrate the new release from IHV. == Test Case == Check if the device binds to a driver. == Risk of Regression == The driver binds to certain USB IDs thus should be reasonably low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1807339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1806850 Title: Fix Terminus USB hub that may breaks connected USB devices after S3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: [Impact] USB devices connected to Terminus USB hub stop working after S3. [Fix] The Terminus hub seems to have a rather slow reset command, so we need to wait for extra time before doing any further action. [Test] After applying the fix, USB devices connected to the HUB no longer stop functioning after S3. [Regression Potential] Low. Although the fix affects all devices connect to the HUB, it has no functional change other than imposes longer delay time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807333] Re: Add support for 0cf3:535b QCA_ROME device
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1807333 Title: Add support for 0cf3:535b QCA_ROME device Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: In Progress Bug description: == Impact == 0cf3:535b is not full functioning with the current in-kernel driver. For example, it doesn't work with a BLE keyboard. == Fix == It is a QCA_ROME device. Should mark it so in the device ID table to make it work properly. == Test Case == Try to use this module with a BLE keyboard. It is expected to work without problem, but instead it can't even find the keyboard. == Risk of Regression == Very low. This is already in upstream, and proved working in QA lab. Device info: T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0cf3 ProdID=535b Rev= 0.01 C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1807333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806335] Re: Enable new Realtek card reader
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1806335 Title: Enable new Realtek card reader Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: [Impact] USB Storage based Realtek card reader doesn't work, because the usb-storage module tries to use it in UAS mode instead of using "ums-realtek". [Fix] Add new IDs to ums-realtek driver. In addition to that, we add a new module knob, "enable_mmc=", to enable/disable MMC, as vendors may not pay MMC royalties. "enable_mmc" defaults to 1. [Test] After applying the patch, the card reader works, and verified "enable_mmc=" can enable/disable MMC support. [Regression Potential] Minimal. This SRU enables two specific card readers that don't work as UAS, the new module knob only introduces new behavior when enable_mmc=0. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807342] Re: Add support for Dell DW5821e WWAN/GPS module
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1807342 Title: Add support for Dell DW5821e WWAN/GPS module Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: In Progress Bug description: == Impact == DW5821e doesn't work in Bionic. == Fix == Three commits are required to support it. All of them are already in the mainline kernel. == Test Case == With the command $ sudo mmcli -L the device should be listed as a modem. == Risk of Regression == Very low. it only adds the device ID to the right driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1807342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806015] Re: bcache: performance regression without tuning under bionic
I confirmed that the underlying block devices (SAS, NVME) perform the same on the 4.4 and 4.15 kernels. Roughly 170 IOP/s direct to the SAS device and 570 IOP/s direct to the bcache infront of the SAS device. The block scheduler has no effect, due to the use of O_DIRECT. I can reproduce the sysbench difference in performance on 4.15 versus 4.4. The tuning helps though, only disabling sequential_cutoff really matters as this enables bcache to also cache reads; in general the faster reads allow additional writes. During testing, I believe the core issue we're seeing between 4.4 and 4.15 is around two things: 1) ext4 fs on bionic + enable metadata_csum by default on the filesystems, which will result in additional latency and IO as the csum is calculated and then embedded into the journal 2) fsync performance on 4.15 is measurably slower than on 4.4, even without csum_metadata enabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806015 Title: bcache: performance regression without tuning under bionic Status in linux package in Ubuntu: Confirmed Bug description: Whilst diagnosing a disk performance issue on our QA cloud, I did some performance testing of bcache fronted spindles to compare xenial (4.4 kernel) and bionic (4.14 kernel) installs on the same hardware. A vanilla install (with no tuning of bcache configuration) resulted in the following performance metrics (using the sysbench fileio rndrw benchmark): Xenial 4 threads: 45.77 MiB/sec read 30.52 MiB/sec write 48 threads (matching core count): 138.72 MiB/sec read 92.52 MiB/sec write Bionic 4 threads: 29.51 MiB/sec 19.67 MiB/sec 48 threads (matching core count): 41.35 MiB/sec 27.59 MiB/sec After tuning (disabling the congested_{read|write}_threshold_us and disabling sequential cutoff) Xenial 48 threads (matching core count): 153.60 MiB/sec 102.40 MiB/sec Bionic 48 threads (matching core count): 161.49 MiB/sec 107.67 MiB/sec suggestion is this might be something todo with the move from deadline to cfq as the default IO scheduler between 4.4 and 4.13 but as you can see the baseline vanilla performance is significantly slower. As a further reference point, the IO performance on the NVMe device supporting the bcache device is: 4 threads: 554.56 MiB/sec read 369.71 MiB/sec write ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.39.41 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 29 11:38 seq crw-rw 1 root audio 116, 33 Nov 29 11:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 30 10:11:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.
[Kernel-packages] [Bug 1773897]
I can also reproduce this bug. Notebook: Dell XPS 13 (9370) Wi-Fi/BT module: not sure... bluez: 5.50 BT mouse: logitech M336 (M337) Log: [bluetooth]# paired-devices Device 34:88:5D:92:FC:0C Bluetooth Mouse M336/M337/M535 // try to connect the mouse [bluetooth]# connect 34:88:5D:92:FC:0C Attempting to connect to 34:88:5D:92:FC:0C Failed to connect: org.bluez.Error.Failed // try to connect in discovery mode [bluetooth]# connect 34:88:5D:92:FC:0C Attempting to connect to 34:88:5D:92:FC:0C [CHG] Device 34:88:5D:92:FC:0C Connected: yes [CHG] Device 34:88:5D:92:FC:0C ServicesResolved: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device 34:88:5D:92:FC:0C ServicesResolved: no [CHG] Device 34:88:5D:92:FC:0C Connected: no // moving around the mouse [CHG] Device 34:88:5D:92:FC:0C Connected: yes [CHG] Device 34:88:5D:92:FC:0C Connected: no [CHG] Device 34:88:5D:92:FC:0C Connected: yes [CHG] Device 34:88:5D:92:FC:0C Connected: no [CHG] Device 34:88:5D:92:FC:0C Connected: yes [CHG] Device 34:88:5D:92:FC:0C Connected: no -- 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.7~16.04.1 -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 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Tuesday, 11. December 2018 22:04 UTC reason: - promote-to-proposed: Source package tags missing + promote-to-proposed: Ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Tuesday, 11. December 2018 22:04 UTC reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804149] Remote offloaded syslog file attached for 20181208
--- Comment on attachment From finne...@us.ibm.com 2018-12-11 18:17 EDT--- Remote offloaded syslog file attached for 20181208 Filename: ilabg3.remote.syslog.20181208.txt Dec 8 13:57:50 ilabg3 kernel: [673809.233056] Unable to handle kernel pointer dereference in virtual kernel address space Dec 8 13:57:50 ilabg3 kernel: [673809.233064] Failing address: TEID: 0483 Dec 8 13:57:50 ilabg3 kernel: [673809.233066] Fault in home space mode while using kernel ASCE. Dec 8 13:57:50 ilabg3 kernel: [673809.233069] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d Dec 8 13:57:50 ilabg3 kernel: [673809.233103] Oops: 0004 ilc:3 [#1] SMP ** Attachment added: "Remote offloaded syslog file attached for 20181208" https://bugs.launchpad.net/bugs/1804149/+attachment/5221492/+files/ilabg3.remote.syslog.20181208.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/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363037.322657] [<03ff80272e88>] iscsi_xmit_task+0x48/0x138
[Kernel-packages] [Bug 1804149] syslog.3
--- Comment on attachment From finne...@us.ibm.com 2018-12-11 18:16 EDT--- /var/log/syslog.3, renamed as syslog.ilabg3.3.txt attached ** Attachment added: "syslog.3" https://bugs.launchpad.net/bugs/1804149/+attachment/5221491/+files/syslog.ilabg3.3.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/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363037.322657] [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi] [1363037.322658] [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt Oops output: Oops: 0004 ilc:3 [#1] SMP *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https:/
[Kernel-packages] [Bug 1804149] dmesg.ilabg3.201812081359
--- Comment on attachment From finne...@us.ibm.com 2018-12-11 18:14 EDT--- Ubuntu guest hosted on z/VM 7.1.0 reported another Kernel panic Oops: 0004 ilc:3 [#1] SMP on Dec 8 13:57:50 ilabg3 kernel: [673809.233056] (MST) dmesg.ilabg3.201812081359 attached /var/log/syslog.3, renamed as syslog.ilabg3.3.txt attached Remote offloaded syslog file attached for 20181208 Filename: ilabg3.remote.syslog.20181208.txt root@ilabg3:/var/dump/201812081359# uname -a Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux root@ilabg3:/var/dump/201812081359# ls -l total 151024 -rw--- 1 root root376789 Dec 8 13:59 dmesg.201812081359 -rw--- 1 root root 154267627 Dec 8 13:59 dump.201812081359 root@ilabg3:/var/dump/201812081359# ** Attachment added: "dmesg.ilabg3.201812081359" https://bugs.launchpad.net/bugs/1804149/+attachment/5221490/+files/dmesg.ilabg3.201812081359.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/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Tuesday, 11. December 2018 22:04 UTC reason: - promote-to-proposed: Builds not complete + promote-to-proposed: Source package tags missing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Tuesday, 11. December 2018 22:04 UTC reason: promote-to-proposed: Source package tags missing To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing
Just out of curiosity, who's is using btrfs. It doesn't matter whether you have /home or / on btrfs. I am not certain whether it plays any role, but it seems to be the common denominator in my tests. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722778 Title: System frequently becomes completely unresponsive due to thrashing Status in linux package in Ubuntu: Confirmed Bug description: To replicate: Run firefox for a couple of hours. Expected results: All open applications should run normally: occasional slowdown for page faults are tolerable but the observed behaviour is not. Actual results: Several times per day my computer will become completely unresponsive apart from high hard disk activity. Once it enters this state: it will not recover without a hard reset regardless of any time waited or input given. On one occasion I have tested it by leaving it thrashing for 12 hours, at the end of which there was no evidence of progress. This behaviour was not observed when running Ubuntu 16.04 on the same computer and swap settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jeremy 3367 F...m pulseaudio /dev/snd/controlC0: jeremy 3367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 00:41:01 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6ef78518-5d77-4673-9917-36ed31b247d9 InstallationDate: Installed on 2017-08-15 (56 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 80TV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-12-generic root=UUID=f2087105-8407-42b8-af6c-f00fe6846c51 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-09-14 (27 days ago) dmi.bios.date: 03/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80TV dmi.product.version: Lenovo ideapad 310-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module
After chatting on IRC, #systemd channel, damjan explained this: https://github.com/systemd/systemd/blob/master/NEWS#L845 So, actually, the following file: cat /lib/modprobe.d/systemd.conf disables "extra" dummies, as follows: -- options bonding max_bonds=0 options dummy numdummies=0 -- Forcing us to explicitly create the dummy devices per demand (I believe, and I'll try it soon). I guess that it's really time to say goodbye to "ifupdown / /etc/network/interfaces" approach... Just for testing, after disabling the dummy line out from that file and rebooting it, I have the 12 dummies without my ugly workaround via /etc/rc.local! See, Jan-Dirk? I thought that I could blame systemd and I got my answer there! NOTE: I actually like systemd, okay? :-P It's just a new way of doing this (Netplan? systemd-networkd directly?), Jan, you can safely move to Ubuntu! ^_^ Cheers! ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Invalid Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 - phase: Packaging - phase-changed: Tuesday, 11. December 2018 20:35 UTC + phase: Uploaded + phase-changed: Tuesday, 11. December 2018 22:04 UTC reason: - prepare-package-signed: Package not yet uploaded + promote-to-proposed: Builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Uploaded phase-changed: Tuesday, 11. December 2018 22:04 UTC reason: promote-to-proposed: Builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://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 1807550] Re: kernel bug
Hi Kai Thanks. Unfortunately no change. dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2 w/o firmware' in cold state, will try to load a firmware [ 124.221609] dvb-usb: downloading firmware from file 'dvb-usb-bluebird-02.fw' [ 124.229878] usbcore: registered new interface driver dvb_usb_cxusb [ 124.395307] usb 2-1.1: USB disconnect, device number 5 [ 124.395336] BUG: unable to handle kernel paging request at 2db8 [ 124.395339] PGD 0 P4D 0 [ 124.395342] Oops: [#1] SMP PTI [ 124.395345] CPU: 1 PID: 189 Comm: kworker/1:2 Tainted: G OE 4.18.0-13-generic #14~lp1807550 [ 124.395346] Hardware name: Hewlett-Packard HP EliteBook 8460p/161C, BIOS 68SCF Ver. F.67 02/13/2018 [ 124.395351] Workqueue: usb_hub_wq hub_event [ 124.395355] RIP: 0010:cxusb_disconnect+0x18/0x70 [dvb_usb_cxusb] [ 124.395356] Code: 00 00 00 00 31 c0 5d c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 54 53 48 8b 87 c8 00 00 00 49 89 fc <4c> 8b a8 b8 2d 00 00 49 8b 5d 10 48 85 db 74 18 48 8b 83 a8 00 00 [ 124.395378] RSP: :bd33410ffb60 EFLAGS: 00010246 [ 124.395380] RAX: RBX: 960069d4f430 RCX: [ 124.395381] RDX: RSI: 960069d4f400 RDI: 960069d4f400 [ 124.395382] RBP: bd33410ffb78 R08: R09: 9f12f900 [ 124.395384] R10: bd33410ffb98 R11: 0001 R12: 960069d4f400 [ 124.395385] R13: c0ff70a8 R14: 960069594800 R15: 9600695948a0 [ 124.395386] FS: () GS:96007dc4() knlGS: [ 124.395388] CS: 0010 DS: ES: CR0: 80050033 [ 124.395389] CR2: 2db8 CR3: 8360a002 CR4: 000606e0 [ 124.395390] Call Trace: [ 124.395395] usb_unbind_interface+0x7a/0x270 [ 124.395399] device_release_driver_internal+0x17c/0x260 [ 124.395401] device_release_driver+0x12/0x20 [ 124.395402] bus_remove_device+0xec/0x160 [ 124.395405] device_del+0x13d/0x320 [ 124.395408] ? __dev_printk+0x3c/0x80 [ 124.395409] usb_disable_device+0x9e/0x270 [ 124.395411] usb_disconnect+0x92/0x2a0 [ 124.395413] hub_port_connect+0x80/0xa80 [ 124.395416] hub_event+0x745/0xb30 [ 124.395420] ? __switch_to+0xb2/0x500 [ 124.395423] ? __switch_to_asm+0x40/0x70 [ 124.395426] process_one_work+0x167/0x3f0 [ 124.395429] worker_thread+0x4d/0x460 [ 124.395431] kthread+0x105/0x140 [ 124.395433] ? rescuer_thread+0x360/0x360 [ 124.395435] ? kthread_destroy_worker+0x50/0x50 [ 124.395437] ret_from_fork+0x35/0x40 [ 124.395438] Modules linked in: dvb_usb_cxusb(OE) dib0070(OE) dvb_usb(OE) dvb_core(OE) rc_core(OE) rfcomm ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ccm bnep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic kvm irqbypass gpio_ich snd_hda_intel snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep ghash_clmulni_intel snd_pcm arc4 pcbc aesni_intel aes_x86_64 crypto_simd cryptd uvcvideo(OE) glue_helper intel_cstate intel_rapl_perf videobuf2_vmalloc(OE) videobuf2_memops(OE) videobuf2_v4l2(OE) videobuf2_common(OE) videodev(OE) media(OE) iwldvm mac80211 snd_seq_midi snd_seq_midi_event snd_rawmidi btusb iwlwifi snd_seq btrtl btbcm snd_seq_device [ 124.395471] btintel snd_timer bluetooth joydev snd hp_wmi mei_me input_leds serio_raw ecdh_generic wmi_bmof cfg80211 sparse_keymap soundcore mac_hid mei hp_accel lpc_ich lis3lv02d input_polldev tpm_infineon sunrpc parport_pc ppdev lp parport autofs4 btrfs xor zstd_compress raid6_pq libcrc32c i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse firewire_ohci fb_sys_fops ahci libahci sdhci_pci drm cqhci e1000e firewire_core sdhci crc_itu_t wmi video [ 124.395497] CR2: 2db8 [ 124.395499] ---[ end trace 2d6226ca006f53ac ]--- [ 124.395502] RIP: 0010:cxusb_disconnect+0x18/0x70 [dvb_usb_cxusb] [ 124.395502] Code: 00 00 00 00 31 c0 5d c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 54 53 48 8b 87 c8 00 00 00 49 89 fc <4c> 8b a8 b8 2d 00 00 49 8b 5d 10 48 85 db 74 18 48 8b 83 a8 00 00 [ 124.395524] RSP: :bd33410ffb60 EFLAGS: 00010246 [ 124.395525] RAX: RBX: 960069d4f430 RCX: [ 124.395527] RDX: RSI: 960069d4f400 RDI: 960069d4f400 [ 124.395528] RBP: bd33410ffb78 R08: R09: 9f12f900 [ 124.395529] R10: bd33410ffb98 R11: 0001 R12: 960069d4f400 [ 124.395530] R13: c0ff70a8 R14: 960069594800 R15: 9600695948a0 [ 124.395532] FS: () GS:96007dc4() knlGS: [ 124.395533] CS: 0010 DS: ES: CR0: 80050033 [ 124.395534] CR2: 2db8 CR3: 8360a002 CR4: 000606e0 On 12/10/18 6:28 PM, Kai-Hen
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Joe, is your kernel different than the one Gavin Guo built for us here? https://launchpad.net/~mimi0213kimo/+archive/ubuntu/sf00204509-rcu- backport We have enabled extra debugging and given that kernel to our internal customer who attempting to repro. Since the repro takes a very long time it is difficult to decide when the fix is working or not. Paul McKenney upstream has submitted a pull request for this patch (and others) to go into 4.21. Getting some "burn in" time upstream hasn't really started in earnest yet, but there is no negative discussion about the PR, and I am tempted to get this into the regular based on Paul's comment: "Lock srcu_data structure in srcu_gp_start(), fixing a an extremely rare but also extremely embarrassing concurrency bug, courtesy of Dennis Krein." -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: In Progress Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev&id=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Packaging - phase-changed: Tuesday, 11. December 2018 20:03 UTC + phase-changed: Tuesday, 11. December 2018 20:35 UTC reason: - prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet 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/1807982 Title: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: 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 package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Packaging phase-changed: Tuesday, 11. December 2018 20:35 UTC reason: prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
This bug was fixed in the package hwdata - 0.249-1ubuntu1 --- hwdata (0.249-1ubuntu1) trusty; urgency=medium * Change PNP vendor name for GSM to LG Electronics (LP: #1755490) -- Dariusz Gadomski Thu, 29 Nov 2018 17:17:30 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Released Status in hwdata source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
This bug was fixed in the package gnome-desktop3 - 3.8.4-0ubuntu3.3 --- gnome-desktop3 (3.8.4-0ubuntu3.3) trusty; urgency=medium * libgnome-desktop/display-name.c - some vendors encode the screen ratio (e.g 16/9) in the EDID instead of including the screen size, detect those cases and display the product name instead of the screen diagonal. (lp: #1755490) -- Dariusz Gadomski Fri, 30 Nov 2018 08:27:43 +0100 ** Changed in: gnome-desktop3 (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: hwdata (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Released Status in hwdata source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807608]
Created attachment 279927 dmesg 4.20.0-042000rc6-generic (restart) I do not know what happens. But now it works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807608 Title: Not work Bluetooth Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, I'm working with linux 4.19, and not work bluetooth. Not problem with linux 4.18.20. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2718 F pulseaudio /dev/snd/pcmC0D0p: caravena 2718 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 9 15:29:31 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (6 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Packaging - phase-changed: Tuesday, 11. December 2018 16:06 UTC + phase-changed: Tuesday, 11. December 2018 20:03 UTC reason: - prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet 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/1807982 Title: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Packaging phase-changed: Tuesday, 11. December 2018 20:03 UTC reason: prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807406]
Created attachment 279953 dmesg 4.20.0-042000rc6-generic [2.641261] hid-generic 001F:8086:22D8.0003: hidraw2: HID v2.00 Device [hid-ishtp 8086:22D8] on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807406 Title: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, Message after returning from suspension dmesg: [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for response from ISHTP device Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 12:02:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I sent you my hacked acpi tables, why don't you use them? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu
While the latest kernels do at least work in some form they aren't quite right. The sensitivity doesn't respond to the GUI settings. Also after some time the touchpad stops responding. Sometimes it recovers others it does not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781879 Title: Latest ASUS trackpad doesn't work in Ubuntu Status in Linux: In Progress Status in linux package in Ubuntu: Confirmed Bug description: It seems there might be a new hardware variant of the elan trackpad in the newer ASUS machines. The issue is the shown here with some reasonably deep investigation. Is this something that I can do or am I reduced to having to find out a mouse if I want to use Linux? https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/ user@TUF-GAMING-FX504GD-FX80GD:~$ xinput Virtual core pointer id=2[master pointer (3)] ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ↳ Logitech USB Receiver id=12 [slave pointer (2)] ↳ Logitech USB Receiver id=13 [slave pointer (2)] Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)] ↳ Asus WMI hotkeys id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1781879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807869] Re: ubuntu_nbd_smoke_test failed with Xenial
@Sam, can you give this fix a test? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807869 Title: ubuntu_nbd_smoke_test failed with Xenial Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Spotted in this cycle with node: * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/ * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/ * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/ Error log from kernel01: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-22282 Date: Mon Dec 10 05:22:47 EST 2018 Host: kernel01 Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 641567 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 6.2G 187M 98% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 3.1G 17G 17% /home testpool.3622624G 128K 24G 1% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 128K 24G 1% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 128K 24G 1% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 128K 24G 1% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 128K 24G 1% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd NBD device /dev/nbd0 created found nbd export NBD exports found: test starting clien with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 failed unmounting /mnt/nbd-test-22282 stopping client disconnect, sock, done killing server stderr: bs=1024, sz=134217728 bytes timeout=30 umount: /mnt/nbd-test-22282: mountpoint not found ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Dec 11 04:08:37 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M nobp=1 BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-141-generic N/A linux-backports-modules-4.4.0-141-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1807869/+
[Kernel-packages] [Bug 1807869] Re: ubuntu_nbd_smoke_test failed with Xenial
Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=42e9d7328c470d0e6599289db16085e4b9261271 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807869 Title: ubuntu_nbd_smoke_test failed with Xenial Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Spotted in this cycle with node: * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/ * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/ * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/ Error log from kernel01: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-22282 Date: Mon Dec 10 05:22:47 EST 2018 Host: kernel01 Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 641567 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 6.2G 187M 98% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 3.1G 17G 17% /home testpool.3622624G 128K 24G 1% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 128K 24G 1% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 128K 24G 1% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 128K 24G 1% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 128K 24G 1% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd NBD device /dev/nbd0 created found nbd export NBD exports found: test starting clien with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 failed unmounting /mnt/nbd-test-22282 stopping client disconnect, sock, done killing server stderr: bs=1024, sz=134217728 bytes timeout=30 umount: /mnt/nbd-test-22282: mountpoint not found ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Dec 11 04:08:37 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M nobp=1 BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-141-generic N/A linux-backports-modules-4.4.0-141-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux
[Kernel-packages] [Bug 1806649]
Created attachment 279945 dmesg 4.20.0-042000rc6-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/1806649 Title: Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2784 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 07:41:10 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806649]
Not work with linux 4.20-rc6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806649 Title: Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2784 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 07:41:10 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806682]
Created attachment 279947 dmesg 4.20.0-042000rc6-generic [1.654074] ACPI: Invalid passive threshold -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806437]
Created attachment 279941 dmesg 4.20.0-042000rc6-generic [1.931623] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.390738] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio /dev/snd/pcmC0D0p: caravena 2769 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 12:49:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806863]
Created attachment 279951 dmesg 4.20.0-042000rc6-generic [1.949949] i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using dummy regulator [1.949957] i2c_hid i2c-ELAN2514:00: Linked as a consumer to regulator.0 [1.949958] i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vddl not found, using dummy regulator [1.976160] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (64/65535) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806863 Title: i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using dummy regulator Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [1.685824] i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using dummy regulator Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2809 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 5 08:19:35 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (2 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco
Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=30d50ff103fa914a349413de5002a1a53390c9a3 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807341 Title: ubuntu_squashfs_smoke_test failed with Disco Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Tested on a KVM node with generic kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh Testing with compression method gzip Testing mount of squashfs: PASSED (gzip) Testing umount of squashfs: PASSED (gzip) Checking data integrity: FAILED (squashed /bin different from original /bin, gzip) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 07:39 seq crw-rw 1 root audio 116, 33 Dec 7 07:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Dec 7 07:44:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1807341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
** Changed in: linux (Ubuntu) Importance: Critical => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Critical => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Critical => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling
** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => 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/1788549 Title: powerpc/powernv/pci: Work around races in PCI bridge enabling Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: == Comment: #0 - Michael Ranweiler - 2018-08-21 13:52:03 == +++ This bug was initially created as a clone of Bug #170766 +++ Please apply the following kernel patch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=db2173198b9513f7add8009f225afa1f1c79bcc6 powerpc/powernv/pci: Work around races in PCI bridge enabling The generic code is racy when multiple children of a PCI bridge try to enable it simultaneously. This leads to drivers trying to access a device through a not-yet-enabled bridge, and this EEH errors under various circumstances when using parallel driver probing. There is work going on to fix that properly in the PCI core but it will take some time. x86 gets away with it because (outside of hotplug), the BIOS enables all the bridges at boot time. This patch does the same thing on powernv by enabling all bridges that have child devices at boot time, thus avoiding subsequent races. It's suitable for backporting to stable and distros, while the proper PCI fix will probably be significantly more invasive. Signed-off-by: Benjamin Herrenschmidt Cc: sta...@vger.kernel.org Signed-off-by: Michael Ellerman == Comment: #2 - Michael Ranweiler - 2018-08-21 18:23:35 == This has some fuzz and also move it back from the pci macro to dev_err so we'll attach the backported patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco
@Sam, do you mind retesting this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807341 Title: ubuntu_squashfs_smoke_test failed with Disco Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Tested on a KVM node with generic kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh Testing with compression method gzip Testing mount of squashfs: PASSED (gzip) Testing umount of squashfs: PASSED (gzip) Checking data integrity: FAILED (squashed /bin different from original /bin, gzip) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 07:39 seq crw-rw 1 root audio 116, 33 Dec 7 07:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Dec 7 07:44:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1807341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807869] Re: ubuntu_nbd_smoke_test failed with Xenial
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: ubuntu-kernel-tests Importance: Undecided => High ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807869 Title: ubuntu_nbd_smoke_test failed with Xenial Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Bug description: Spotted in this cycle with node: * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/ * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/ * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/ Error log from kernel01: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-22282 Date: Mon Dec 10 05:22:47 EST 2018 Host: kernel01 Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018 Machine: kernel01 s390x s390x CPUs online: 8 CPUs total:8 Page size: 4096 Pages avail: 641567 Pages total: 977383 Free space: Filesystem Size Used Avail Use% Mounted on udev 1.9G 0 1.9G 0% /dev tmpfs382M 39M 344M 11% /run /dev/dasda1 6.7G 6.2G 187M 98% / tmpfs1.9G 4.0K 1.9G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/datavg-home 21G 3.1G 17G 17% /home testpool.3622624G 128K 24G 1% /testpool.36226 testpool.36226/testfs.36226 24G 128K 24G 1% /var/tmp/testdir36226 testpool.36226/testfs.36226/clone 24G 128K 24G 1% /var/tmp/testdir36226/clone testpool.36226/testfs.36226/renameme 24G 128K 24G 1% /var/tmp/testdir36226/renameme testpool.36226/testfs.36226/shared24G 128K 24G 1% /var/tmp/testdir36226/shared testpool.36226/testfs.36226/testfs2.36226 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226 testpool.36226/testfs.36226/testfs2.36226.unmounted 24G 128K 24G 1% /var/tmp/testdir36226/testfs2.36226.unmounted testpool.36226/testfs.36226/unshared 24G 128K 24G 1% /var/tmp/testdir36226/unshared tmpfs382M 0 382M 0% /run/user/1000 tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd NBD device /dev/nbd0 created found nbd export NBD exports found: test starting clien with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 failed unmounting /mnt/nbd-test-22282 stopping client disconnect, sock, done killing server stderr: bs=1024, sz=134217728 bytes timeout=30 umount: /mnt/nbd-test-22282: mountpoint not found ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Dec 11 04:08:37 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M nobp=1 BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-141-generic N/A linux-backports-modules-4.4.0-141-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!
I'm also seeing this occur on 18.10. These are some logs in my `/var/log/syslog` around the time of the crash: ** Attachment added: "var-log-syslog-sample.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730331/+attachment/5221406/+files/var-log-syslog-sample.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1730331 Title: ath10k_pci: firmware crashed! Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware package in Fedora: Unknown Bug description: ... Nov 4 18:35:50 akane kernel: [ 10.216896] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 10.216908] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 10.217641] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 10.228600] kvm: Nested Virtualization enabled Nov 4 18:35:50 akane kernel: [ 10.228611] kvm: Nested Paging enabled Nov 4 18:35:50 akane kernel: [ 10.258913] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 10.263535] MCE: In-kernel MCE decoding enabled. Nov 4 18:35:50 akane kernel: [ 10.271401] EDAC amd64: Node 0: DRAM ECC enabled. Nov 4 18:35:50 akane kernel: [ 10.271416] EDAC amd64: F16h_M30h detected (node 0). Nov 4 18:35:50 akane kernel: [ 10.271491] EDAC MC: DCT0 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271494] EDAC amd64: MC: 0: 4096MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271523] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271526] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271528] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271530] EDAC MC: DCT1 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271532] EDAC amd64: MC: 0: 0MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271534] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271537] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271539] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271541] EDAC amd64: using x4 syndromes. Nov 4 18:35:50 akane kernel: [ 10.271542] EDAC amd64: MCT channel count: 1 Nov 4 18:35:50 akane kernel: [ 10.271829] EDAC MC0: Giving out device to module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT) Nov 4 18:35:50 akane kernel: [ 10.271892] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED) Nov 4 18:35:50 akane kernel: [ 10.271894] AMD64 EDAC driver v3.5.0 Nov 4 18:35:50 akane kernel: [ 10.532131] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 10.575859] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 11.397803] ath10k_pci :04:00.0: firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa) Nov 4 18:35:50 akane kernel: [ 11.407389] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 11.407395] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 11.408085] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 11.408148] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 11.408156] ath10k_pci :04:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 Nov 4 18:35:50 akane kernel: [ 11.410197] ath10k_pci :04:00.0: firmware register dump: Nov 4 18:35:50 akane kernel: [ 11.416213] ath10k_pci :04:00.0: [00]: 0x4100016C 0x15B3 0x009BFF84 0x00955B31 Nov 4 18:35:50 akane kernel: [ 11.424559] ath10k_pci :04:00.0: [04]: 0x009BFF84 0x00060130 0x0013 0x Nov 4 18:35:50 akane kernel: [ 11.432767] ath10k_pci :04:00.0: [08]: 0x009C8EA4 0x7170 0x0001 0x00435300 Nov 4 18:35:50 akane kernel: [ 11.441059] ath10k_pci :04:00.0: [12]: 0x0009 0x 0x00958360 0x0095836B Nov 4 18:35:50 akane kernel: [ 11.449397] ath10k_pci :04:00.0: [16]: 0x00958080 0x0094078E 0x 0x Nov 4 18:35:50 akane kernel: [ 11.457686] ath10k_pci :04:00.0: [20]: 0x409BFF84 0x0040AB44 0x004101E0 0x000C Nov 4 18:35:50 akane kernel: [ 11.466132] ath10k_pci
[Kernel-packages] [Bug 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.6 --- libvirt (4.0.0-1ubuntu8.6) bionic; urgency=medium * d/control: explicitly Build-dep on libwiretap-dev to fix FTBFS since libwireshark 2.6.x SRU upload (LP: #1801666) * debian/patches/ubuntu/lp1787405-*: Support guest dedicated Crypto Adapters on s390x (LP: #1787405) -- Christian Ehrhardt Fri, 09 Nov 2018 07:42:01 +0100 ** Changed in: libvirt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787405 Title: [FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Fix Committed Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in qemu source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] * The ability to pass through more cryptographic capabilities is a very important feature for users of s390x as virtualization platform. Its availability upstream now and its backport in this bug allows to exploit the crypto cards as new HW for these virtualization use cases. * This falls under both "other safe cases" SRU exceptions: - For Long Term Support releases we regularly want to enable new hardware ... - For Long Term Support releases we sometimes want to introduce new features. They must not change the behaviour on existing installations ... * This bug has three main components: - kernel (ability to do all of this) - qemu (add feature to exploit the new code) - libvirt (make the feature user consumable) [Test Case] * In general this consists of a few steps - get the updated kernel/qemu/libvirt - mask the card & domains from the usual driver - load vfio-ap - assign card&domain to vfio-ap - prepare a guest - configure a guest to use the card * See comment #66 how to do all of that in detail https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/66 [Regression Potential] * The changes are mostly s390x only and adding a new feature so regressions to existing components should be low. But to backport it slight changes to the MDEV handling had to be applied as well. The potential regressions I can see are in that MDEV handling if one of the backports would be bad. Fortunately we know that without the related libvirt fixes we added here using MDEVs didn't work at all yet, and people very rarely use qemu without libvirt for anything else than experiments. Therefore I'm confident that even if there would be a flaw in the MDEV changes no one is hugely relying on it. [Other Info] * n/a == SRU Justification == (Kernel SRU) Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. (Since all kernel patches/commits are from kernel 4.19, they will automagically land in 'Disco'.) == Fix == 9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit") 3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART") e585b24 ("KVM: s390: refactor crypto initialization") 1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver") 65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework") 96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters") 3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains") 3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains") 81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix") 4210459 ("KVM: s390: interface to clear CRYCB masks") 258287c ("s390: vfio-ap: implement mediated device open callback") e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl") 46a7263 ("s390: vfio-ap: zeroize the AP queues") cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl") 6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE") d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first") 3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear") 56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2") 19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1") 6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0") c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1") 6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 C
[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
I'm getting exactly this issue. An ATI RX 480 on Kubuntu 18.04 with a ASUS MG28U on HDMI-1. It is on a 5m cable so using the displayport wasn't an option. The long HDMI cable is to allow the large system box to be away from my desk. I mostly use the system as a web and data server and it is stuffed with hard drives. Works perfectly on 4.13 kernels. Fails on the 4.15 kernels before the sddm login screen. 4.15.0-43-generic <-- screen repeats HDMI no signal 4.15.0-42-generic <-- screen repeats HDMI no signal 4.15.0-35-generic <-- screen repeats HDMI no signal 4.13.0-36-generic <-- ok On 4.13 kernels it runs the screen at 3840x2160 @ 30Hz. On 4.15 kernels it doesn't. At a guess looking at the syslog, the 4.13 fell back to 30Hz at the hi- res while the 4.15 does not. Over the long cable the screen isn't detecting the screen at 60Hz. Hope that helps. I may have to look at getting a longer active cable... ** Attachment added: "syslog_fragment_4.15.0.43.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+attachment/5221404/+files/syslog_fragment_4.15.0.43.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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
anything is better than Windows 10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco
Thanks for the analysis Seth, I'll fix that up. ** Changed in: ubuntu-kernel-tests Importance: Undecided => High ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807341 Title: ubuntu_squashfs_smoke_test failed with Disco Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Bug description: Tested on a KVM node with generic kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh Testing with compression method gzip Testing mount of squashfs: PASSED (gzip) Testing umount of squashfs: PASSED (gzip) Checking data integrity: FAILED (squashed /bin different from original /bin, gzip) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 07:39 seq crw-rw 1 root audio 116, 33 Dec 7 07:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Dec 7 07:44:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1807341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787405] Update Released
The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any 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/1787405 Title: [FEAT] Guest-dedicated Crypto Adapters Status in Ubuntu on IBM z Systems: Fix Committed Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in qemu source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] * The ability to pass through more cryptographic capabilities is a very important feature for users of s390x as virtualization platform. Its availability upstream now and its backport in this bug allows to exploit the crypto cards as new HW for these virtualization use cases. * This falls under both "other safe cases" SRU exceptions: - For Long Term Support releases we regularly want to enable new hardware ... - For Long Term Support releases we sometimes want to introduce new features. They must not change the behaviour on existing installations ... * This bug has three main components: - kernel (ability to do all of this) - qemu (add feature to exploit the new code) - libvirt (make the feature user consumable) [Test Case] * In general this consists of a few steps - get the updated kernel/qemu/libvirt - mask the card & domains from the usual driver - load vfio-ap - assign card&domain to vfio-ap - prepare a guest - configure a guest to use the card * See comment #66 how to do all of that in detail https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/66 [Regression Potential] * The changes are mostly s390x only and adding a new feature so regressions to existing components should be low. But to backport it slight changes to the MDEV handling had to be applied as well. The potential regressions I can see are in that MDEV handling if one of the backports would be bad. Fortunately we know that without the related libvirt fixes we added here using MDEVs didn't work at all yet, and people very rarely use qemu without libvirt for anything else than experiments. Therefore I'm confident that even if there would be a flaw in the MDEV changes no one is hugely relying on it. [Other Info] * n/a == SRU Justification == (Kernel SRU) Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to a KVM guest such that the hypervisor cannot observe the communication of the guest with the device. (Since all kernel patches/commits are from kernel 4.19, they will automagically land in 'Disco'.) == Fix == 9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit") 3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART") e585b24 ("KVM: s390: refactor crypto initialization") 1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver") 65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework") 96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters") 3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains") 3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains") 81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix") 4210459 ("KVM: s390: interface to clear CRYCB masks") 258287c ("s390: vfio-ap: implement mediated device open callback") e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl") 46a7263 ("s390: vfio-ap: zeroize the AP queues") cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl") 6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE") d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first") 3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear") 56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2") 19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1") 6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0") c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1") 6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2") 9ee71f2 ("K
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 + phase: Packaging + phase-changed: Tuesday, 11. December 2018 16:06 UTC + reason: + prepare-package: Package not yet uploaded + prepare-package-meta: Package not yet uploaded + prepare-package-signed: Package not yet 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/1807982 Title: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 phase: Packaging phase-changed: Tuesday, 11. December 2018 16:06 UTC reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco
This is a test issue, likely that the test was broken by a change in userspace. The test creates a squashfs using /bin as the source. In disco this is a link to usr/bin, so the created squashfs contains a single file /bin which is also a symlink to usr/bin. Since this is a relative symlink and usr/bin doesn't exist in the squashfs, the attempt to diff the contents of /bin and $SQUASHFS_MNT/bin finds many differences, causing the test to fail. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807341 Title: ubuntu_squashfs_smoke_test failed with Disco Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Tested on a KVM node with generic kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh Testing with compression method gzip Testing mount of squashfs: PASSED (gzip) Testing umount of squashfs: PASSED (gzip) Checking data integrity: FAILED (squashed /bin different from original /bin, gzip) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 07:39 seq crw-rw 1 root audio 116, 33 Dec 7 07:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Dec 7 07:44:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1807341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800649] Re: Add support for NVIDIA GPU passthrough
** Changed in: qemu (Ubuntu) Status: Incomplete => 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/1800649 Title: Add support for NVIDIA GPU passthrough Status in linux package in Ubuntu: Won't Fix Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Won't Fix Bug description: This bug will keep track of an important feature that is being developed upstream and need to be backported to Ubuntu 18.04 PPC64. The feature allows QEMU/KVM guests to have NVIDIA GPUs passed-through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806396]
Created attachment 279935 dmesg 4.20.0-042000rc6-generic [ 14.588039] lis3lv02d: unknown sensor type 0x0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806396 Title: lis3lv02d: unknown sensor type 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 15.684425] lis3lv02d: unknown sensor type 0x0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:22:33 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** 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) => Marcelo Cerri (mhcerri) ** 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) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807982 Title: linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: linux packages should own /usr/lib/linux/triggers
dpkg --contents linux-image-unsigned-4.15.0-43-generic_4.15.0-43.46_amd64.deb |grep trigger drwxr-xr-x root/root 0 2018-12-06 14:52 ./usr/lib/linux/triggers/ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770256 Title: linux packages should own /usr/lib/linux/triggers Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: 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 1807982] [NEW] linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
Public bug reported: This bug is for tracking the 4.15.0-1007.7~16.04.1 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: 1806659 ** 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: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** 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/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 (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.12.03-1 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: xenial ** 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/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/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel
[Kernel-packages] [Bug 1770256] Re: linux packages should own /usr/lib/linux/triggers
dpkg --contents linux-image-unsigned-4.18.0-13-generic_4.18.0-13.14_amd64.deb |grep trigger drwxr-xr-x root/root 0 2018-12-05 06:10 ./usr/lib/linux/triggers/ ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You 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 Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: 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 1800649] Re: Add support for NVIDIA GPU passthrough
Add support for NVIDIA GPU passthrough Is this just a duplicate of LP 1800649? (Now coming in via the ubuntu-power-system project.) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649 or is it meant to be the libvirt part of LP 1800649, or is this a request to move this feature over from the custom to the generic package(s)? Please provide some more details - thx. --- Comment From mranw...@us.ibm.com 2018-12-10 10:15 EDT--- This is a dup of 1800649, it was meant to create an IBM side mirror it instead of a new bug. I'm not sure why it's that way, but asked if we can get it fixed. ** Tags added: architecture-ppc64le bugnameltc-173957 severity-medium targetmilestone-inin1804 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800649 Title: Add support for NVIDIA GPU passthrough Status in linux package in Ubuntu: Won't Fix Status in qemu package in Ubuntu: Incomplete Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Won't Fix Bug description: This bug will keep track of an important feature that is being developed upstream and need to be backported to Ubuntu 18.04 PPC64. The feature allows QEMU/KVM guests to have NVIDIA GPUs passed-through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806430] Re: linux: 3.2.0-139.185 -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 backports: derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - verification-testing: Testing 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/1806430 Title: linux: 3.2.0-139.185 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: Invalid 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: derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
@Hui, could you give some details here on what's the status of the kernel patches. Are they in cosmic and/or disco yet? Do we need to block the alsa SRU on those bits to land to be able to verify the change works? -- 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/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -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: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff - verification-testing: Testing 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/1806670 Title: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574196] Re: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number.
Happening to me too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1574196 Title: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number. Status in bcmwl package in Ubuntu: Confirmed Bug description: The card Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) doesn't see 5Ghz networks with an high channel number, if you change the channel back to a lower one the network will be found again. In my case with channel 104 the network wasn't seen by the card, with channel 40 it works fine wireless-info script result: ## wireless info START ## Report from: 22 Apr 2016 19:23 CEST +0200 Booted last: 22 Apr 2016 18:51 CEST +0200 Script from: 27 Sep 2015 00:34 UTC + # release ### Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty # kernel Linux 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, quiet, splash, vt.handoff=7 # desktop ### Ubuntu # lspci # 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7758] Kernel driver in use: r8169 04:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) Subsystem: Broadcom Corporation Device [14e4:0619] Kernel driver in use: wl # lsusb # Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 004: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse Bus 001 Device 003: ID 258a:0001 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA card info ## # rfkill 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no # lsmod # wl 6367819 0 mxm_wmi13021 1 nouveau wmi19177 2 mxm_wmi,nouveau cfg80211 496328 1 wl # interfaces auto lo iface lo inet loopback # ifconfig ## eth0 Link encap:Ethernet HWaddr UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0Link encap:Ethernet HWaddr inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan2 Link encap:Ethernet HWaddr inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:45040 errors:0 dropped:0 overruns:0 frame:7469 TX packets:33232 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:33581962 (33.5 MB) TX bytes:6334838 (6.3 MB) Interrupt:18 # iwconfig ## eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. wlan2 IEEE 802.11abg ESSID:"LamerTexWiFi" Mode:Managed Frequency:2.437 GHz Access Point: Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off # route # Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 00 wlan2 192.168.1.0 0.0.0.0 255.255.255.0 U 9 00 wlan2 192.168.122.0 0.0.0.0 255.255.255.0 U 0 00 virbr0 # resol
[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic
Prepped for Bionic and Cosmic in a PPA [1] for Bileto ticket [2] Depending autopkgtests queued. I'll run usual virtualization regression checks on that over night and into tomorrow. MPs are up for review at [3][4], but since Andeas change applies on all these as-is there isn't much difference. The biggest blocker here si the lack of a more clearly outlined testcase. @Andres/@Vern - can you help to fill the testcase steps in the SRU template? [1]: https://bileto.ubuntu.com/#/ticket/3560 [2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3560/+packages [3]: https://code.launchpad.net/~paelzer/ubuntu/+source/ipxe/+git/ipxe/+merge/360678 [4]: https://code.launchpad.net/~paelzer/ubuntu/+source/ipxe/+git/ipxe/+merge/360679 ** Description changed: + [Impact] + + * VLAN 0 is special (for QoS actually, not a real VLAN) + * Some components in the stack accidentially strip it, so does ipxe in +this case. + * Fix by porting a fix that is carried by other distributions as upstrem +didn't follow the sugegstion but it is needed for the use case affected +by the bug here (Thanks Andres) + + [Test Case] + + * TODO + + [Regression Potential] + + * The onyl refernce to VLAN tags on iPXE boto that we found was on iBFT +boot for SCSI, we tested that in comment #34 and it still worked fine. + * We didn't see such cases on reivew, but there might be use cases that +made some unexpected use of the headers which are now stripped. But +that seems wrong. + + + [Other Info] + + * n/a + + --- + + I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. ** Description changed: [Impact] - * VLAN 0 is special (for QoS actually, not a real VLAN) - * Some components in the stack accidentially strip it, so does ipxe in -this case. - * Fix by porting a fix that is carried by other distributions as upstrem -didn't follow the sugegstion but it is needed for the use case affected -by the bug here (Thanks Andres) + * VLAN 0 is special (for QoS actually, not a real VLAN) + * Some components in the stack accidentally strip it, so does ipxe in + this case. + * Fix by porting a fix that is carried by other distributions as upstream + didn't follow the suggestion but it is needed for the use case affected + by the bug here (Thanks Andres) [Test Case] - * TODO + * TODO [Regression Potential] - * The onyl refernce to VLAN tags on iPXE boto that we found was on iBFT -boot for SCSI, we tested that in comment #34 and it still worked fine. - * We didn't see such cases on reivew, but there might be use cases that -made some unexpected use of the headers which are now stripped. But -that seems wrong. - + * The only reference to VLAN tags on i
[Kernel-packages] [Bug 1806430] Re: linux: 3.2.0-139.185 -proposed tracker
** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806430 Title: linux: 3.2.0-139.185 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: Invalid 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: derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker
All bugs either verified in Bionic or by packaging review. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- 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/1806670 Title: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 11:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/ipxe/+git/ipxe/+merge/360678 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/ipxe/+git/ipxe/+merge/360679 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in ipxe-qemu-256k-compat package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in ipxe source package in Trusty: Won't Fix Status in ipxe source package in Xenial: Won't Fix Status in ipxe source package in Bionic: Triaged Status in ipxe source package in Cosmic: Triaged Status in ipxe source package in Disco: Fix Released Bug description: I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807974] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807974 Title: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell XPS 13 9370 developer edition (Ubuntu version) running Cosmic. A handful of times per day, my wireless stops working ("?" appears in the icon in Network Manager). Turning wireless off and then on again, or suspending and waking the machine up, makes the wireless work again. dmesg output is as follows: $ dmesg | grep ath10k [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 6317c652-4817-4fdd-b6d7-c7b8336e493f) [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 6646.270369] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump: [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3 [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107 [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19 [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8 [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103 [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6 [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1 [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809 [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118 [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 03393f2f-0ce1-4017-b711-40dd14f2ec11) [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [17641.848065] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [17641.860595] ath10k_pci :02:00.0: Copy Engine register dump: [17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3 [17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244 [17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52 [17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105 [17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30 [17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1 [17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809 [17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118 [17642.835601] ath10k_pci :02:00.0: device successfully recovered [17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809 [17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118 I do not recall having any wireless issues before I upgraded (when this machine was running Bionic). Bug #1730331 - ath10k_pci: firmware crashed! Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10] could be related, but appear to be related to earlier releases, whereas my issue has appeared/become much worse on Cosmic. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
[Kernel-packages] [Bug 1806570] Re: linux-aws: 4.4.0-1037.40 -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: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Testing in progress + promote-to-security: Master bug not ready for release + promote-to-updates: Master bug not ready for release -- 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/1806570 Title: linux-aws: 4.4.0-1037.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806578] Re: linux-kvm: 4.4.0-1039.45 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - verification-testing: Testing in progress -- 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/1806578 Title: linux-kvm: 4.4.0-1039.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp