[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend
Looks like it's in master-next (-31.33). See https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-next
and https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-31.33#n856
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
after suspend
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
This upstream bug has been confirmed to affect Ubuntu users[1]. As
per the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
from system sleep. Frequency of the bug is described as once every
few days[2].
[1] E.g. this user confirms the bug & very specific workaround:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
[2] E.g. this log of crashes:
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23
This is a bug in blk-core.c. It is not specific to any one hardware
driver. Technically the suspend bug is triggered by the SCSI core -
which is used by *all SATA devices*.
The commit also includes a test which quickly and reliably proves the
existence of a horrifying bug.
I guess you might avoid this bug only if you have root on NVMe. The
other way to not hit the Xorg crash is if you don't use all your RAM,
so there's no pressure that leads to cold pages of Xorg being swapped.
Also, you won't reproduce the Xorg crash if you suspend+resume
immediately. (This frustrated my tests at one point, it only
triggered after left the system suspended over lunch :).
Fix: "block: do not use interruptible wait anywhere"
in kernel 4.17:
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428
in kernel 4.16.8:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.16.y=7859056bc73dea2c3714b00c83b253d4c22bf7b6
lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-24.26#n856
I.e., this bug is still present in Ubuntu source package
linux-4.15.0-24.26 (and 4.15.0-23.25). I attach hardware details
(lspci-vnvn.log) of a system where this bug is known to happen.
Regards
Alan
WORKAROUND: Use kernel parameter:
scsi_mod.scan=sync
== Fix ==
1dc3039bc87a ("block: do not use interruptible wait anywhere")
== Regression Potential ==
Low. This patch has been sent to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://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 1785816] Re: Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
Thanks folks, looking forward to the results. I would have thought it would noop where the feature was not in use; as far as I know it requires explicit activation. Mark -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785816 Title: Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING Status in linux package in Ubuntu: Triaged Bug description: Hi folks, is there a reason we do not enable CONFIG_NETWORK_PHY_TIMESTAMPING ? I'm not sure of the tradeoffs but I think this config option is required for PTP time syncronization which would be useful in telco and financial (and OCD :)) environments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780103] Re: Network namespaces support for non-IP suddenly missing
I have source code now that works on the old kernel, and doesn't on the new one. Shall I post it (somehow - I don't know how)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780103 Title: Network namespaces support for non-IP suddenly missing Status in linux package in Ubuntu: Incomplete Bug description: I run 16.04, and I keep daily track of all dist-upgrades. Yesterday (3 july 2018) there was an upgrade, and it must have been a kernel upgrade, because my machine had rebooted (which I make it do automatically if needed). From today, the system tests on my project have stopped working (C development). These system tests do the following: using the 'ip' command, they set up several network namespaces, in which I run several executables concurrently, that exchange network messages with each other. The namespaces that use IP have kept on working, while the ones that don't (I'm implementing an ethernet network packet structure of my own) have stopped working. I've done the same tests on my laptop, which is also a 16.04, on which I haven't done the upgrade (and I'm very hesitant to do so now, because this is my bread and butter), and there they work still. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kees 1919 F pulseaudio /dev/snd/seq:timidity 1084 F timidity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3ed19ff5-7945-42ac-a22a-9136402798d8 InstallationDate: Installed on 2018-02-06 (148 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=43c7f0dc-00d1-4bb5-86c0-9ac982fbe227 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.19 RfKill: Tags: xenial Uname: Linux 4.4.0-128-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H110M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/16/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kees 1920 F pulseaudio /dev/snd/seq:timidity 1065 F timidity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=3ed19ff5-7945-42ac-a22a-9136402798d8 InstallationDate: Installed on 2018-02-06 (148 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=43c7f0dc-00d1-4bb5-86c0-9ac982fbe227 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio
[Kernel-packages] [Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
** Description changed: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: - * Disable integrated graphics/GPU in your BIOS. + * Disable integrated graphics/GPU in your BIOS; or - * Add 'nomodeset' to your kernel command line. - + * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then + run: sudo update-initramfs + and reboot. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS; or * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run: sudo update-initramfs and reboot. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767786] Re: No WiFi (BCM43142) after kernel upgrade to 4.4.0-122
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767786 Title: No WiFi (BCM43142) after kernel upgrade to 4.4.0-122 Status in linux package in Ubuntu: Expired Bug description: The wireless adapter is not working after updating the LinuxMint 18.3 Sylvia kernel from 4.4.0-119 to 4.4.0-122. In order to make it work I downgraded back to 4.4.0-119. 03:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751887 Title: The brightness of the screen cannot be adjusted with either the buttons or the slider. Status in linux package in Ubuntu: Expired Bug description: Brightness is always at 100% and cannot be adjusted with either the FN brightness buttons or the Unity top bar slider. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: albertoinet 1199 F pulseaudio /dev/snd/controlC0: albertoinet 1199 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 20:49:16 2018 HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f InstallationDate: Installed on 2018-02-25 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Micro-Star International Co., Ltd. GT72VR 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1785IMS.30E dmi.board.asset.tag: Default string dmi.board.name: MS-1785 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: GT dmi.product.name: GT72VR 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785363] [NEW] Error in Booting
You have been subscribed to a public bug: When i change my default graphics driver as Nvidia then it's not start . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 4 09:59:11 2018 DistUpgraded: 2018-06-18 22:25:36,929 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [GeForce GT 520M] [17aa:397d] MachineType: LENOVO HuronRiver Platform ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=976f64eb-604f-4770-b36c-2efb3dae6ef1 ro quiet splash acpi_backlight=none vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-06-18 (46 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Jun 18 23:25:54 2018 xserver.configfile: default xserver.errors: Failed to initialize GLX extension (Compatible NVIDIA X driver not found) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16560 vendor LEN xserver.version: 2:1.19.6-1ubuntu4 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic ubuntu -- Error in Booting https://bugs.launchpad.net/bugs/1785363 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785363] Re: Error in Booting
Please try the workarounds mentioned at the top of bug 1705369. ** Package changed: ubuntu => nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1785363 Title: Error in Booting Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: When i change my default graphics driver as Nvidia then it's not start . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 4 09:59:11 2018 DistUpgraded: 2018-06-18 22:25:36,929 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [GeForce GT 520M] [17aa:397d] MachineType: LENOVO HuronRiver Platform ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=976f64eb-604f-4770-b36c-2efb3dae6ef1 ro quiet splash acpi_backlight=none vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-06-18 (46 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Jun 18 23:25:54 2018 xserver.configfile: default xserver.errors: Failed to initialize GLX extension (Compatible NVIDIA X driver not found) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16560 vendor LEN xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1785363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775452] Re: Nouveau problems
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775452 Title: Nouveau problems Status in linux package in Ubuntu: Expired Bug description: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5M/300E5L ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RED.019.171215.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5M-XD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9046A07-C01-G001-S0001+10.0.15063 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RED.019.171215.ZW:bd12/15/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5M/300E5L:pvrP06RED:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5M-XD1BR:rvrSGL9046A07-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5M/300E5L dmi.product.version: P06RED dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways
Latest Dell IoT 300x Gateway kernel snap (r93) based on kernel ver. 4.4.0-132.158 was tested and verified by CE-QA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783241 Title: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: Several scheduled upgrades to the HMS SocketCAN protocol driver over USB->CAN interface are required. SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS kernel through following patch (BugLink: http://bugs.launchpad.net/bugs/1774563): cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == SRU Justification == The scheduled upgrades include following changes: - support adapters for CL1 (Communication Layer for legacy devices) and CL2 (current devices) - removed CAN-IDM100 support (Microchip Rev A microcontroller) - add CAN-IDM101 support (Microchip Rev B microcontroller) - add Error-Passive recognition - move CAN message handling to the core module - use ktime API for timestamps - fixes Linux kernel coding style issues == Fix == UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways
caracalla-kernel snap (r93) based on kernel ver. 4.4.0-132.158 was tested and verified by CE-QA. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783241 Title: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: Several scheduled upgrades to the HMS SocketCAN protocol driver over USB->CAN interface are required. SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS kernel through following patch (BugLink: http://bugs.launchpad.net/bugs/1774563): cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == SRU Justification == The scheduled upgrades include following changes: - support adapters for CL1 (Communication Layer for legacy devices) and CL2 (current devices) - removed CAN-IDM100 support (Microchip Rev A microcontroller) - add CAN-IDM101 support (Microchip Rev B microcontroller) - add Error-Passive recognition - move CAN message handling to the core module - use ktime API for timestamps - fixes Linux kernel coding style issues == Fix == UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785759] Re: System hangs after shutdown or restart operation is initiated.
For testing the latest kernel, I downloaded and installed the following .deb files (System is 64-bit): linux-headers-4.18.0-041800rc8_4.18.0-041800rc8.201808052031_all.deb linux- headers-4.18.0-041800rc8-generic_4.18.0-041800rc8.201808052031_amd64.deb linux-image-unsigned-4.18.0-041800rc8-generic_4.18.0-041800rc8.201808052031_amd64.deb (showed the 'missing dependencies' error on installation, therefore installed linux-modules) linux- modules-4.18.0-041800rc8-generic_4.18.0-041800rc8.201808052031_amd64.deb This resolved hanging of the system while shutting down/restarting. However, now I see a particular screen on startup (image attached) where I can spot the " [2.124104] ACPI Bios Error (bug) ". Is this something to be worried about? ** Attachment added: "Image of the screen on startup (displaying the ACPI Bios Error)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785759/+attachment/5172817/+files/IMG_2159.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785759 Title: System hangs after shutdown or restart operation is initiated. Status in linux package in Ubuntu: Incomplete Bug description: When I attempt to turn off my laptop or restart it, the system hangs as it is. I then have to resort to force shutdown via the power button. I've disabled my touchpad (since it doesn't work properly - probably a hardware issue) and therefore use an external mouse (Logitech M235). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: protagonist26 2204 F pulseaudio /dev/snd/controlC0: protagonist26 2204 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 7 12:36:21 2018 InstallationDate: Installed on 2018-07-27 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20354 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=3dad4d21-4cc3-4346-abae-fb6b8a4eee38 ro quiet splash acpi=force vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN25WW:bd04/10/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785234] Re: Kernel panic softlockup with z3fold while running bitcoind
Update: I could not recreate this bug using zbud as the allocator. I need to test newer kernels and see if there's an easier way to trigger this. -- 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/1785234 Title: Kernel panic softlockup with z3fold while running bitcoind Status in linux-gcp package in Ubuntu: New Bug description: So far I have only triggered this while running bitcoind (or bitcoin- qt) with the z3fold module loaded. I will do further testing to see if I can trigger it any other ways. [54075.373045] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:41] [54075.377042] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [bitcoin-msghand:7509] [54075.377042] Modules linked in: cachefiles ip6table_filter ip6_tables fscache iptable_filter ip_tables x_tables crct10dif_pclmul crc32_pclmul ghash_clmulni_intel intel_rapl_perf psmouse serio_raw virtio_net pvpanic i2c_piix4 nfsd auth_rpcgss nfs_acl lockd grace sunrpc autofs4 aesni_intel aes_x86_64 crypto_simd cryptd glue_helper z3fold lz4hc lz4hc_compress [54075.377068] CPU: 1 PID: 7509 Comm: bitcoin-msghand Not tainted 4.15.0-1014-gcp #14~16.04.1-Ubuntu [54075.377069] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [54075.377076] RIP: 0010:native_queued_spin_lock_slowpath+0x25/0x1a0 [54075.377077] RSP: :aec7c13b7420 EFLAGS: 0202 ORIG_RAX: ff11 [54075.377079] RAX: 0001 RBX: db7b82e96a80 RCX: [54075.377080] RDX: 0001 RSI: 0001 RDI: 8c687a5aa010 [54075.377081] RBP: aec7c13b7420 R08: 8c6879c749d8 R09: 0002 [54075.377082] R10: aec7c13b74d8 R11: aec7c13b7628 R12: 8c687a5aa000 [54075.377083] R13: 8c687a5aa010 R14: 8c687a5aa000 R15: db7b82de7580 [54075.377084] FS: 7f133e7fc700() GS:8c687fd0() knlGS: [54075.377086] CS: 0010 DS: ES: CR0: 80050033 [54075.377087] CR2: 7f3c521ba000 CR3: b4d24006 CR4: 003606e0 [54075.377090] DR0: DR1: DR2: [54075.377091] DR3: DR6: fffe0ff0 DR7: 0400 [54075.377092] Call Trace: [54075.377099] _raw_spin_lock+0x20/0x30 [54075.377104] z3fold_zpool_map+0x72/0xf0 [z3fold] [54075.377108] zpool_map_handle+0x1c/0x20 [54075.377111] zswap_writeback_entry+0x47/0x350 [54075.377114] z3fold_zpool_evict+0x2b/0x40 [z3fold] [54075.377116] z3fold_zpool_shrink+0x2a5/0x350 [z3fold] [54075.377118] zpool_shrink+0x1c/0x20 [54075.377119] zswap_frontswap_store+0x271/0x4d0 [54075.377123] __frontswap_store+0x78/0x100 [54075.377125] swap_writepage+0x3f/0x80 [54075.377128] pageout.isra.53+0x1e6/0x340 [54075.377131] shrink_page_list+0x992/0xbe0 [54075.377133] shrink_inactive_list+0x296/0x5e0 [54075.377135] ? __switch_to_asm+0x40/0x70 [54075.377137] ? syscall_return_via_sysret+0x5/0x75 [54075.377140] shrink_node_memcg+0x367/0x7e0 [54075.377142] ? __switch_to_asm+0x40/0x70 [54075.377144] ? __switch_to_asm+0x40/0x70 [54075.377146] shrink_node+0xe1/0x310 [54075.377147] ? shrink_node+0xe1/0x310 [54075.377149] do_try_to_free_pages+0xee/0x360 [54075.377152] try_to_free_pages+0xf1/0x1c0 [54075.377155] __alloc_pages_slowpath+0x405/0xec0 [54075.377158] __alloc_pages_nodemask+0x265/0x280 [54075.377162] alloc_pages_current+0x6a/0xe0 [54075.377165] __page_cache_alloc+0x86/0x90 [54075.377167] generic_file_read_iter+0x817/0xb60 [54075.377169] ? __switch_to_asm+0x40/0x70 [54075.377170] ? __switch_to_asm+0x34/0x70 [54075.377172] ? __switch_to_asm+0x40/0x70 [54075.377173] ? __switch_to_asm+0x34/0x70 [54075.377174] ? __switch_to_asm+0x40/0x70 [54075.377176] ? __switch_to_asm+0x34/0x70 [54075.377177] ? __switch_to_asm+0x40/0x70 [54075.377178] ? __switch_to_asm+0x34/0x70 [54075.377181] ext4_file_read_iter+0x56/0xf0 [54075.377184] new_sync_read+0xe2/0x130 [54075.377187] __vfs_read+0x29/0x40 [54075.377188] vfs_read+0x93/0x130 [54075.377190] SyS_read+0x55/0xc0 [54075.377194] do_syscall_64+0x7b/0x150 [54075.377196] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [54075.377197] RIP: 0033:0x7f1360bed27d [54075.377198] RSP: 002b:7f133e7f8a00 EFLAGS: 0293 ORIG_RAX: [54075.377200] RAX: ffda RBX: 7f128e42c7d0 RCX: 7f1360bed27d [54075.377201] RDX: 1000 RSI: 7f128dfe27d0 RDI: 0014 [54075.377201] RBP: 004f R08: 228def3009585ceb R09: 60c81007fca0c815 [54075.377202] R10: 6156858af7255092 R11: 0293 R12: 003c [54075.377203] R13: 008b R14: 7f128d6d03cf R15: 008b [54075.377205] Code: 84 00 00 00 00 00 0f 1f 44 00 00 55
[Kernel-packages] [Bug 1779802] Re: Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1779802 Title: Touchpad of ThinkPad P52 failed to work with message "lost sync at byte" Status in HWE Next: New Status in HWE Next artful series: New Status in HWE Next bionic series: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Invalid Bug description: On ThinkPad P52: touchpad failed to work and reports: [ 2.713396] input: ETPS/2 Elantech TrackPoint as /devices/platform/i8042/serio1/input/input8 [ 2.725328] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input5 And lots of errors printed out: [ 19.468387] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.474455] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.480657] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.487665] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.494682] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.494685] psmouse serio1: issuing reconnect request [ 19.679895] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.686285] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.692642] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.699858] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [ 19.706873] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 And the middle button can not work too. [Impact] On ThinkPad P52, Elantech touchpad had sync issue then failed to work. Middle button was not enabled too. [Fix] With two upstream patches, elantech touchpad works fine with middle button. [Test Case] Touchpad moves fine, left/right/middle buttons works fine. scroll mode works fine. [Regression Potential] Very low, Just enable specific hardware support. ??? (1): Input: elantech - fix V4 report decoding for module with middle key Aaron Ma (1): Input: elantech - enable middle button of touchpads on ThinkPad P52 drivers/input/mouse/elantech.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1779802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784542] Re: Realtek ethernet not functional on 4.15.0-29.31
Thanks. This issue is resolved on that kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784542 Title: Realtek ethernet not functional on 4.15.0-29.31 Status in linux package in Ubuntu: Confirmed Bug description: When using ethernet (Realtek RTL8111/8168/8411 using built-in r8169 driver v2.3LK-NAPI), dhclient stuck at DHCPDISCOVER. When using static IP, nm shows it's connected, but I can't ping anywhere. This issue only shows up in 4.15.0-29.31. I tried the following versions without issue: 1) 4.18.0-041800rc7 2) 4.16.0-041600 3) 4.15.0-23 4) 4.15.0-20 No issue on wifi (Intel 7260 iwlwifi), USB ethernet (Dell D3100 Dock) and USB ethernet (generic adapter using r8152 driver). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 1771 F pulseaudio /dev/snd/controlC0: daniel 1771 F pulseaudio CurrentDesktop: MATE Date: Tue Jul 31 14:42:31 2018 HibernationDevice: RESUME=UUID=efa14060-79a3-4f5d-99a5-9bb5f7e840d6 InstallationDate: Installed on 2018-07-08 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785731] Re: Linux Mint 19
kernel-fixed-upstream ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Riccardo Casa (rikmac) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785731 Title: Linux Mint 19 Status in linux package in Ubuntu: Incomplete Bug description: Last kernel update 4.15.0-30 CPU1 idle after kernel update. System:Host: iw5dgq-K53SC Kernel: 4.15.0-30-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm Distro: Linux Mint 19 Tara Machine: Device: laptop System: ASUSTeK product: K53SC v: 1.0 serial: N/A Mobo: ASUSTeK model: K53SC v: 1.0 serial: N/A BIOS: American Megatrends v: K53SC.204 date: 05/30/2011 BatteryBAT0: charge: 48.9 Wh 96.7% condition: 50.6/56.2 Wh (90%) volts: 12.4/10.8 model: [MKF_CUSTOMER] [MKF_BASEBOARD_ID] serial: N/A status: N/A CPU: Dual core Intel Core i5-2410M (-MT-MCP-) arch: Sandy Bridge rev.7 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9179 clock speeds: min/max: 800/2900 MHz 1: 2693 MHz 2: 2694 MHz 3: 2693 MHz 4: 2694 MHz Graphics: Card-1: Intel 2nd Generation Core Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0116 Card-2: NVIDIA GF119M [GeForce GT 520MX] bus-ID: 01:00.0 chip-ID: 10de:1051 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 18.0.5 (compat-v: 3.0) Direct Render: Yes Audio: Card Intel 6 Series/C200 Series Family High Def. Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20 Sound: Advanced Linux Sound Architecture v: k4.15.0-30-generic Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:002b IF: wlp3s0 state: up mac: Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: 9000 bus-ID: 05:00.0 chip-ID: 10ec:8168 IF: enp5s0 state: down mac: Drives:HDD Total Size: 240.1GB (17.9% used) ID-1: /dev/sda model: KINGSTON_SV300S3 size: 240.1GB serial: Partition: ID-1: / size: 220G used: 41G (20%) fs: ext4 dev: /dev/sda1 RAID: System: supported: N/A No RAID devices: /proc/mdstat, md_mod kernel module present Unused Devices: none Sensors: System Temperatures: cpu: 84.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Repos: Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list deb http: //mirrors.evowise.com/linuxmint/packages tara main upstream import backport deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-updates main restricted universe multiverse deb http: //mirror.csclub.uwaterloo.ca/ubuntu bionic-backports main restricted universe multiverse deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http: //archive.canonical.com/ubuntu/ bionic partner Info: Processes: 210 Uptime: 2:20 Memory: 1566.4/7885.5MB Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0 Client: Unknown python3.6 client inxi: 2.3.56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Re: linux-gcp: 4.15.0-1016.17 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784290] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-signed-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp 4.15.0-1016.17 - is in universe instead of main linux-image-4.15.0-1016-gcp-dbgsym 4.15.0-1016.17 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- 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/1784290 Title: linux-gcp: 4.15.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: Incomplete 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
@Kai-Heng your latest kernel completely breaks the network using r8169 for me. The system sort of manages to complete startup but fails to attach an address to the network card. This is accompanied with lots of console output similar to this ``` Aug 7 14:46:28 kernel: [ 25.761050] r8169 :05:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10). Aug 7 14:46:28 kernel: [ 25.771937] r8169 :05:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10). Aug 7 14:46:28 kernel: [ 26.068062] r8169 :05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000). Aug 7 14:46:28 kernel: [ 26.168057] r8169 :05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000). Aug 7 14:46:28 kernel: [ 26.268060] r8169 :05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000). Aug 7 14:46:28 kernel: [ 26.368055] r8169 :05:00.0 eth0: rtl_ocpar_cond == 1 (loop: 100, delay: 1000). ``` Using the standard bionic kernel the network works as long as I run `sudo ethtool -s eth0 wol g` between reboots. Otherwise the network card just vanishes (not visible in BIOS and Linux) until I unplug the computer for a minute or so. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T 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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1779817/+subscriptions -- Mailing list: https://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 1779817] Re: r8169 no internet after suspending
I can't even boot Kai's latest kernel! The system hard locks early in the boot process, I have tried blacklisting r8169 and rebuilding the initramfs, pretty sure it is not loaded by the point at which it hangs. My hardware is cursed... On 7 August 2018 at 21:13, Jan Rathmann wrote: > @Kai-Heng > I can confirm what Erik says - my network card seems to come up properly > after suspend with the backported kernel in #39. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1779817 > > Title: > r8169 no internet after suspending > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1779817/+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/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T 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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785890] [NEW] r8169 not resume after sleep , ubuntu 18.04
Public bug reported: after sleeping, network r8169 does not work again, only restarting computer for it to work again Kernel: 4.15.0-30-generic -- lshw -c network descrição: Ethernet interface produto: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller fabricante: Realtek Semiconductor Co., Ltd. ID físico: 0 informações do barramento: pci@:03:00.0 -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eusener2611 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 7 17:28:11 2018 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5457 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=f9b97b9a-9128-4f53-b1c9-751ec57cbb6a ro intel_pstate=skylake_hwp quiet splash nouveau.runpm=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-26 (102 days ago) dmi.bios.date: 12/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0WT51R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/08/2017:svnDellInc.:pnInspiron5457:pvr:rvnDellInc.:rn0WT51R:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5457 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1785890 Title: r8169 not resume after sleep , ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Bug description: after sleeping, network r8169 does not work again, only restarting computer for it to work again Kernel: 4.15.0-30-generic -- lshw -c network descrição: Ethernet interface produto: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller fabricante: Realtek Semiconductor Co., Ltd. ID físico: 0 informações do barramento: pci@:03:00.0 -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eusener2611 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 7 17:28:11 2018 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5457 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=f9b97b9a-9128-4f53-b1c9-751ec57cbb6a ro intel_pstate=skylake_hwp quiet splash nouveau.runpm=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-26 (102 days ago) dmi.bios.date: 12/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0WT51R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/08/2017:svnDellInc.:pnInspiron5457:pvr:rvnDellInc.:rn0WT51R:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron
[Kernel-packages] [Bug 1785890] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785890 Title: r8169 not resume after sleep , ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Bug description: after sleeping, network r8169 does not work again, only restarting computer for it to work again Kernel: 4.15.0-30-generic -- lshw -c network descrição: Ethernet interface produto: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller fabricante: Realtek Semiconductor Co., Ltd. ID físico: 0 informações do barramento: pci@:03:00.0 -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eusener2611 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 7 17:28:11 2018 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5457 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=f9b97b9a-9128-4f53-b1c9-751ec57cbb6a ro intel_pstate=skylake_hwp quiet splash nouveau.runpm=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-26 (102 days ago) dmi.bios.date: 12/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0WT51R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/08/2017:svnDellInc.:pnInspiron5457:pvr:rvnDellInc.:rn0WT51R:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5457 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
@Kai-Heng I can confirm what Erik says - my network card seems to come up properly after suspend with the backported kernel in #39. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T 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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785481] Re: amdgpu WQHD resolution(2560 × 1440) not available
Donk, the next step is to fully reverse commit bisect from kernel 4.15 to 4.16.18, in order to identify the latest kernel commit that did not work followed immediately by the next kernel commit that did work. This will allow a consideration of the fix commit for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow. Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully reverse commit bisecting. Also, the kernel release names are irrelevant for the purposes of bisecting. It is most helpful that after the fix commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed. Thank you for your help. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1785481 Title: amdgpu WQHD resolution(2560 × 1440) not available Status in linux package in Ubuntu: Incomplete Bug description: Hello, I use ubuntu 16.04 with hwe stack and an Radeon R9 285. With kernel 4.13 and older, I can use a resolution of 2560x1440. But, since the upgrade to kernel 4.15, I'm limited to the 1920x1200. I have attached the output of xrandr on both kernel. My screen (Dell U2713HM) is plugged to the output DVI-1. With a kernel 4.13, the output is detected as a DVI-I. But with a kernel 4.15, the output is detected as a DVI-D. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 5 16:46:32 2018 SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to xenial on 2016-12-17 (595 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederic 2366 F pulseaudio /dev/snd/controlC1: frederic 2366 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/Fred_SSD-Fred_Swap IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/Fred_SSD-Fred_Root ro quiet ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-17 (596 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare scanner sudo video _MarkForUpload: True dmi.bios.date: 10/28/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3003 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3003:bd10/28/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIRANGER:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784542] Re: Realtek ethernet not functional on 4.15.0-29.31
Please try this one instead: https://people.canonical.com/~khfeng/bionic-r8169-backport2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784542 Title: Realtek ethernet not functional on 4.15.0-29.31 Status in linux package in Ubuntu: Confirmed Bug description: When using ethernet (Realtek RTL8111/8168/8411 using built-in r8169 driver v2.3LK-NAPI), dhclient stuck at DHCPDISCOVER. When using static IP, nm shows it's connected, but I can't ping anywhere. This issue only shows up in 4.15.0-29.31. I tried the following versions without issue: 1) 4.18.0-041800rc7 2) 4.16.0-041600 3) 4.15.0-23 4) 4.15.0-20 No issue on wifi (Intel 7260 iwlwifi), USB ethernet (Dell D3100 Dock) and USB ethernet (generic adapter using r8152 driver). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 1771 F pulseaudio /dev/snd/controlC0: daniel 1771 F pulseaudio CurrentDesktop: MATE Date: Tue Jul 31 14:42:31 2018 HibernationDevice: RESUME=UUID=efa14060-79a3-4f5d-99a5-9bb5f7e840d6 InstallationDate: Installed on 2018-07-08 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784281] Re: linux: 4.15.0-31.33 -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/1784281 Title: linux: 4.15.0-31.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New 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 is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784292 (linux-azure), bug 1784293 (linux-azure-edge), bug 1784294 (linux-gcp), bug 1784296 (linux-hwe), bug 1784297 (linux-hwe-edge) derivatives: bug 1784283 (linux-raspi2), bug 1784284 (linux-oem), bug 1784285 (linux-aws), bug 1784288 (linux-azure), bug 1784290 (linux-gcp), bug 1784291 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784285] Re: linux-aws: 4.15.0-1018.18 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784285 Title: linux-aws: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784288] Re: linux-azure: 4.15.0-1020.20 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1784288 Title: linux-azure: 4.15.0-1020.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784284] Re: linux-oem: 4.15.0-1014.17 -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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1784284 Title: linux-oem: 4.15.0-1014.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784291] Re: linux-kvm: 4.15.0-1018.18 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784291 Title: linux-kvm: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784292] Re: linux-azure: 4.15.0-1020.20~16.04.1 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1784292 Title: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785856] Re: hung task flush-zfs
The mainline kernel builds do not seem to have the zfs kernel modules. I have lxd configured to use a zfs pool. Where can I get the zfs kernel modules compiled against the mainline kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785856 Title: hung task flush-zfs Status in linux package in Ubuntu: Incomplete Bug description: After restoring a snapshot on a running container a hung task task oops trace gets logged for flush-zfs. The command run was: % lxc restore wedgeiq foo1 If the container is not running restoring seems less likely to cause the hung task. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.131.137 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 7 16:03 seq crw-rw 1 root audio 116, 33 Aug 7 16:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 7 16:36:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: NEXCOM NSA-5160 PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic root=/dev/mapper/VG_WARP-WARPDRIVE ro intel_iommu=on net.ifnames=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 23 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/25/2017:svnNEXCOM:pnNSA-5160:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct23:cvrDefaultstring: dmi.product.name: NSA-5160 dmi.product.version: Default string dmi.sys.vendor: NEXCOM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755384] Re: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi
This bug was initially opened for Artful, but it is now EOL as is the 4.13 kernel. Can you confirm this bug still exists in Bionic(18.04)? ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755384 Title: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi Status in linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi. Reproduce: - 1. create VM with default setting in ESXi 6.5 / on-developing ESXi build 7940658 2. install geustOS zyh-ubuntu16.04.4-dsktop-64 image. 3. reboot it after finish installation 4. edit VM setting and enable hot-add CPU and memory 5. open a terminal and type command "ls /sys/devices/system/memory", find memory0 -- memory7 listed. 6. edit VM setting and set default 1024M memory to 2048M 7. type command "ls /sys/devices/system/memory", it still lists memory0-memory7. No more memoryX is added. The hot-add memory can't be recognized. Expect: For step 7, it should list memory8--memory15 when type "ls /sys/devices/system/memory". To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1755384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755393] Re: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit / ubuntu-18.04-desktop hang
This bug was initially opened for Artful, but it is now EOL as is the 4.13 kernel. Can you confirm this bug still exists in Bionic(18.04)? ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags removed: artful ** Tags added: bionic ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755393 Title: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit / ubuntu-18.04-desktop hang Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi Reproduce: - 1. create VM with EFI firewall in ESXi 2. install geustOS with ubuntu16.04.4-dsktop-64bit image. 3. reboot it after finish installation 4. edit VM setting and enable hot-add CPU and memory 5. edit VM setting and set default 1 vCPU to 2 6. open a terminal and run script to enable vcpu1: "sudo ~/rescanCpu.sh" 7. check the cpu number with command "cat /proc/cpuinfo" in terminal. but there is not output message for this command. click anywhere on VM desktop, there is no response. It seems like VM hang. From vmware developer's analysis: Looks to me like Ubuntu's problem. It noticed at 566 seconds after boot that CPU1 was hot-added. Then perhaps you run code to online CPU, and doing so ended up with warning at blk-mq.c: Mar 6 17:41:33 vmware-virtual-machine kernel: [ 566.583896] CPU1 has been hot-added Mar 6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing CommAmqpListener Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.431990] SMP alternatives: switching to SMP code Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487612] x86: Booting SMP configuration: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487616] smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.489517] Disabled fast string operations Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.492082] smpboot: CPU 1 Converting physical 2 to logical package 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.493162] Will online and init hotplugged CPU: 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524713] [ cut here ] Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524726] WARNING: CPU: 1 PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 __blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524727] Modules linked in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helpe r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops mptspi mptscsih drm mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi floppy Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525006] CPU: 1 PID: 2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525008] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.7915097.B64.1802282254 02/28/2018 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525013] Workqueue: kblockd blk_mq_run_work_fn Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525016] task: 8ab5326b task.stack: a694441d8000 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525021] RIP: 0010:__blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525023] RSP: 0018:a694441dbe38 EFLAGS: 00010202 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525026] RAX: 0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525028] RDX: 8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525029] RBP: a694441dbe50 R08: R09: 0001 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525031] R10: 02e2 R11: 029b
[Kernel-packages] [Bug 1785856] Re: hung task flush-zfs
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8 ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1785856 Title: hung task flush-zfs Status in linux package in Ubuntu: Incomplete Bug description: After restoring a snapshot on a running container a hung task task oops trace gets logged for flush-zfs. The command run was: % lxc restore wedgeiq foo1 If the container is not running restoring seems less likely to cause the hung task. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.131.137 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 7 16:03 seq crw-rw 1 root audio 116, 33 Aug 7 16:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 7 16:36:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: NEXCOM NSA-5160 PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic root=/dev/mapper/VG_WARP-WARPDRIVE ro intel_iommu=on net.ifnames=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 23 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/25/2017:svnNEXCOM:pnNSA-5160:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct23:cvrDefaultstring: dmi.product.name: NSA-5160 dmi.product.version: Default string dmi.sys.vendor: NEXCOM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785739] Re: [Regression] APM Merlin boards fail to recover link after interface down/up
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Cosmic) Assignee: dann frazier (dannf) => (unassigned) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => In Progress ** Description changed: [Impact] On an APM Merlin (X-Gene2) board, the onboard 1G interface fails to re-establish link when the interface is brought down and back up. Juju + MAAS provider does this after every install (so to configure a bridge), making this config unusable. This was actually a regression introduced by the fix for LP: #1632739 in 4.4.0-48.69. [Test Case] 1) From a remote system, start a ping to the IP address of the Merlin board's eth0 interface. 2) On the merlin board: sudo ifconfig eth0 down; sudo ifconfig eth0 up 3) Ping should recover, but doesn't [Fix] commit 84a527a41f38a80353f185d05e41b021e1ff672b Author: Shaohui Xie Date: Tue May 10 17:42:26 2016 +0800 - net: phylib: fix interrupts re-enablement in phy_start + net: phylib: fix interrupts re-enablement in phy_start [Regression Risk] + The fix appears to be straightforward - don't enable interrupts on a phy that does not have a valid interrupt. Fixes are upstream, so any regressions should get upstream support for fixing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785739 Title: [Regression] APM Merlin boards fail to recover link after interface down/up 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 Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] On an APM Merlin (X-Gene2) board, the onboard 1G interface fails to re-establish link when the interface is brought down and back up. Juju + MAAS provider does this after every install (so to configure a bridge), making this config unusable. This was actually a regression introduced by the fix for LP: #1632739 in 4.4.0-48.69. [Test Case] 1) From a remote system, start a ping to the IP address of the Merlin board's eth0 interface. 2) On the merlin board: sudo ifconfig eth0 down; sudo ifconfig eth0 up 3) Ping should recover, but doesn't [Fix] commit 84a527a41f38a80353f185d05e41b021e1ff672b Author: Shaohui Xie Date: Tue May 10 17:42:26 2016 +0800 net: phylib: fix interrupts re-enablement in phy_start [Regression Risk] The fix appears to be straightforward - don't enable interrupts on a phy that does not have a valid interrupt. Fixes are upstream, so any regressions should get upstream support for fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785780] 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 1785780 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/1785780 Title: TB 16 issue on Dell Lattitude 7490 with large amount of data Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: Hi. Large amount of data gets corrupted when using the TB16 ethernet port. (rsync synchronization, etc... ) We can confirm this issue on this kernel. Creating new issue as stated in this bug (#1729674) Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On my Fedora is this still an issue even with announced bugfix (link copied from this discussion #78. Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It's fixed by turning the checksum offload off (tested on the Fedora . sudo ethtool --offload enp11s0u1u2 rx off https://bugs.launchpad.net/dell-sputnik/+bug/1729674 related in bugzilla: To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1785780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785780] Re: TB 16 issue on Dell Lattitude 7490 with large amount of data
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785780 Title: TB 16 issue on Dell Lattitude 7490 with large amount of data Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: Hi. Large amount of data gets corrupted when using the TB16 ethernet port. (rsync synchronization, etc... ) We can confirm this issue on this kernel. Creating new issue as stated in this bug (#1729674) Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On my Fedora is this still an issue even with announced bugfix (link copied from this discussion #78. Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It's fixed by turning the checksum offload off (tested on the Fedora . sudo ethtool --offload enp11s0u1u2 rx off https://bugs.launchpad.net/dell-sputnik/+bug/1729674 related in bugzilla: To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1785780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
I confirm this bug on a Asus UX331UAL with Ubuntu 18.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755393] 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 1755393 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755393 Title: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit / ubuntu-18.04-desktop hang Status in linux package in Ubuntu: Incomplete Bug description: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi Reproduce: - 1. create VM with EFI firewall in ESXi 2. install geustOS with ubuntu16.04.4-dsktop-64bit image. 3. reboot it after finish installation 4. edit VM setting and enable hot-add CPU and memory 5. edit VM setting and set default 1 vCPU to 2 6. open a terminal and run script to enable vcpu1: "sudo ~/rescanCpu.sh" 7. check the cpu number with command "cat /proc/cpuinfo" in terminal. but there is not output message for this command. click anywhere on VM desktop, there is no response. It seems like VM hang. From vmware developer's analysis: Looks to me like Ubuntu's problem. It noticed at 566 seconds after boot that CPU1 was hot-added. Then perhaps you run code to online CPU, and doing so ended up with warning at blk-mq.c: Mar 6 17:41:33 vmware-virtual-machine kernel: [ 566.583896] CPU1 has been hot-added Mar 6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing CommAmqpListener Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.431990] SMP alternatives: switching to SMP code Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487612] x86: Booting SMP configuration: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487616] smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.489517] Disabled fast string operations Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.492082] smpboot: CPU 1 Converting physical 2 to logical package 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.493162] Will online and init hotplugged CPU: 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524713] [ cut here ] Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524726] WARNING: CPU: 1 PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 __blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524727] Modules linked in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helpe r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops mptspi mptscsih drm mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi floppy Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525006] CPU: 1 PID: 2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525008] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.7915097.B64.1802282254 02/28/2018 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525013] Workqueue: kblockd blk_mq_run_work_fn Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525016] task: 8ab5326b task.stack: a694441d8000 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525021] RIP: 0010:__blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525023] RSP: 0018:a694441dbe38 EFLAGS: 00010202 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525026] RAX: 0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525028] RDX: 8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525029] RBP: a694441dbe50 R08: R09: 0001 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525031] R10: 02e2 R11: 029b R12: 8ab5310d69c0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525032] R13: 8ab53c662740 R14: 8ab53c668300 R15:
[Kernel-packages] [Bug 1784291] Re: linux-kvm: 4.15.0-1018.18 -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 ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 07. August 2018 18:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 07. August 2018 18:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1784291 Title: linux-kvm: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755384] 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 1755384 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755384 Title: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi Status in linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi. Reproduce: - 1. create VM with default setting in ESXi 6.5 / on-developing ESXi build 7940658 2. install geustOS zyh-ubuntu16.04.4-dsktop-64 image. 3. reboot it after finish installation 4. edit VM setting and enable hot-add CPU and memory 5. open a terminal and type command "ls /sys/devices/system/memory", find memory0 -- memory7 listed. 6. edit VM setting and set default 1024M memory to 2048M 7. type command "ls /sys/devices/system/memory", it still lists memory0-memory7. No more memoryX is added. The hot-add memory can't be recognized. Expect: For step 7, it should list memory8--memory15 when type "ls /sys/devices/system/memory". To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1755384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755393] Re: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit / ubuntu-18.04-desktop hang
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-package (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755393 Title: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit / ubuntu-18.04-desktop hang Status in linux package in Ubuntu: Incomplete Bug description: hot-add CPU cause VM with ubuntu-16.04.4-desktop-64bit hang in ESXi Reproduce: - 1. create VM with EFI firewall in ESXi 2. install geustOS with ubuntu16.04.4-dsktop-64bit image. 3. reboot it after finish installation 4. edit VM setting and enable hot-add CPU and memory 5. edit VM setting and set default 1 vCPU to 2 6. open a terminal and run script to enable vcpu1: "sudo ~/rescanCpu.sh" 7. check the cpu number with command "cat /proc/cpuinfo" in terminal. but there is not output message for this command. click anywhere on VM desktop, there is no response. It seems like VM hang. From vmware developer's analysis: Looks to me like Ubuntu's problem. It noticed at 566 seconds after boot that CPU1 was hot-added. Then perhaps you run code to online CPU, and doing so ended up with warning at blk-mq.c: Mar 6 17:41:33 vmware-virtual-machine kernel: [ 566.583896] CPU1 has been hot-added Mar 6 17:42:17 vmware-virtual-machine CommAmqpListener[2376]: Initializing CommAmqpListener Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.431990] SMP alternatives: switching to SMP code Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487612] x86: Booting SMP configuration: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.487616] smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.489517] Disabled fast string operations Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.492082] smpboot: CPU 1 Converting physical 2 to logical package 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.493162] Will online and init hotplugged CPU: 1 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524713] [ cut here ] Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524726] WARNING: CPU: 1 PID: 2402 at /build/linux-hwe-4GXcua/linux-hwe-4.13.0/block/blk-mq.c:1106 __blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.524727] Modules linked in: vmw_vsock_vmci_transport vsock nls_iso8859_1 vmw_balloon sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helpe r cryptd intel_rapl_perf joydev input_leds serio_raw shpchp vmw_vmci i2c_piix4 nfit tpm_crb mac_hid parport_pc ppdev lp parport autofs4 vmw_pvscsi vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops mptspi mptscsih drm mptbase nvme nvme_core vmxnet3 scsi_transport_spi ahci libahci pata_acpi floppy Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525006] CPU: 1 PID: 2402 Comm: kworker/1:0H Not tainted 4.13.0-36-generic #40~16.04.1-Ubuntu Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525008] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.7915097.B64.1802282254 02/28/2018 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525013] Workqueue: kblockd blk_mq_run_work_fn Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525016] task: 8ab5326b task.stack: a694441d8000 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525021] RIP: 0010:__blk_mq_run_hw_queue+0x7b/0xa0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525023] RSP: 0018:a694441dbe38 EFLAGS: 00010202 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525026] RAX: 0001 RBX: 8ab50b4edc00 RCX: 8ab53c662760 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525028] RDX: 8ab50b9cba60 RSI: 8ab50b4edc40 RDI: 8ab50b4edc00 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525029] RBP: a694441dbe50 R08: R09: 0001 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525031] R10: 02e2 R11: 029b R12: 8ab5310d69c0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525032] R13: 8ab53c662740 R14: 8ab53c668300 R15: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525036] FS: () GS:8ab53c64() knlGS: Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525038] CS: 0010 DS: ES: CR0: 80050033 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525039] CR2: 7ff14dd7ab00 CR3: 1180a002 CR4: 001606e0 Mar 6 17:42:17 vmware-virtual-machine kernel: [ 610.525140] Call Trace: Mar 6 17:42:17 vmware-virtual-machine
[Kernel-packages] [Bug 1774471] Re: Various fixes for CXL kernel module
--- Comment From vajai...@in.ibm.com 2018-08-07 13:50 EDT--- (In reply to comment #10) > This bug is awaiting verification that the kernel in -proposed solves the > problem. Please test the kernel and update this bug with the results. If the > problem is solved, change the tag 'verification-needed-bionic' to > 'verification-done-bionic'. If the problem still exists, change the tag > 'verification-needed-bionic' to 'verification-failed-bionic'. > > If verification is not done by 5 working days from today, this fix will be > dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. Thank you! Have manually verified following patches to be present on Ubuntu-4.17.0-6.7(Cosmic) and 4.15.0-31-generic (Bionic) kernels: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 9a6d2022bacd: cxl: Configure PSL to not use APC virtual machines b6c84ba22ff3: cxl: Disable prefault_mode in Radix mode ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774471 Title: Various fixes for CXL kernel module Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == IBM is requesting the five patches in this pull request to be applied to Bionic. IBM states they patches fix various issues found after the 18.04 kernel freeze. == Regression Potential == Low. Limited to cxl driver. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1774471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780066] Re: [Bionic] Disk IO hangs when using BFQ as io scheduler
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780066 Title: [Bionic] Disk IO hangs when using BFQ as io scheduler Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: When BFQ is used, disk IO will hang some seconds after boot. This was also reported in some public MLs [1][2]. The fix is already in mainline, but it's not available in 4.15. [1] https://lkml.org/lkml/2017/12/1/80 [2] https://groups.google.com/forum/#!topic/bfq-iosched/nB2cVfDMSOU == SRU Justification == Impact: Disk IO hangs several seconds after booting with a bionic Ubuntu kernel Fix: Three patches are cherry-picked for SRU. "block, bfq: add requeue-request hook" is the fix, while the other two are cleanups and make the whole fixes clean cherry-picks. Testcase: Boot the kernel with BFQ as IO scheduler. Risk of Regression: Clean cherry-picks from upstream so the risk should be fairly low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785319] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172692/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172678/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172690/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
[Kernel-packages] [Bug 1785319] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172677/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1784284] Re: linux-oem: 4.15.0-1014.17 -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 ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 07. August 2018 16:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 07. August 2018 16:31 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1784284 Title: linux-oem: 4.15.0-1014.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755384] Re: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755384 Title: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi Status in linux: Confirmed Status in linux package in Ubuntu: New Bug description: hot-add memory can't be recognized for ubuntu-16.04.4-desktop-64 in ESXi. Reproduce: - 1. create VM with default setting in ESXi 6.5 / on-developing ESXi build 7940658 2. install geustOS zyh-ubuntu16.04.4-dsktop-64 image. 3. reboot it after finish installation 4. edit VM setting and enable hot-add CPU and memory 5. open a terminal and type command "ls /sys/devices/system/memory", find memory0 -- memory7 listed. 6. edit VM setting and set default 1024M memory to 2048M 7. type command "ls /sys/devices/system/memory", it still lists memory0-memory7. No more memoryX is added. The hot-add memory can't be recognized. Expect: For step 7, it should list memory8--memory15 when type "ls /sys/devices/system/memory". To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1755384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
@Vasiliy, hopefully by early next week. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: no Would you like LXD to be available over the network? (yes/no) [default=no]: Would you like stale cached images to be updated automatically? (yes/no) [default=yes] Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: Now run the following to launch 48 containers in batches of 12. lxd-benchmark launch --count 48 --parallel 12 In two out of four attempts, I got the kernel errors. I also tried echo 1 >/sys/module/spl/parameters/spl_taskq_kick but did not manage to continue. Include any warning/errors/backtraces from the system logs
[Kernel-packages] [Bug 1785319] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172689/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172675/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172687/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172683/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172682/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** No longer affects: unity-control-center (Ubuntu) ** Description changed: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc.
[Kernel-packages] [Bug 1785319] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172684/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172676/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
[Kernel-packages] [Bug 1785319] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172679/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785856] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785856 Title: hung task flush-zfs Status in linux package in Ubuntu: Confirmed Bug description: After restoring a snapshot on a running container a hung task task oops trace gets logged for flush-zfs. The command run was: % lxc restore wedgeiq foo1 If the container is not running restoring seems less likely to cause the hung task. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.131.137 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 7 16:03 seq crw-rw 1 root audio 116, 33 Aug 7 16:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 7 16:36:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: NEXCOM NSA-5160 PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic root=/dev/mapper/VG_WARP-WARPDRIVE ro intel_iommu=on net.ifnames=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 23 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/25/2017:svnNEXCOM:pnNSA-5160:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct23:cvrDefaultstring: dmi.product.name: NSA-5160 dmi.product.version: Default string dmi.sys.vendor: NEXCOM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785319] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172680/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172673/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172681/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172685/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172686/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172688/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172691/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
Verified passed for Ubuntu Bionic using the reproducer described in comment #1. Marking as verified. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: no Would you like LXD to be available over the network? (yes/no) [default=no]: Would you like stale cached images to be updated automatically? (yes/no) [default=yes] Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: Now run the following to launch 48 containers in batches of 12. lxd-benchmark launch --count 48 --parallel 12 In two out of four attempts, I got the kernel errors. I also tried echo
[Kernel-packages] [Bug 1785319] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172693/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172694/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172695/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
Verified passed for Ubuntu Xenial using the reproducer described in comment #1. Marking as verified. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: no Would you like LXD to be available over the network? (yes/no) [default=no]: Would you like stale cached images to be updated automatically? (yes/no) [default=yes] Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: Now run the following to launch 48 containers in batches of 12. lxd-benchmark launch --count 48 --parallel 12 In two out of four attempts, I got the kernel errors. I also tried echo
[Kernel-packages] [Bug 1785856] Re: hung task flush-zfs
The oops: Aug 7 16:47:42 wedgeamb kernel: [ 2640.306142] INFO: task kworker/u24:1:9703 blocked for more than 120 seconds. Aug 7 16:47:42 wedgeamb kernel: [ 2640.306176] Tainted: P O 4.4.0-131-generic #157-Ubuntu Aug 7 16:47:42 wedgeamb kernel: [ 2640.306204] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 7 16:47:42 wedgeamb kernel: [ 2640.306235] kworker/u24:1 D 880038b1f858 0 9703 2 0x Aug 7 16:47:42 wedgeamb kernel: [ 2640.306245] Workqueue: writeback wb_workfn (flush-zfs-2) Aug 7 16:47:42 wedgeamb kernel: [ 2640.306248] 880038b1f858 2980c1b4a2885446 88085b6b8e00 88085496c600 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306251] 880038b2 88085f2572c0 7fff 880038b1f9c8 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306254] 8184f8e0 880038b1f870 8184f0e5 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306257] Call Trace: Aug 7 16:47:42 wedgeamb kernel: [ 2640.306266] [] ? bit_wait+0x60/0x60 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306270] [] schedule+0x35/0x80 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306273] [] schedule_timeout+0x1b6/0x270 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306330] [] ? rrm_exit+0x48/0x80 [zfs] Aug 7 16:47:42 wedgeamb kernel: [ 2640.306336] [] ? ktime_get+0x3e/0xb0 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306340] [] ? bit_wait+0x60/0x60 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306343] [] io_schedule_timeout+0xa4/0x110 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306347] [] bit_wait_io+0x1b/0x70 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306350] [] __wait_on_bit_lock+0x50/0xb0 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306354] [] __lock_page+0xbb/0xe0 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306359] [] ? autoremove_wake_function+0x40/0x40 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306364] [] write_cache_pages+0x2e0/0x510 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306409] [] ? zpl_write_common_iovec+0xe0/0xe0 [zfs] Aug 7 16:47:42 wedgeamb kernel: [ 2640.306413] [] ? mutex_lock+0x12/0x30 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306448] [] ? rrw_exit+0x60/0x150 [zfs] Aug 7 16:47:42 wedgeamb kernel: [ 2640.306492] [] zpl_writepages+0x94/0x170 [zfs] Aug 7 16:47:42 wedgeamb kernel: [ 2640.306495] [] do_writepages+0x21/0x30 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306499] [] __writeback_single_inode+0x45/0x350 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306503] [] writeback_sb_inodes+0x262/0x600 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306506] [] __writeback_inodes_wb+0x8c/0xc0 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306510] [] wb_writeback+0x259/0x310 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306514] [] wb_workfn+0x19a/0x3a0 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306518] [] process_one_work+0x16b/0x490 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306522] [] worker_thread+0x4b/0x4d0 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306525] [] ? process_one_work+0x490/0x490 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306529] [] kthread+0xe7/0x100 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306532] [] ? kthread_create_on_node+0x1e0/0x1e0 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306535] [] ret_from_fork+0x55/0x80 Aug 7 16:47:42 wedgeamb kernel: [ 2640.306538] [] ? kthread_create_on_node+0x1e0/0x1e0 ** Description changed: After restoring a snapshot on a running container a hung task task oops trace gets logged for flush-zfs. The command run was: % lxc restore wedgeiq foo1 If the container is not running restoring seems less likely to cause the hung task. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.131.137 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Aug 7 16:03 seq - crw-rw 1 root audio 116, 33 Aug 7 16:03 timer + total 0 + crw-rw 1 root audio 116, 1 Aug 7 16:03 seq + crw-rw 1 root audio 116, 33 Aug 7 16:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 7 16:36:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 001 Device 002: ID 8087:8000 Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 8087:8000 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 001: ID 1d6b:0003
[Kernel-packages] [Bug 1785675] Re: Security fix: check if IOMMU page is contained in the pinned physical page
I built a test kernel with commit 76fa4975f3ed. It required commit 1463edca6734d as a prereq. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1785675 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: * If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. * If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785675 Title: Security fix: check if IOMMU page is contained in the pinned physical page Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06 12:27:59 == Please, add the following security fix to the distro kernel: 76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned physical page Also already available in the 4.14 stable tree: 58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned physical page And in the 4.17 stable tree: 970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned physical page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785856] [NEW] hung task flush-zfs
Public bug reported: After restoring a snapshot on a running container a hung task task oops trace gets logged for flush-zfs. The command run was: % lxc restore wedgeiq foo1 If the container is not running restoring seems less likely to cause the hung task. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.131.137 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 7 16:03 seq crw-rw 1 root audio 116, 33 Aug 7 16:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 7 16:36:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: NEXCOM NSA-5160 PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic root=/dev/mapper/VG_WARP-WARPDRIVE ro intel_iommu=on net.ifnames=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 23 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/25/2017:svnNEXCOM:pnNSA-5160:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct23:cvrDefaultstring: dmi.product.name: NSA-5160 dmi.product.version: Default string dmi.sys.vendor: NEXCOM ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Attachment added: "output from ubuntu-bug" https://bugs.launchpad.net/bugs/1785856/+attachment/5172703/+files/apport.linux-image-4.4.0-131-generic.xym7ry1v.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785856 Title: hung task flush-zfs Status in linux package in Ubuntu: Confirmed Bug description: After restoring a snapshot on a running container a hung task task oops trace gets logged for flush-zfs. The command run was: % lxc restore wedgeiq foo1 If the container is not running restoring seems less likely to cause the hung task. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.131.137 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 7 16:03 seq crw-rw 1 root audio 116, 33 Aug 7 16:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 7 16:36:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: NEXCOM NSA-5160 PciMultimedia: ProcEnviron: SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic root=/dev/mapper/VG_WARP-WARPDRIVE ro intel_iommu=on net.ifnames=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No
[Kernel-packages] [Bug 1784291] Re: linux-kvm: 4.15.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784291 Title: linux-kvm: 4.15.0-1018.18 -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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1777338 Can you test this kernel and see if it resolves this bug? If this kernel also fixes the bug, I'll submit an SRU request. Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Tested today. All OK. Tag updated.
The installation wasn't trivial, since even with an apply-all proposed
the image wasn't installed. I had to explicitly select it (using
synaptic).
I was also somewhat alarmed that two linux packages had to be removed.
However, all seems well and I've removed mainline 4.16.9.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
[Kernel-packages] [Bug 1785319] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172670/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172674/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1785319] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172672/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1785319/+attachment/5172671/+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/1785319 Title: All kinds of problems on wake from lid close 18.04 Status in linux package in Ubuntu: Confirmed Bug description: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1383 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-26 (103 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. XPS 15 9560 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1785319] Re: All kinds of problems on wake from lid close 18.04
apport information ** Tags added: apport-collected bionic ** Description changed: This seems to be multiple packages, Ubuntu 18.04 itself (because 17.10 and all previous versions worked fine), and firmware. When wake from lid close, GUI freezes up and un-freezes every few seconds. Wifi won't even scan for networks, much less join one. Probably more things are wrong, but that's what's visible to me. Here's dmesg recent errors: [43548.249307] ath10k_warn: 129 callbacks suppressed [43548.249309] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.285609] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.316369] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.347057] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.382893] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.419305] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.455788] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.492277] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.523109] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43548.553793] ath10k_pci :02:00.0: failed to wake target for read32 at 0x0003a028: -110 [43551.161054] ath10k_pci :02:00.0: failed to read device register, device is gone [43551.270391] ath10k_pci :02:00.0: firmware crashed! (guid c2f1d8ad-ba2b-4c87-a0e1-9dff072ac468) [43551.270394] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [43551.270396] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43551.270803] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [43551.271233] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [43551.271235] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43551.271242] ath10k_pci :02:00.0: failed to read firmware dump area: -28 [43551.271243] ath10k_pci :02:00.0: Copy Engine register dump: [43551.417001] ath10k_pci :02:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295 [43551.562682] ath10k_pci :02:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295 [43551.708407] ath10k_pci :02:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295 [43551.841610] ath10k_pci :02:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295 [43551.975925] ath10k_pci :02:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295 [43552.108938] ath10k_pci :02:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295 [43552.254895] ath10k_pci :02:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295 [43552.400652] ath10k_pci :02:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295 [43552.400689] ath10k_pci :02:00.0: failed to reset chip: -5 [43552.400690] ath10k_pci :02:00.0: Could not init hif: -5 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: tom1383 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-26 (103 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) + MachineType: Dell Inc. XPS 15 9560 + 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 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash acpi_rev_override=5 nouveau.modeset=0 enable_psr=1 disable_power_well=0 pci=noaer pcie_aspm=force nmi_watchdog=0 nouveau.runpm=0 vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-30-generic N/A + linux-backports-modules-4.15.0-30-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/23/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.9.4 + dmi.board.name: 0JHP5H + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
[Kernel-packages] [Bug 1772516] Re: [Config] enable EDAC_DEBUG on ARM64
This is fix released for Cosmic and NACked for Bionic. Marking the bionic track as won't fix. ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772516 Title: [Config] enable EDAC_DEBUG on ARM64 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Won't Fix Status in linux source package in Cosmic: Fix Released Bug description: [Impact] Testing EDAC requires EDAC_DEBUG to be enabled. ARM64 server customers currently need to rebuild Ubuntu kernels with this config option to test EDAC support. [Fix] Enable EDAC_DEBUG config option in the kernel. [Test] [Regression Potential] None. Limited to ARM64 architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
I can confirm now that fix works for me. Do somebody knows when this kernel and zfsutils package will move from proposed to updates? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: no Would you like LXD to be available over the network? (yes/no) [default=no]: Would you like stale cached images to be updated automatically? (yes/no) [default=yes] Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: Now run the following to launch 48 containers in batches of 12. lxd-benchmark launch --count 48 --parallel 12 In two out of four attempts, I got the kernel errors. I also tried echo 1 >/sys/module/spl/parameters/spl_taskq_kick but
[Kernel-packages] [Bug 1784292] Re: linux-azure: 4.15.0-1020.20~16.04.1 -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/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 07. August 2018 16:03 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 07. August 2018 16:03 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1784292 Title: linux-azure: 4.15.0-1020.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784285] Re: linux-aws: 4.15.0-1018.18 -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/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 07. August 2018 16:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 07. August 2018 16:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1784285 Title: linux-aws: 4.15.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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 snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1784281 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
