[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Is there even anyone out there with disco dingo AND a functioning kernel with an nvidia driver? But of course if someone did, they wouldn't be here. "I've tried nothing and I'm all out of ideas, man!" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic Status in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in The Bionic Beaver: Confirmed Status in linux source package in Bionic: Fix Released Bug description: This was the last OK then my 18.04 hangs after an update this morning. 07:00 AM CEST Last Ok in boot was Started gnome display manager. dispatcher service .. tem changes.pp link was shut down Tried install lightdm from command line and the response was lastest already installed. Probably it is what is coming after the lastest OK which is to be the error. And here I have lots of guesses.. Any Ideas ? I need to do some work and I may not be waiting long. Search and browsed and now close to give up. Yeah it is a Lenovo. Guys: turn of auto update it is a machine killer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826348] Re: linux-oracle: 4.15.0-1012.14 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826346 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1826358 - phase: Ready for Packaging - phase-changed: Thursday, 25. April 2019 10:40 UTC + phase: Packaging + phase-changed: Friday, 26. April 2019 04:39 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1826348 Title: linux-oracle: 4.15.0-1012.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826346 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1826358 phase: Packaging phase-changed: Friday, 26. April 2019 04:39 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826348] Re: linux-oracle: 4.15.0-1012.14 -proposed tracker
** Summary changed: - linux-oracle: -proposed tracker + linux-oracle: 4.15.0-1012.14 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1826348 Title: linux-oracle: 4.15.0-1012.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826346 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1826358 phase: Ready for Packaging phase-changed: Thursday, 25. April 2019 10:40 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817817] Re: To add power setting bin file for SAR support (QCA6174)
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1817817 Title: To add power setting bin file for SAR support (QCA6174) Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Cosmic: Fix Released Bug description: [Impact] To meet the policy requirement of the RF radiation, we need to reduce the power of the device. [Fix] Qualcomm provides a new firmware for this. 97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin [Test] We can't verify it. [Regression Potential] Low, it's a fix from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823994] Re: arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
I am still seeing this issue on ARM64 nodes for the SRU triggered yesterday: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.13.69) but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823994 Title: arm64: not able to install linux-generic-hwe-18.04-edge/bionic- proposed Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-hwe-edge source package in Bionic: Fix Committed Bug description: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.8.66) but 4.18.0.16.65 is to be installed E: Unable to correct problems, you have held broken packages. ``` 5. same happens trying to install `linux-image-generic-hwe-18.04-edge`: ``` $ sudo apt install linux-image-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but it is not installable E: Unable to correct problems, you have held broken packages. ``` 6. also not able to install `linux-image-5.0.0-8-generic`: ``` $ sudo apt install linux-image-5.0.0-8-generic Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image-5.0.0-8-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-image-5.0.0-8-generic' has no installation candidate ``` more info: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ~$ apt-cache policy linux-generic-hwe-18.04-edge linux-generic-hwe-18.04-edge: Installed: 4.18.0.16.65 Candidate: 5.0.0.8.66 Version table: 5.0.0.8.66 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 4.18.0.16.65 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826274] Re: Headset keeps disconnecting after upgrade to Disco
The bluez version hasn't changed (in any meaningful way) between cosmic and disco. So I don't think that's the cause. Also, those log messages are from the kernel. Can you please try downgrading your kernel to something more like cosmic (4.18) and tell us which versions do or don't have the bug? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Tags added: a2dp ** Tags added: disco regression-release ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1826274 Title: Headset keeps disconnecting after upgrade to Disco Status in linux package in Ubuntu: Incomplete Bug description: I'm using Bose QC35 headset and Dell XPS 9570 laptop. It was working perfectly on Cosmic, after upgrade to Disco when headsed is switched to HSP/HFP mode in pavucontrol I'm getting bursts of following messages in dmesg: Apr 24 23:27:28 daffy kernel: [53021.123542] Bluetooth: hci0: SCO packet for unknown connection handle 65534 Apr 24 23:27:28 daffy kernel: [53021.123551] Bluetooth: hci0: SCO packet for unknown connection handle 0 Apr 24 23:27:28 daffy kernel: [53021.143555] Bluetooth: hci0: SCO packet for unknown connection handle 63744 Apr 24 23:27:28 daffy kernel: [53021.153575] Bluetooth: hci0: SCO packet for unknown connection handle 1 Apr 24 23:27:28 daffy kernel: [53021.173563] Bluetooth: hci0: SCO packet for unknown connection handle 63744 Then, after at most a few minutes, after one of bursts like above, pulseaudio reports: Apr 24 23:27:28 daffy pulseaudio[2733]: W: [bluetooth] module- bluez5-device.c: SCO packet received of unaligned size: 5 (the size differs between runs) And the headset is getting disconnected from pulseaudio - it's still connected via Bluetooth, but it's status in pavucontrol switches to 'Disabled'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826141] Re: linux-aws: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826150 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 14:35 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 26. April 2019 02:36 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1826141 Title: linux-aws: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Ready for Promote to Proposed phase-changed: Friday, 26. April 2019 02:36 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826143] Re: linux-azure: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826150 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 15:35 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 26. April 2019 02:36 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1826143 Title: linux-azure: 5.0.0-1005.5 -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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Ready for Promote to Proposed phase-changed: Friday, 26. April 2019 02:36 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches
** No longer affects: amd ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: amd Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
I suspect the Xorg modesetting driver's atomic logic might have something to do with this. Can someone experiencing the problem please try logging into 'Ubuntu on Wayland' and tell us if that avoids the issue? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
** 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/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Kernel NULL pointer dereference in mac80211_hwsim. [Fix] a1881c9b8a1e mac80211_hwsim: Timer should be initialized before device registered This fix has been included in 4.19.9 or above. [Test Case] $ git clone https://github.com/aircrack-ng/aircrack-ng # Tested with 69a406c $ cd aircrack-ng $ grep 'sudo apt' README.md | bash $ autoreconf -i $ ./configure --with-experimental $ make check $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration # Run integration test again and check dmesg $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration Verified with VMs setup locally. [Regression Risk] Low. Move forward data structure initialization only. This patch has also been included in LTS stable kernel. Original Bug Report The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6:
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
I still haven't been able to reproduce this. If you can reproduce this easily, maybe I can provide some kernels to be tested? I'll keep trying to reproduce here. I compared my VM settings to why is in the bug description, and I have the same config, except the region. I wouldn't think that would have an effect, but I'll look into it. -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823056] Re: autopkgtests run too often, too much and don't skip enough
Requesting to rerun linux test cases, as triggered by gcc-8 to confirm the fix. As currently they pass rebuild test, but end up as an overall FAIL due to regression suite. they should turn green under: http://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html#gcc-8 Or look for gree pass, as triggered by gcc-8 on https://autopkgtest.ubuntu.com/packages/linux/cosmic/s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823056 Title: autopkgtests run too often, too much and don't skip enough Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] * linux autopkgtest should only execute either rebuild tests, when triggered by toolchain. or execute regression suite when triggered by meta but never both. As otherwise, it results in false negative results for the kernel [Test Case] * Trigger adt test of linux with a matching linux-meta. Check that rebuild test is skipped, and that the regression suite test runs. * trigger adt test of linux with triggered by gcc-6/7/8 (as appropriate) and observe that rebuild test runs, and regression suite test is skipped. * (when this is applied to flavours) trigger adt test of linux-* with a matching flavour meta, and check that regression test-suite is skipped on kernels that cannot boot in scaling stack (e.g. gcp, azure, aws, etc) [Fix] * debian/tests/* are modified to pay more attention as to what they are triggered by, and raise appropriate skipped error codes [Regression Potential] * incorrect tests may run at incorrect time is the regression potential here, hence the two test cases verify that the right tests are executed when expected. * care was taken to take into account all linux kernel flavours, hence the third test case need to be reverified on flavoured kernels. [Other Info] * affects all stable series xenial and up, across all kernel flavours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826289] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1825420 *** https://bugs.launchpad.net/bugs/1825420 ** This bug has been marked a duplicate of bug 1825420 package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826289 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: Confirmed Bug description: I had problems in the 19.04 upgrade, as in https://ubuntuforums.org/showthread.php?t=2417517 The Crash happened during a sudo apt full-upgrade that was requested by the team is helping me ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu Apr 25 01:27:59 2019 ErrorMessage: triggers looping, abandoned HibernationDevice: RESUME=UUID=16ee3024-b6d7-4569-92e6-334e6d55fb90 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=dcd8f016-29e1-4dc4-a9e1-33ea6b421152 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.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-23 (1 days ago) dmi.bios.date: 09/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0607 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0607:bd09/17/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All 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/1826289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822808 - phase: Holding before Release - phase-changed: Tuesday, 23. April 2019 09:10 UTC + phase: Ready for Release + phase-changed: Thursday, 25. April 2019 23:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 + promote-to-updates: Pending -- ready to copy -- 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/1822807 Title: linux-gcp: 4.15.0-1030.32~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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid 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 verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822808 phase: Ready for Release phase-changed: Thursday, 25. April 2019 23:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Promote to Proposed - phase-changed: Thursday, 25. April 2019 21:07 UTC + phase: Testing + phase-changed: Thursday, 25. April 2019 23:07 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- 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/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Testing phase-changed: Thursday, 25. April 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826144] Re: linux-gcp: 5.0.0-1005.5 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 - phase: Ready for Packaging - phase-changed: Wednesday, 24. April 2019 16:07 UTC + phase: Packaging + phase-changed: Thursday, 25. April 2019 23:06 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1826144 Title: linux-gcp: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 phase: Packaging phase-changed: Thursday, 25. April 2019 23:06 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Promote to Proposed - phase-changed: Thursday, 25. April 2019 21:08 UTC + phase: Testing + phase-changed: Thursday, 25. April 2019 23:08 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- 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/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Testing phase-changed: Thursday, 25. April 2019 23:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822807 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Holding before Release - phase-changed: Tuesday, 23. April 2019 08:35 UTC + phase: Ready for Release + phase-changed: Thursday, 25. April 2019 23:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 + promote-to-updates: Pending -- ready to copy -- 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/1822808 Title: linux-gcp: 4.15.0-1030.32 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid 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 verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822807 (xenial/linux-gcp) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Ready for Release phase-changed: Thursday, 25. April 2019 23:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826144] Re: linux-gcp: 5.0.0-1005.5 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 5.0.0-1005.5 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1826144 Title: linux-gcp: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 phase: Ready for Packaging phase-changed: Wednesday, 24. April 2019 16:07 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825272] Re: headset-mic doesn't work on two Dell laptops.
** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1825272 Title: headset-mic doesn't work on two Dell laptops. Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Confirmed Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] the headset-mic can't be detected after we plug the headset into the audio jack [Fix] Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE. [Test Case] Boot up the system plug the headset into the audio jack The audio device selecting dialogue will show up selecting headset-mic icon, then rerord sound from headset-mic, it works well. [Regression Risk] Low. this patch only applies to specific dell machines which have the same pin config as defined in the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1825272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM is enabled, on some codecs or for some hw design, there is noise with the codec runtime PM enabled. [Fix] put the machine in the power_save_black_list, this will set the power_save=0 [Test Case] just boot up and do some audio operations, there is no noise anymore [Regression Risk] Low. this patch ony applies to the specific machines. I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Promote to Proposed - phase-changed: Thursday, 25. April 2019 21:07 UTC + phase: Testing + phase-changed: Thursday, 25. April 2019 22:38 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Testing phase-changed: Thursday, 25. April 2019 22:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826334] Re: linux-raspi2: 4.15.0-1035.37 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Holding before Promote to Proposed phase-changed: Thursday, 25. April 2019 13:38 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Holding -- master bug not ready for proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826334 Title: linux-raspi2: 4.15.0-1035.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Holding before Promote to Proposed phase-changed: Thursday, 25. April 2019 13:38 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [SRU justification] == Impact == Ethernet connection using a SKY2 card stops working after suspend. == Fix == A fix for this landed in v5.0 upstream and was picked up in Xenial via upstream stable but not yet in Bionic and Cosmic. The change simply increases a timeout. == Testcase == Suspend/resume with affected hardware present. == Risk of Regression == Very low as only changing a timeout value in a specific hardware driver. --- Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM is enabled, on some codecs or for some hw design, there is noise with the codec runtime PM enabled. [Fix] put the machine in the power_save_black_list, this will set the power_save=0 [Test Case] just boot up and do some audio operations, there is no noise anymore [Regression Risk] Low. this patch ony applies to the specific machines. I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821290] Re: Pop noise when headset is plugged in or removed from GHS/Line-out jack
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1821290 Title: Pop noise when headset is plugged in or removed from GHS/Line-out jack Status in HWE Next: Fix Released 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 Bug description: == SRU Justification == * Impact: There's unpleasant pop noise when headset is plugged in or removed from GHS/Line-out jack. * Fix: Issue can be fixed by these four patches. All of them are accepted by upstream. - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of Headset Mode for ALC225 - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225 - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB * Testcase: Connect/remove a headset to/from the jack and see if there's noise. * Risk of Regression: Low since these patches only affect specific platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1821290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814874] Re: NULL pointer dereference when using z3fold and zswap
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1814874 Title: NULL pointer dereference when using z3fold and zswap Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == Justification == When using z3fold and zswap on a VM under overcommitted memory stress, z3fold will complains about an "unknown buddy id 0" and fail to get a pointer to the mapped allocation in z3fold_map(). z3fold: unknown buddy id 0 WARNING: CPU: 2 PID: 1584 at mm/z3fold.c:971 z3fold_zpool_map+0xce/0x100 [z3fold] And it will leads to a null pointer dereference in zswap BUG: unable to handle kernel NULL pointer dereference at PGD 0 P4D 0 Oops: [#1] SMP PTI CPU: 2 PID: 1584 Comm: stress Tainted: GW 4.18.0-17-generic #18-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 RIP: 0010:zswap_writeback_entry+0x4d/0x360 == Fix == ca0246bb (z3fold: fix possible reclaim races) This patch has already in Disco, and can be cherry-picked into B/C. Not needed for Xenial and older kernels as z3fold is not supported. == Test == Test kernels for Bionic / Cosmic could be found here: http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Bionic/ http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Cosmic/ This issue can be reproduced easily in a KVM with the following setup: * 8G disk, 4G RAM, 4 CPUs * 1G swap * "zswap.enabled=1 zswap.zpool=z3fold zswap.max_pool_percent=7" added to grub * "z3fold" module added into /etc/initramfs-tools/modules Stress it with two childs running: * stress --vm-bytes 512M --vm 4 --vm-hang 3 * stress --vm-bytes 512M --vm 4 --vm-hang 7 The VM is expected to crash within 5 minutes. With the patched kernel, the VM can withstand this stress for over an hour with crashing with this issue == Regression potential == Small. Fix limited to z3fold. User needs to enable it explicitly for this feature. == Original Bug Report == Under memory pressure, my VM locks up. This has been reported upstream though I don't know how far any solution has progressed. https://bugzilla.kernel.org/show_bug.cgi?id=201603 Feb 6 07:15:42 vps632258 kernel: [151336.450064] z3fold: unknown buddy id 0 Feb 6 07:15:42 vps632258 kernel: [151336.454450] BUG: unable to handle kernel NULL pointer dereference at 0008 The little bit of log I managed to salvage is attached. This has happened to two identical VMs. Unusually it has not occurred on a third VM which is configured the same but has less RAM (fingers crossed it won't). Irrelevant information: I thought the lock-ups were due to me using a BTRFS filesystem, however I swapped over to NILFS2 and this still occurs. The only difference seems to be that I am now able to grab some of the kernel output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-14-generic 4.18.0-14.15~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:55:05 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1814874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00
[Kernel-packages] [Bug 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1818490 Title: Intel I210 Ethernet card not working after hotplug [8086:1533] Status in HWE Next: Confirmed Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Summary: Intel I210 Ethernet card not working after hotplug Steps to reproduce: 1. Power on system with ethernet cable on Intel I210 2. Check ethernet is workable 3. Unplug then plug the ethernet cable Expected result: Intel I210 Ethernet card is working, e.g. IP address acquired automatically if configured as DHCP. Actual result: Intel I210 Ethernet card not working after hotplug. dmesg has following error messages instead: [ 16.464321] [ cut here ] [ 16.464326] PCI PM: State of device not saved by igb_runtime_suspend+0x0/0x90 [igb] [ 16.464334] WARNING: CPU: 2 PID: 49 at /build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 pci_pm_runtime_suspend+0x175/0x180 [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi video [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem #37-Ubuntu [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 01/14/2019 [ 16.464369] Workqueue: pm pm_runtime_work [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180 [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282 [ 16.464372] RAX: RBX: 8a2557aee0a0 RCX: 0006 [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490 [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373 [ 16.464373] R10: R11: R12: [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: [ 16.464374] FS: () GS:8a257c48() knlGS: [ 16.464375] CS: 0010 DS: ES: CR0: 80050033 [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0 [ 16.464376] DR0: DR1: DR2: [ 16.464376] DR3: DR6: fffe0ff0 DR7: 0400 [ 16.464376] Call Trace: [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0 [ 16.464380] __rpm_callback+0xca/0x210 [ 16.464381] ? __switch_to_asm+0x40/0x70 [ 16.464382] ? __switch_to_asm+0x34/0x70 [ 16.464382] rpm_callback+0x59/0x80 [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0 [ 16.464384] rpm_suspend+0x137/0x640 [ 16.464385] ? __switch_to_asm+0x40/0x70 [ 16.464386] pm_runtime_work+0x81/0xa0 [ 16.464388] process_one_work+0x1de/0x410 [ 16.464389] worker_thread+0x32/0x410 [ 16.464390] kthread+0x121/0x140 [ 16.464391] ? process_one_work+0x410/0x410 [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70 [ 16.464392]
[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Kernel NULL pointer dereference in mac80211_hwsim. [Fix] a1881c9b8a1e mac80211_hwsim: Timer should be initialized before device registered This fix has been included in 4.19.9 or above. [Test Case] $ git clone https://github.com/aircrack-ng/aircrack-ng # Tested with 69a406c $ cd aircrack-ng $ grep 'sudo apt' README.md | bash $ autoreconf -i $ ./configure --with-experimental $ make check $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration # Run integration test again and check dmesg $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration Verified with VMs setup locally. [Regression Risk] Low. Move forward data structure initialization only. This patch has also been included in LTS stable kernel. Original Bug Report The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to
[Kernel-packages] [Bug 1823056] Re: autopkgtests run too often, too much and don't skip enough
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1823056 Title: autopkgtests run too often, too much and don't skip enough Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] * linux autopkgtest should only execute either rebuild tests, when triggered by toolchain. or execute regression suite when triggered by meta but never both. As otherwise, it results in false negative results for the kernel [Test Case] * Trigger adt test of linux with a matching linux-meta. Check that rebuild test is skipped, and that the regression suite test runs. * trigger adt test of linux with triggered by gcc-6/7/8 (as appropriate) and observe that rebuild test runs, and regression suite test is skipped. * (when this is applied to flavours) trigger adt test of linux-* with a matching flavour meta, and check that regression test-suite is skipped on kernels that cannot boot in scaling stack (e.g. gcp, azure, aws, etc) [Fix] * debian/tests/* are modified to pay more attention as to what they are triggered by, and raise appropriate skipped error codes [Regression Potential] * incorrect tests may run at incorrect time is the regression potential here, hence the two test cases verify that the right tests are executed when expected. * care was taken to take into account all linux kernel flavours, hence the third test case need to be reverified on flavoured kernels. [Other Info] * affects all stable series xenial and up, across all kernel flavours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826171] Re: linux: 4.18.0-19.20 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826170 (bionic/linux-hwe) derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 (linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm) -- swm properties -- boot-testing-requested: true - phase: Promote to Proposed - phase-changed: Thursday, 25. April 2019 11:01 UTC + bugs-spammed: true + phase: Testing + phase-changed: Thursday, 25. April 2019 22:32 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- 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/1826171 Title: linux: 4.18.0-19.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826170 (bionic/linux-hwe) derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 (linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 25. April 2019 22:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1825487 Title: The Realtek card reader does not enter PCIe 1.1/1.2 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] The Realtek card reader does not enter PCIe 1.1/1.2. This keeps Intel SoC staying at PC3, which consumes lots of power. [Fix] Set correct ASPM parameter on rtsx_pci. [Test] With the patch applied, Intel SoC can enter PC10, which saves lots of power. [Regression Potential] Low. The card reader in question still works as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1825487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825272] Re: headset-mic doesn't work on two Dell laptops.
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1825272 Title: headset-mic doesn't work on two Dell laptops. Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Confirmed Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] the headset-mic can't be detected after we plug the headset into the audio jack [Fix] Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE. [Test Case] Boot up the system plug the headset into the audio jack The audio device selecting dialogue will show up selecting headset-mic icon, then rerord sound from headset-mic, it works well. [Regression Risk] Low. this patch only applies to specific dell machines which have the same pin config as defined in the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1825272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824827] Re: tasks doing write()/fsync() hit deadlock in write_cache_pages()
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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verification-needed-cosmic' to 'verification-failed-
cosmic'.
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-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/1824827
Title:
tasks doing write()/fsync() hit deadlock in write_cache_pages()
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Invalid
Bug description:
[Impact]
* Tasks of a multi-threaded workload doing write() and fsync()
might deadlock in write_cache_pages(), preventing progress.
* The fix addresses a corner case in write_cache_pages() on
the range_cyclic implementation which allows the deadlock.
* Patch:
- commit 64081362e8ff4587b4554087f3cfc73d3e0a4cd7
("mm/page-writeback.c: fix range_cyclic writeback vs
writepages deadlock"), present in v4.20-rc1~92^2~19.
[Test Case]
* This issue originally has been hit by the 'perforce' (p4d)
tool in a XFS filesystem, but it's difficult/rare to occur.
* We've written an userspace + kernel module (kprobes-based)
to reproduce this problem and verify the test kernel/patch.
* The kprobes are strictly tied to particular kernel versions
because of the assembly instruction offsets. We'll provide
updated versions for -updates and -proposed for verification.
* Steps
(see output examples in comments):
- Userspace part:
$ gcc -o test test.c -pthread
- Kernel part:
$ touch Makefile
$ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kprobe-test.o clean
$ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kprobe-test.o
modules
- Shorter hung task timeout and higher console logging level
to notice the deadlocked tasks sooner, and watch progress:
$ echo 10 | sudo tee /proc/sys/kernel/hung_task_timeout_secs
$ echo 9 | sudo tee /proc/sys/kernel/printk
- Load module / Run userspace part (logging to kernel log) in XFS:
$ sudo insmod kprobe-test.ko
$ cd /path/to/xfs-mountpoint && sudo sh -c 'stdbuf -oL /path/to/test
>/dev/kmsg'
$ sudo rmmod kprobe-test
You may need to ctrl-z with the original kernel as 'test' doesn't
finish.
- Check kernel log or watch the system console:
$ dmesg
Check threads in D state.
$ ps -eLo pid,tid,state,comm | grep D | grep -e test -e kworker
[Regression Potential]
* The patch is small but changes core writeback infrastructure,
so there's a chance this may _affect_ some or other behavior
that has not been validated with our regression testing; not
exactly _break_ it. Please note our regression testing.
* This has been verified with 'xfstests' (not only for XFS fs,
despite its original name), used by major Linux filesystems
for regression testing during development. It's been tested
on systems with 24 and 4 CPUs (to exercise differences in
scalability, parallelism, and workload) and XFS and ext4
(reporter's environment + Ubuntu's default).
No regressions were observed (the set of failed tests is
the same in each system and tests failed in the same way).
* This has also been verified with 'iozone' for write intensive
tests, to exercise the writeback mechanism and no errors were
observed.
* The reporter has been running the test kernel with the patch
for weeks and has not observed any other issues/regressions.
[Other Info]
* This is only required in Cosmic (for the Bionic HWE kernel),
and is already applied in Disco.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824333] Re: autofs kernel module missing
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. 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-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/1824333 Title: autofs kernel module missing Status in autofs package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in autofs source package in Cosmic: Invalid Status in linux source package in Cosmic: Fix Committed Status in autofs source package in Disco: Invalid Status in linux source package in Disco: Fix Committed Bug description: linux-modules-4.18.0-17-generic misses the autofs module whereas linux-modules-4.15.0-47-generic contains it: root@files07:~# find /lib/modules -name '*autofs*' /lib/modules/4.15.0-46-generic/kernel/fs/autofs4 /lib/modules/4.15.0-46-generic/kernel/fs/autofs4/autofs4.ko /lib/modules/4.15.0-47-generic/kernel/fs/autofs4 /lib/modules/4.15.0-47-generic/kernel/fs/autofs4/autofs4.ko root@files07:~# dpkg -l|grep linux-modules ii linux-modules-4.15.0-46-generic 4.15.0-46.49 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-47-generic 4.15.0-47.50 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.18.0-15-generic 4.18.0-15.16~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-16-generic 4.18.0-16.17~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP ii linux-modules-4.18.0-17-generic 4.18.0-17.18~18.04.1 amd64 Linux kernel extra modules for version 4.18.0 on 64 bit x86 SMP This make it impossible to install and use the autofs package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1824333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259127/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259125/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259124/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259123/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259128/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259118/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259129/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259126/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259130/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259119/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259120/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259122/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259121/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2384 F pulseaudio /dev/snd/controlC1: jan2384 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 InstallationDate: Installed on 2016-10-22 (915 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20ALA0ARHH Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALA0ARHH dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20ALA0ARHH dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] Re: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.
apport information ** Tags added: apport-collected ** Description changed: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jan2384 F pulseaudio + /dev/snd/controlC1: jan2384 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998 + InstallationDate: Installed on 2016-10-22 (915 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + MachineType: LENOVO 20ALA0ARHH + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-18-generic N/A + linux-backports-modules-4.18.0-18-generic N/A + linux-firmware 1.173.5 + Tags: bionic + Uname: Linux 4.18.0-18-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago) + UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/20/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: GIET94WW (2.44 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20ALA0ARHH + dmi.board.vendor: LENOVO + dmi.board.version: SDK0E50510 PRO + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.family: ThinkPad X240 + dmi.product.name: 20ALA0ARHH + dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 + dmi.product.version: ThinkPad X240 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1826461/+attachment/5259117/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Confirmed Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to
[Kernel-packages] [Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:08 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:08 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826168] Re: linux-gcp: 4.18.0-1010.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826167 (bionic/linux-gcp-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 10:38 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 22:08 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1826168 Title: linux-gcp: 4.18.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826167 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 22:08 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826229] Re: linux-azure: 4.15.0-1043.47~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826230 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 12:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 22:08 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1826229 Title: linux-azure: 4.15.0-1043.47~14.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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826230 phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 22:08 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:07 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:07 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1826461 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: Incomplete Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Aroiu Ovidiu (ixanneo) 1. Could you describe somehow the performance difference? 2. How can I fix the touchpad issue which occurs by using your parameters Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826461] [NEW] Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.
Public bug reported: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826461 Title: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Status in linux package in Ubuntu: New Bug description: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection. Ubuntu 18.04, Thinkpad X240, Sierra modem Reproduced on 4.15 and 4.18 kernel. The bug is triggered only when there is no WiFi connection. After waking laptop from suspend ModemManager stops working and after that I cannot suspend anymore. When it happens mmcli -L gives: Found 1 modems: /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001] And mmcli -m 9: Status | lock: 'none' | unlock retries: 'sim-pin (3)' | state: 'registered' |power state: 'on' |access tech: 'gprs, lte' | signal quality: '0' (cached) After a few attempts to restart ModemManager and suspend it starts working. But only for one suspend. After one suspend I need to do the whole procedure again. Similar to: https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743 On Ubuntu 16.04 suspend and ModemManager used to work flawlessly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:08 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 20:07 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 21:07 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review 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/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:07 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826169] Re: linux-kvm: 4.18.0-1011.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 11:36 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 21:08 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review 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/1826169 Title: linux-kvm: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:08 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 20:07 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 21:07 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 21:07 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826171] Re: linux: 4.18.0-19.20 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826170 (bionic/linux-hwe) derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 (linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 11:01 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826171 Title: linux: 4.18.0-19.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826170 (bionic/linux-hwe) derivatives: bug 1826160 (linux-raspi2), bug 1826163 (linux-aws), bug 1826166 (linux-azure), bug 1826168 (linux-gcp), bug 1826169 (linux-kvm) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 11:01 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 20:07 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 20:07 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826146] Re: linux-snapdragon: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826150 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 13:06 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 20:06 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1826146 Title: linux-snapdragon: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826150 phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 20:06 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826160] Re: linux-raspi2: 4.18.0-1013.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 10:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 20:07 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826160 Title: linux-raspi2: 4.18.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 20:07 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826163] Re: linux-aws: 4.18.0-1015.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826171 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 25. April 2019 09:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 25. April 2019 20:07 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1826163 Title: linux-aws: 4.18.0-1015.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826161 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826171 phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 20:07 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] [NEW] Azure: Backport vIOMMU driver (increase vCPU limits)
Public bug reported: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: New Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824819 phase: Testing phase-changed: Thursday, 25. April 2019 09:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825996] Re: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04
*** This bug is a duplicate of bug 1825699 *** https://bugs.launchpad.net/bugs/1825699 It can boot but if I remove i2c_i801 from backlist touch pad does not work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825996 Title: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04 Status in linux package in Ubuntu: Fix Released Bug description: Hello, I upgrade ubuntu on 19.10 but my touchpad is not found. Can you help me ? Thank you Josselin ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbeaud-huy 2159 F pulseaudio /dev/snd/controlC1: jbeaud-huy 2159 F pulseaudio /dev/snd/pcmC1D0p: jbeaud-huy 2159 F...m pulseaudio CurrentDesktop: KDE Date: Tue Apr 23 15:49:51 2019 InstallationDate: Installed on 2018-11-19 (154 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LTS6YR00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c816b2e0-898d-4948-80e7-1466ae6b59e3 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) dmi.bios.date: 08/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET47W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS6YR00 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:bvrR0QET47W(1.24):bd08/14/2018:svnLENOVO:pn20LTS6YR00:pvrThinkPadL480:rvnLENOVO:rn20LTS6YR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS6YR00 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825996/+subscriptions -- Mailing list: https://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 1781016] Re: Slow flood of do_IRQ: No irq for vector
I have an APC UPS too. Great find. Who would have guessed an IRQ handling problem message from the kernel was due to a serial or USB device. Wow. On Thu, Apr 18, 2019 at 7:16 AM Kai-Heng Feng wrote: > Thanks for the info. Have anyone filed a bug against upstream apcupsd? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1781016 > > Title: > Slow flood of do_IRQ: No irq for vector > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Every few seconds I get something like this in my dmesg: > > [44984.933221] do_IRQ: 1.34 No irq handler for vector > [44986.933976] do_IRQ: 1.34 No irq handler for vector > [44991.935614] do_IRQ: 1.34 No irq handler for vector > [45004.938590] do_IRQ: 1.34 No irq handler for vector > [45005.939002] do_IRQ: 4.34 No irq handler for vector > [45034.949161] do_IRQ: 4.34 No irq handler for vector > [45051.954569] do_IRQ: 4.34 No irq handler for vector > [45058.956019] do_IRQ: 4.34 No irq handler for vector > [45062.957727] do_IRQ: 4.34 No irq handler for vector > [45063.958204] do_IRQ: 4.34 No irq handler for vector > [45073.961103] do_IRQ: 4.34 No irq handler for vector > > The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, > 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log > is just messages like above with varying #.## numbers. > > I researched it and tried disabling irqbalance. It had no effect, the > messages continued. > > The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. > I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 > NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never > occurred before installing 18.03 on the same hardware. No overclocking > whatsoever has ever been done to this machine. > > Also, I had to disable selective suspend on USB in this version to > prevent major USB issues, which was not required in 17.10, that might > be related. > > My system seems stable, but spurious IRQs can't be good. I'd like to > resolve this if possible. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-26-generic 4.15.0-26.28 > ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 > Uname: Linux 4.15.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gdm2145 F pulseaudio > doug 3736 F pulseaudio >/dev/snd/controlC1: gdm2145 F pulseaudio > doug 3736 F pulseaudio > Date: Tue Jul 10 12:49:00 2018 > HibernationDevice: > > InstallationDate: Installed on 2017-06-26 (379 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: System manufacturer System Product Name > ProcEnviron: >LANGUAGE=en_CA:en >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_CA.UTF-8 >SHELL=/bin/bash > ProcFB: > > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic > root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal > video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 > PulseList: >Error: command ['pacmd', 'list'] failed with exit code 1: Home > directory not accessible: Permission denied >No PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.15.0-26-generic N/A >linux-backports-modules-4.15.0-26-generic N/A >linux-firmware 1.173.1 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/19/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 4011 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME B350-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title:
[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs
There is no problem with suspend. I want to choose " when lid closed do nothing" I want that apps running on background when lid closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825219 Title: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs Status in linux package in Ubuntu: Incomplete Bug description: On ubuntu 16.04 settings "do anything when closing lid" is applied. Hard reset needs. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: neslihan 1863 F...m pulseaudio /dev/snd/controlC0: neslihan 1863 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947 InstallationDate: Installed on 2018-09-12 (220 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) MachineType: Acer TravelMate 5335 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-47-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/26/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA51_MV dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Intel_Mobile dmi.product.name: TravelMate 5335 dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
I only had time to look briefly, but here's a few notes. Firstly, a workaround for now is passing cma=0 on the kernel command line. I feel like there must be something wrong here if everything just works fine with CMA turned off, because obviously devices are getting CMA allocations when they don't really need them. I'm not familiar with CMA, but my assumption would be that you want as small a region as possible for it and thus you want to only use it for devices where it's actually necessary. Shooting from the hip I'd guess that one of two things is wrong, either some devices are doing their allocations wrong and getting CMA memory when they don't need it, or the DMA allocator is over zealous in its use of CMA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1826148 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 07:01 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 17:31 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages copies requested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826150 Title: linux: 5.0.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1826148 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 17:31 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826230] Re: linux-azure: 4.15.0-1043.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826229 (trusty/linux-azure) -- swm properties -- boot-testing-requested: true - phase: Ready for Promote to Proposed - phase-changed: Thursday, 25. April 2019 12:01 UTC + phase: Promote to Proposed + phase-changed: Thursday, 25. April 2019 17:31 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed -- 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/1826230 Title: linux-azure: 4.15.0-1043.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826229 (trusty/linux-azure) -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Thursday, 25. April 2019 17:31 UTC reason: promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816669] Re: AMD Rome : Minimal support patches
I would like these patches in 18.04.1 LTS. What do I need to do? -thanks -kim -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816669 Title: AMD Rome : Minimal support patches Status in amd: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: The following 3 patches need to be back ported to ubuntu 18.04.2(Linux 4.18) to complete the minimal support for Rome : 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode --thanks --kim --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1816669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1750786] Re: stress-ng enosys stressor triggers a kernel BUG
** Changed in: linux (Ubuntu) Status: In Progress => 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/1750786 Title: stress-ng enosys stressor triggers a kernel BUG Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: We are seeing kernel BUGs when running the stress-ng enosys stresser on released trusty kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1826150 Title: linux: 5.0.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1826148 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 07:01 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
With ivrs there are, at least, two problems: 1. Performance drop 2. With IOMMU disabled in bios these are useless -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826150] Re: linux: 5.0.0-14.15 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826150 Title: linux: 5.0.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826147 (bionic/linux-hwe-edge), bug 1826148 (bionic/linux-oem-osp1) derivatives: bug 1826139 (linux-raspi2), bug 1826141 (linux-aws), bug 1826143 (linux-azure), bug 1826144 (linux-gcp), bug 1826145 (linux-kvm), bug 1826146 (linux-snapdragon) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 07:01 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826230] Re: linux-azure: 4.15.0-1043.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => 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/1826230 Title: linux-azure: 4.15.0-1043.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826229 (trusty/linux-azure) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Thursday, 25. April 2019 12:01 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance
** Changed in: linux-azure (Ubuntu Xenial) Status: New => Fix Committed -- 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/1819689 Title: [linux-azure] Commit To Improve NVMe Performance Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Status in linux-azure source package in Cosmic: Fix Committed Bug description: In bug 1818138, the config option CONFIG_NO_HZ_FULL was requested to be enabled in the linux-azure kernels(currently 4.15 and 4.18) in order to increase NVME disks performance. To achieve the peak IOPs we are seeing in testing, the following commit is also needed: 7ac257b862f2c (“blk-mq: remove the request_list usage”) This commit cleans up unused code in block-mq (mq uses pre-allocated tags to allocate request, not request_list as it's used only in legacy queue). The commit saves a bunch of rcu locks on I/O queuing path, which increases the achievable IOPs seen in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821378] Re: [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Fix Committed
--
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/1821378
Title:
[linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
in Azure kernel
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
Fix Committed
Status in linux-azure source package in Cosmic:
Fix Committed
Bug description:
This is a request to include the following two commits in 16.04 and
18.04 linux-azure:
fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")
Both commits are fixes to prior commits and have been cc'd to upstream
stable.
Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4
The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed.
The result is accessing a bogus memory address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826343] Re: linux-kvm: 4.15.0-1033.33 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826358 - phase: Ready for Packaging - phase-changed: Thursday, 25. April 2019 10:40 UTC + phase: Packaging + phase-changed: Thursday, 25. April 2019 16:08 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- 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/1826343 Title: linux-kvm: 4.15.0-1033.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826358 phase: Packaging phase-changed: Thursday, 25. April 2019 16:08 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826343] Re: linux-kvm: 4.15.0-1033.33 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.15.0-1033.33 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- 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/1826343 Title: linux-kvm: 4.15.0-1033.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826358 phase: Packaging phase-changed: Thursday, 25. April 2019 16:08 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826335] Re: linux-snapdragon: 4.15.0-1051.56 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826358 - phase: Ready for Packaging - phase-changed: Thursday, 25. April 2019 10:39 UTC + phase: Packaging + phase-changed: Thursday, 25. April 2019 15:37 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1826335 Title: linux-snapdragon: 4.15.0-1051.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826358 phase: Packaging phase-changed: Thursday, 25. April 2019 15:37 UTC reason: prepare-package: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826335] Re: linux-snapdragon: 4.15.0-1051.55 -proposed tracker
** Summary changed: - linux-snapdragon: -proposed tracker + linux-snapdragon: 4.15.0-1051.55 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) ** Summary changed: - linux-snapdragon: 4.15.0-1051.55 -proposed tracker + linux-snapdragon: 4.15.0-1051.56 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1826335 Title: linux-snapdragon: 4.15.0-1051.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826358 phase: Packaging phase-changed: Thursday, 25. April 2019 15:37 UTC reason: prepare-package: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826143] Re: linux-azure: 5.0.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 - phase: Packaging - phase-changed: Thursday, 25. April 2019 15:05 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 25. April 2019 15:35 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- builds not complete -- 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/1826143 Title: linux-azure: 5.0.0-1005.5 -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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 phase: Holding before Promote to Proposed phase-changed: Thursday, 25. April 2019 15:35 UTC reason: promote-to-proposed: Holding -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826378] Re: linux autopkg tests failin in bionic and cosmic -proposed
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826378 Title: linux autopkg tests failin in bionic and cosmic -proposed Status in linux package in Ubuntu: Confirmed Bug description: The linux autopkg tests block evaluation of the binutils, gcc-7 and gcc-8 updates in bionic-proposed and cosmic-proposed.. There doesn't seem to be any progress, and pings on #ubuntu-release don't get attention. While these packages should probably stay in -proposed for longer than a week, the failing autopkg tests don't allow clear britney test runs. Pretty please address this issue, by either stating that these test results can be ignored, or please fix them. For the future, it would be nice, if this kind of ping could be avoided. See http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html http://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826416] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1826416 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826416 Title: [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy" Status in linux package in Ubuntu: Incomplete Bug description: A mutual customer is reporting ssh is not working on a Xenial based VM. This VM is running the 4.4 based Xenial kernel and not a custom linux-azure kernel. After an investigation this is a known old signaling issue. The 4.4 based Xenial kernels require the following patch: vmbus: fix missing signaling in hv_signal_on_read() (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13c5e97701091f9b02ded0c68809f8a6b08c747a). The patch is not in the upstream stable 4.4 tree, because it’s not needed there. Compared to the upstream 4.4 tree, Ubuntu 4.4.0-124-generic integrated more hv patches from the mainline kernel, e.g. Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read(), so it must pick up the above patch. We checked the latest Ubuntu 4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/tree/?h=Ubuntu-4.4.0-146.172) and the patch is also absent there. The patch (13c5e97701091f9b02ded0c68809f8a6b08c747a) can be cleanly cherry-picked into Ubuntu-4.4.0-146.172. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen
No BIOS options changed. I am on X1 Yoga 2nd gen - the BIOS exposes S3 by default. X1 Yoga 3rd gen is the first Lenovo generation that defaults to S0i3 for suspend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825395 Title: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt docking station. Initial connection to the dock works great, but after a few plug/unplug and suspend/resume cycles, the system gets in a state where a reboot is needed to make the dock work. The displayport connection still works so my external monitor gets the right display, but the thunderbolt / PCIe connection does not and so the USB and network ports in the dock aren't usable. I assume it is connected to the kernel messages like [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400 [37270.096820] pci :09:00.0: enabling Extended Tags [37270.096975] pci :09:00.0: supports D1 D2 [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link) [37270.097187] pcieport :07:01.0: ASPM: current common clock configuration is broken, reconfiguring [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400 [37270.108705] pci :0a:00.0: enabling Extended Tags [37270.108865] pci :0a:00.0: supports D1 D2 [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.109066] pcieport :07:02.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330 [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit] [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit] [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit] [37270.109499] pci :0b:00.0: supports D1 [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold [37270.109686] pcieport :07:04.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109724] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109738] pci :09:00.0: devices behind bridge are unusable because [bus 0a] cannot be assigned for them [37270.109766] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 0b [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under [bus 07-0b] (conflicts with (null) [bus 07-0b]) [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70] [37270.109843] pcieport :07:04.0: bridge window [mem 0xd400-0xe9ff] [37270.109848] pcieport :07:04.0: bridge window [mem 0x9000-0xb9ff 64bit pref] [37270.109849] pcieport :07:04.0: devices behind bridge are unusable because [bus 3d-70] cannot be assigned for them ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roland 1690 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 09:40:22 2019 InstallationDate: Installed on 2019-03-29 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20JGS01000 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET45W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JGS01000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Update to 2 hours ago: Started getting segfault problems with libglib. Again re-install fixed that but then I was getting segfaults elsewhere too. I have now reverted to a full system backup of 18.10 that I made earlier && will probably stay on that for a bit longer. -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
I went back to the 4.18 kernel but am not running VirtualBox (running bare metal). Also seeing issues with libglib. gnome-shell won't run due to a trap in libglib-2.0.so: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826025 -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826143] Re: linux-azure: 5.0.0-1005.5 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 - phase: Ready for Packaging - phase-changed: Wednesday, 24. April 2019 16:06 UTC + phase: Packaging + phase-changed: Thursday, 25. April 2019 15:05 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1826143 Title: linux-azure: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 phase: Packaging phase-changed: Thursday, 25. April 2019 15:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826143] Re: linux-azure: 5.0.0-1005.5 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 5.0.0-1005.5 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) -- 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/1826143 Title: linux-azure: 5.0.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826150 phase: Packaging phase-changed: Thursday, 25. April 2019 15:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
I think the keyboard might want to use hid-microsoft. But before doing that, can you check if the TB16 has the latest firmware? You may need a Windows system to update the firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825996] Re: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04
*** This bug is a duplicate of bug 1825699 *** https://bugs.launchpad.net/bugs/1825699 Beaud'huy, Doesn't work in what regard? It can't boot? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825996 Title: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04 Status in linux package in Ubuntu: Fix Released Bug description: Hello, I upgrade ubuntu on 19.10 but my touchpad is not found. Can you help me ? Thank you Josselin ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbeaud-huy 2159 F pulseaudio /dev/snd/controlC1: jbeaud-huy 2159 F pulseaudio /dev/snd/pcmC1D0p: jbeaud-huy 2159 F...m pulseaudio CurrentDesktop: KDE Date: Tue Apr 23 15:49:51 2019 InstallationDate: Installed on 2018-11-19 (154 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LTS6YR00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c816b2e0-898d-4948-80e7-1466ae6b59e3 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) dmi.bios.date: 08/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET47W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS6YR00 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:bvrR0QET47W(1.24):bd08/14/2018:svnLENOVO:pn20LTS6YR00:pvrThinkPadL480:rvnLENOVO:rn20LTS6YR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS6YR00 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826416] [NEW] [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy"
Public bug reported: A mutual customer is reporting ssh is not working on a Xenial based VM. This VM is running the 4.4 based Xenial kernel and not a custom linux- azure kernel. After an investigation this is a known old signaling issue. The 4.4 based Xenial kernels require the following patch: vmbus: fix missing signaling in hv_signal_on_read() (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13c5e97701091f9b02ded0c68809f8a6b08c747a). The patch is not in the upstream stable 4.4 tree, because it’s not needed there. Compared to the upstream 4.4 tree, Ubuntu 4.4.0-124-generic integrated more hv patches from the mainline kernel, e.g. Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read(), so it must pick up the above patch. We checked the latest Ubuntu 4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/tree/?h=Ubuntu-4.4.0-146.172) and the patch is also absent there. The patch (13c5e97701091f9b02ded0c68809f8a6b08c747a) can be cleanly cherry-picked into Ubuntu-4.4.0-146.172. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-hyper-v ** Summary changed: - [Xenial] Customer could not SSH to Linux VM due to "VSC State Unhealthy" + [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826416 Title: [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy" Status in linux package in Ubuntu: New Bug description: A mutual customer is reporting ssh is not working on a Xenial based VM. This VM is running the 4.4 based Xenial kernel and not a custom linux-azure kernel. After an investigation this is a known old signaling issue. The 4.4 based Xenial kernels require the following patch: vmbus: fix missing signaling in hv_signal_on_read() (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13c5e97701091f9b02ded0c68809f8a6b08c747a). The patch is not in the upstream stable 4.4 tree, because it’s not needed there. Compared to the upstream 4.4 tree, Ubuntu 4.4.0-124-generic integrated more hv patches from the mainline kernel, e.g. Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read(), so it must pick up the above patch. We checked the latest Ubuntu 4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/tree/?h=Ubuntu-4.4.0-146.172) and the patch is also absent there. The patch (13c5e97701091f9b02ded0c68809f8a6b08c747a) can be cleanly cherry-picked into Ubuntu-4.4.0-146.172. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
