[Kernel-packages] [Bug 1855999] [NEW] alsa/hda/realtek: the line-out jack doens't work on a dell AIO
Public bug reported: [Impact] This is from an OEM bug, the line-out jack doesn't work on a Dell AIO machine. [Fix] apply the fixup ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, and make the matching more generic. [Test Case] Booting the kernel with this patch, the line-out jack worked well. [Regression Risk] Low, just apply an existing fixup to a specific machine (dell with alc274 codec, and the pin 0x19 and 0x1a has the 0x4000 configuration). ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1855045 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1855045 somerville ** Description changed: - this bug is for tracking purpose + [Impact] + This is from an OEM bug, the line-out jack doesn't work on a Dell + AIO machine. + + [Fix] + apply the fixup ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, and make the + matching more generic. + + [Test Case] + Booting the kernel with this patch, the line-out jack worked well. + + [Regression Risk] + Low, just apply an existing fixup to a specific machine (dell with alc274 + codec, and the pin 0x19 and 0x1a has the 0x4000 configuration). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855999 Title: alsa/hda/realtek: the line-out jack doens't work on a dell AIO Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] This is from an OEM bug, the line-out jack doesn't work on a Dell AIO machine. [Fix] apply the fixup ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, and make the matching more generic. [Test Case] Booting the kernel with this patch, the line-out jack worked well. [Regression Risk] Low, just apply an existing fixup to a specific machine (dell with alc274 codec, and the pin 0x19 and 0x1a has the 0x4000 configuration). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855999] 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 1855999 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/1855999 Title: alsa/hda/realtek: the line-out jack doens't work on a dell AIO Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] This is from an OEM bug, the line-out jack doesn't work on a Dell AIO machine. [Fix] apply the fixup ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, and make the matching more generic. [Test Case] Booting the kernel with this patch, the line-out jack worked well. [Regression Risk] Low, just apply an existing fixup to a specific machine (dell with alc274 codec, and the pin 0x19 and 0x1a has the 0x4000 configuration). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855998] 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/1855998 Title: package linux-image-5.3.0-24-generic 5.3.0-24.26 failed to install/upgrade: installed linux-image-5.3.0-24-generic package post- installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: root@:/var/lib/dpkg/info# apt install linux-image-5.3.0-24-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-modules-5.3.0-24-generic Suggested packages: fdutils linux-doc-5.3.0 | linux-source-5.3.0 linux-tools The following NEW packages will be installed: linux-image-5.3.0-24-generic linux-modules-5.3.0-24-generic 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 22.8 MB of archives. After this operation, 83.1 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ae.archive.ubuntu.com/ubuntu eoan-updates/main amd64 linux-modules-5.3.0-24-generic amd64 5.3.0-24.26 [14.2 MB] Get:2 http://ae.archive.ubuntu.com/ubuntu eoan-updates/main amd64 linux-image-5.3.0-24-generic amd64 5.3.0-24.26 [8,656 kB] Fetched 22.8 MB in 2min 34s (148 kB/s) Selecting previously unselected package linux-modules-5.3.0-24-generic. dpkg: warning: files list file for package 'linux-modules-5.3.0-19-generic' missing; assuming package has no files currently installed dpkg: warning: files list file for package 'linux-headers-5.3.0-19-generic' missing; assuming package has no files currently installed dpkg: warning: files list file for package 'linux-headers-5.3.0-19' missing; assuming package has no files currently installed (Reading database ... 242579 files and directories currently installed.) Preparing to unpack .../linux-modules-5.3.0-24-generic_5.3.0-24.26_amd64.deb ... Unpacking linux-modules-5.3.0-24-generic (5.3.0-24.26) ... Selecting previously unselected package linux-image-5.3.0-24-generic. Preparing to unpack .../linux-image-5.3.0-24-generic_5.3.0-24.26_amd64.deb ... Unpacking linux-image-5.3.0-24-generic (5.3.0-24.26) ... Setting up linux-modules-5.3.0-24-generic (5.3.0-24.26) ... Setting up linux-image-5.3.0-24-generic (5.3.0-24.26) ... Failed to create symlink to vmlinuz-5.0.0-32-generic: Operation not permitted at /usr/bin/linux-update-symlinks line 64. dpkg: error processing package linux-image-5.3.0-24-generic (--configure): installed linux-image-5.3.0-24-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.3.0-24-generic E: Sub-process /usr/bin/dpkg returned an error code (1) root@raad-N56VZ:/var/lib/dpkg/info# ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: linux-modules-5.3.0-24-generic:amd64: Install linux-image-5.3.0-24-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raad 2841 F pulseaudio /dev/snd/controlC0: raad 2841 F pulseaudio Date: Wed Dec 11 15:32:46 2019 ErrorMessage: installed linux-image-5.3.0-24-generic package post-installation script subprocess returned error exit status 1 MachineType: ASUSTeK COMPUTER INC. N56VZ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/installs/ubuntu/vmlinuz-5.0.0-32-generic root=/dev/mapper/linux-ubuntu_root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1 SourcePackage: linux Title: package linux-image-5.3.0-24-generic 5.3.0-24.26 failed to install/upgrade: installed linux-image-5.3.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-11-12 (28 days ago) dmi.bios.date: 05/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag
[Kernel-packages] [Bug 1853378] Re: [amdgpu] ryzen 2500u random Xorg freeze
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc1/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853378 Title: [amdgpu] ryzen 2500u random Xorg freeze Status in linux package in Ubuntu: Confirmed Bug description: Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of ram on a pcie nvme ssd. PC randomly freezes at times. This actually occurs on asus x505za also running 2500u. I checked the log files and there was this error. [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654 I think it may be a problem with gnome since I was running lubuntu before and there's no hang whatsoever when using that. Ubuntu 18.04.3 LTS Release 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.3.12-050312-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 07:04:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Dell Vega [Radeon Vega 8 Mobile] [1028:08d7] InstallationDate: Installed on 2019-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3585 ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.12-050312-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash idle=nomwait iommu=soft pci=nomsi vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.asset.tag: not specified dmi.board.name: 0TY9XW dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.0 dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/29/2019:svnDellInc.:pnInspiron3585:pvr1.4.0:rvnDellInc.:rn0TY9XW:rvrX01:cvnDellInc.:ct10:cvr1.4.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3585 dmi.product.sku: 08D7 dmi.product.version: 1.4.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git1911150630.a39c34~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.0~git1911201930.bcfc9c~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.0~git1911201930.bcfc9c~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855059] Re: [Regression] 4.15.0-73.82 Can not boot ThunderX
This is the true fix for the issue: https://git.launchpad.net/~kerneltoast/+git/bionic- linux/commit/?id=4d161b28e6bd713f53d9097a6c74d3cb201c1363 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855059 Title: [Regression] 4.15.0-73.82 Can not boot ThunderX Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Bug description: On ThunderX 1socket system. The kernel output log https://pastebin.ubuntu.com/p/35DGgPz5N4/ On ThunderX 2socket system, The kernel output log https://pastebin.ubuntu.com/p/T3fVzwxhmt/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
This patch fixes this issue: https://git.launchpad.net/~kerneltoast/+git /bionic-linux/commit/?id=4d161b28e6bd713f53d9097a6c74d3cb201c1363 Note that this issue is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855059. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: Confirmed Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Packaging - phase-changed: Wednesday, 04. December 2019 19:02 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 11. December 2019 08:11 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 11. December 2019 08:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
rojer and Jonathan, Do those systems use s2idle by default? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Triaged Bug description: With this message the only way to resume work is to reboot the system using power button. With kernel linux-image-5.3.0-13-generic everything is OK. Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still happens in linux-image-5.3.0-18-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: player 4451 F pulseaudio /dev/snd/controlC1: player 4451 F pulseaudio /dev/snd/controlC0: player 4451 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 14 01:27:04 2019 HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e MachineType: LENOVO 20BG0016US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current loglevel=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago) WifiSyslog: dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.sku: LENOVO_MT_20BG dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO, but disabling swap fixes it
According to the description there's no swap in the end, so I think it's like discussion in [1]. So yes, I think it's still a kernel bug. For desktop usage, [2] [3] are mentioned by dsd in the discussion. Maybe we can adopt those daemon as an OOM killer for desktops. [1] https://lkml.org/lkml/2019/8/4/15 [2] https://github.com/endlessm/eos-boot-helper/blob/master/psi-monitor/psi-monitor.c [3] https://gitlab.freedesktop.org/hadess/low-memory-monitor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO, but disabling swap fixes it Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default s
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Update: I managed to revert my kernel to 4.15.0-70-generic through the bootloader menu that appears at the start of my laptop, and my touchpad has started working again. I'll keep using this version until a stable fix is pushed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Ha
[Kernel-packages] [Bug 1848953] Re: Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in Ubuntu 19.10
@Serghei and @John Brown - I am curious, in your proprietary drivers list (Additional Drivers), do you have the Intel card active and enabled? In my laptop, Intel 3165 is grayed and bellow it, it says The device is not working; the checkbox is on Do not use this device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848953 Title: Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in Ubuntu 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I have a clean install of the latest Ubuntu, 19.10, but since the live usb, a bug appeared. I could not login to the 2.4 GHz Wifi network at home with the fresh installed Ubuntu, it says the password is wrong, but it is not. I have Dual Band Intel AC 3165 it seems. My card appears in the Additional Drivers list with the notice that the device is not working. I can connect the 5 GHz wifi, but not the 2.4 GHz. See the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: florin 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 22:49:04 2019 InstallationDate: Installed on 2019-10-19 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5652 IMC Networks TOSHIBA Web Camera - HD Bus 001 Device 006: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE P50-C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=0b07e060-55a5-4186-8670-bce4c230e596 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.50 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE P50-C dmi.product.sku: PSPUFE dmi.product.version: PSPUFE-001009G6 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856010] [NEW] xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite
Public bug reported: These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually: So there must be some test in net that will cause this. >From the test result it looks like the test was executed in the following >sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed Dec 11 06:42:39 2019 Ec2AMI: ami-047cec24582f6ae0d Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 apport-bug arm64 aws ec2-images eoan package-from-proposed sru-20191202 ubuntu-kernel-selftests -- 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/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually: So there must be some test in net that will cause this. From the test result it looks like the test was executed in the following sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed
[Kernel-packages] [Bug 1855978] Re: linux-firmware updates breaks Intel 9260 on Bionic
downgrading linux-firmware to 1.713.12 fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1855978 Title: linux-firmware updates breaks Intel 9260 on Bionic Status in linux-firmware package in Ubuntu: Triaged Bug description: Bug 1852512 pulls new firmware blobs for 5.3 hwe kernel upgrade, and iwlwifi-9260-th-b0-jf-b0-46.ucode is included. This new version doesn't seem to be compatible with Bionic OEM kernels, and will fail WiFi initialization leaving the system booted without wireless connection. The previous version (1.173.12) has iwlwifi-9260-th-b0-jf-b0-43.ucode instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.13 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Dec 11 14:18:01 2019 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 InstallationDate: Installed on 2019-07-11 (152 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1855978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: sru-20191202 ** Tags added: 5.3 aws ubuntu-kernel-selftests -- 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/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually: So there must be some test in net that will cause this. From the test result it looks like the test was executed in the following sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed Dec 11 06:42:39 2019 Ec2AMI: ami-047cec24582f6ae0d Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it
** Changed in: kunpeng920/ubuntu-19.10 Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04 series: Triaged Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Triaged Status in kunpeng920 ubuntu-19.10 series: Triaged Status in kunpeng920 ubuntu-20.04 series: Triaged Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 8c39673d5474b scsi: hisi_sas: Check sas_port before using it [Regression Risk] Patch restricted to hisi_sas driver. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855628] 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 1855628 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/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855628/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855619] Re: Touchpad not working Eoan
Is "advanced functions" an option in the BIOS? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855619 Title: Touchpad not working Eoan Status in linux package in Ubuntu: Confirmed Bug description: My laptop is an Acer Aspire F5-571. It doesn't detect my touchpad when I decided to install Ubuntu 19.10. I have disabled advanced functions of the touchpad (because I think it had issues with I2C). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barrosorbf 1326 F pulseaudio /dev/snd/controlC0: barrosorbf 1326 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:10:38 2019 InstallationDate: Installed on 2019-12-08 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire F5-571 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=53242bb9-2591-4fba-b598-04911527760d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireF5-571:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire F5-571 dmi.product.sku: Aspire F5-571_098A_1_37 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4
Hmm, there are no dmesg attached. Can you please perform a kernel bisection? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843375] Re: Hibernation doesn't work ub 4.15.0-62
Please try 4.15.0-73. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843375 Title: Hibernation doesn't work ub 4.15.0-62 Status in linux package in Ubuntu: Expired Bug description: 4.0.15-58 works properly, but 4.15.0-60 and 4.15.0-62 have lost this functionality in "update" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Can you attach `journalctl -b -1 -k` at the next boot of freeze? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855312] Re: Fix unusable USB hub on Dell TB16 after S3
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Disco) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1855312 Title: Fix unusable USB hub on Dell TB16 after S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: In Progress Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] Sometimes USB hub on Dell TB16 stop working after S3. [Fix] Attempt to power cycle USB device when a it's stuck at eSS.Disabled state, it's basically not recoverable. [Test] After applying the patch, USB ports and USB ethernet are still working after 100 times S3 stress test. [Regression Potential] Low. This is a last resort attempt, in most cases this code path won't be reached. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Hi Matthew, Great Thanks Matthew, waiting for updates from you :). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854842 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1854842 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, there is a kernel splat when sending large IP packets which have padding at the end. enp6s0f0: hw csum failure CPU: 19 PID: 0 Comm: swapper/19 Not tainted 4.15.0-72-generic Call Trace: dump_stack+0x63/0x8e netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xbc/0xd0 nf_ip_checksum+0xc3/0xf0 icmp_error+0x27d/0x310 [nf_conntrack_ipv4] nf_conntrack_in+0x15a/0x510 [nf_conntrack] ? __skb_checksum+0x68/0x330 ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xc0 ? skb_send_sock+0x50/0x50 ip_rcv+0x301/0x360 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x432/0xb80 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xe0 napi_gro_receive+0xc5/0xf0 mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core] ? enqueue_task_rt+0x1b4/0x2e0 mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] net_rx_action+0x140/0x3a0 __do_softirq+0xe4/0x2d4 irq_exit+0xc5/0xd0 do_IRQ+0x86/0xe0 common_interrupt+0x8c/0x8c This bug is a further attempt to fix these splats, as there has been previous fixes in LP #1840854 and a series of commits which landed in 4.15.0-67 (LP #1847155) as a part of upstream -stable patches. This bug will also fix the same problems on the new Mellanox CX6 and Bluefield hardware, which has been enabled already via previous upstream -stable patches which landed in LP #1847155. [Fix] This particular issue was fixed for Mellanox series 5 drivers in the following commits: commit 0aa1d18615c163f92935b806dcaff9157645233a Author: Saeed Mahameed Date: Tue Mar 12 00:24:52 2019 -0700 Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding This commit required a minor backport. This commit was selected for upstream -stable in 4.19.76 and 5.0.10. This commit appears to be omitted from "Bionic update: upstream stable patchset 2019-10-07", which is LP #1847155, probably due to requiring a backport. commit db849faa9bef993a1379dc510623f750a72fa7ce Author: Saeed Mahameed Date: Fri May 3 13:14:59 2019 -0700 Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware This commit required a minor backport. This commit was selected for upstream -stable in 5.1.21 and 5.2.4. This commit has already been applied to the disco kernel, as part of stable updates. [Testcase] The following scapy script will reproduce this issue. Run from the machine with the Mellanox series 5 NIC: 1) a=Ether(dst='ff:ff:ff:ff:ff:ff')/IP(dst='127.0.0.1')/ICMP()/Padding(load='\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe') 2) sendp(a, iface='enp6s0f0') 3) Check dmesg on the reciever side. The example uses localhost, so check dmesg. I have built some test kernels, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test This kernel contains 0aa1d18615c163f92935b806dcaff9157645233a. and https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test-2 This kernel contains db849faa9bef993a1379dc510623f750a72fa7ce. If you install the test kernels the issue is resolved. [Regression Potential] The changes are limited to the mlx5_core driver, and only modify how packet checksums are calculated when padding is involved. Both patches have been accepted and published by upstream -stable, and are widely accepted by the community. Because of this, I believe the risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** 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/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855628/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855978] Re: linux-firmware updates breaks Intel 9260 on Bionic
Emergency work-around steps: 1. remove the problematic firmware manually: $ sudo mv /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode $HOME 2. reload the iwlwifi: $ sudo modprobe -r iwlwifi; sudo modprobe -r iwlwifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1855978 Title: linux-firmware updates breaks Intel 9260 on Bionic Status in linux-firmware package in Ubuntu: Triaged Bug description: Bug 1852512 pulls new firmware blobs for 5.3 hwe kernel upgrade, and iwlwifi-9260-th-b0-jf-b0-46.ucode is included. This new version doesn't seem to be compatible with Bionic OEM kernels, and will fail WiFi initialization leaving the system booted without wireless connection. The previous version (1.173.12) has iwlwifi-9260-th-b0-jf-b0-43.ucode instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.13 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Dec 11 14:18:01 2019 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 InstallationDate: Installed on 2019-07-11 (152 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1855978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D
Spotted on E-5.3 AWS ARM64 instance a1.large, passed on the other 2 ARM64 instances. ** Tags added: 5.3 aws eoan sru-20191202 ** Tags added: arm64 ** Summary changed: - memcg_subgroup_charge from controllers in ubuntu_ltp failed on D + memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1847982 Title: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: New Status in linux-kvm source package in Disco: New Status in linux-oracle source package in Disco: New Bug description: Issue found on Azure Disco kernel 5.0.0-1023.24 Failed on instance: * Standard_GS2 * Standard_D16s_v3 Passed on instance: * Standard_F32s_v2 * Standard_L8s_v2 * Standard_L4s * Standard_L8s_v2 (Although it has passed on these instances, but they all have the same test output, just the pids are different) Test failed with: /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no cu=7 cs=11 startup='Sat Oct 5 01:44:03 2019' memcg_subgroup_charge 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 1 TINFO: Warming up pid: 119041 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041 memcg_subgroup_charge 1 TPASS: rss is 135168 as expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 3 TINFO: Warming up pid: 119071 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071 memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected memcg_subgroup_charge 4 TPASS: rss is 0 as expected memcg_subgroup_charge 5 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 5 TINFO: Warming up pid: 119094 memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094 memcg_subgroup_charge 5 TPASS: rss is 135168 as expected memcg_subgroup_charge 6 TPASS: rss is 0 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1847982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO, but disabling swap fixes it
sorry... I think the only kernel yet that did not suffer was https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ 5.4.0-997_5.4.0-997 will try 5.5-rc1 [1] is not totally equal, but may be related. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO, but disabling swap fixes it Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO, but disabling swap fixes it
There is for sure a bug. As I said, I know how a system behaves that is suffering from too much swapping. My case is far worse. and still, about once a day the GUI is completely locked. this cannot be explained from swapping and cannot be solved by disabling swap. I think the only kernel yet that did not suffer was -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO, but disabling swap fixes it Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: com
[Kernel-packages] [Bug 1855564] Re: system load gradually increase, until a forced shutdown kernel 5.3.0-23 and above
Please test 5.3.0-25.27 in proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855564 Title: system load gradually increase, until a forced shutdown kernel 5.3.0-23 and above Status in linux package in Ubuntu: Confirmed Bug description: There is no issues with kernel 5.3.0-19. the issue is from kernel 5.3.0-23 and above. 20-22 were not tested. The freeze is related to nvme drive access. it can be tested with the following command. sudo /usr/sbin/grub-probe --device /dev/nvme1n1p2 --target=fs_uuid This command freezes on kernel with the bug. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:01:27 2019 HibernationDevice: RESUME=UUID=24dfd8ad-f9e6-4f3a-87bd-32549cf5ba9b InstallationDate: Installed on 2014-04-18 (2059 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7A95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=79eaf8ba-9463-4191-9bfb-30f8b81ed108 ro intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-27 (41 days ago) dmi.bios.date: 07/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.90 dmi.board.asset.tag: Default string dmi.board.name: X299 GAMING PRO CARBON AC (MS-7A95) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd07/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX299GAMINGPROCARBONAC(MS-7A95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A95 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-09-06T20:58:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0
Issue found on E-AWS ARM64 instance a1.medium. Passed on the other 2 ARM64 instances. ** Tags added: sru-20191202 ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- 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/1854722 Title: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: Kernel: 5.0.0-1022.25~18.04.1 Issue found on instance t2.small The test failed with ENOMEM startup='Wed Nov 20 10:40:07 2019' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12) Summary: passed 0 failed 0 skipped 0 warnings 0 tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
Yes, it's in v5.5-rc1 now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu Status in linux package in Ubuntu: Confirmed Bug description: I have one laptop with Realtek RTL8723BU wifi card. It runs, but signal is weak (it only works if the router is less than a meter away), and even if it gets signal it's slow and it gets interrupted frequently. In windows it works normally, and with a much stronger signal. I tested it on Ubuntu 18.04.3 and 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854329] Re: Synaptics Touchpad "loosing sync" on HP laptop
Can you please attach dmesg? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854329 Title: Synaptics Touchpad "loosing sync" on HP laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with the touchpad on HP 15-db1041nm (AMD Ryzen 5 3500U). The touchpad freezes for a few seconds then resumes working. There are also freezes when typing where letters repeat, so instead of the letter r i get r. This may be a different and unrelated bug which I will open, but I'm mentioning as the built-in keyboard could be attached to the same bus? This is similar to bug #1803171, but on HP. I was instructed to report a new bug. Attached is dmesg | grep psmouse showing the sync problems that appear. Description: Ubuntu 19.10 Release: 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) Tags: eoan Uname: Linux 5.4.0-050400-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: milan 951 F pulseaudio /dev/snd/controlC0: milan 951 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: HP HP Laptop 15-db1xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c6d5dded-989d-4d10-a52c-4e53aaaba9d2 ro mitigations=off quiet splash mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/27/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85EA dmi.board.vendor: HP dmi.board.version: 51.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db1xxx dmi.product.sku: 6VK24EA#BED dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854896] Re: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Same problem here with Synaptics TM3336-002 using kernel: 4.15.0-72. How can I go back to kernel 4.15.0-70 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854896 Title: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic Status in linux package in Ubuntu: Incomplete Bug description: Please see to it, my touchpad all of a sudden stopped working after reboot. it happened after updating to the latest kernel 4.15.0-72, i am using linux mint 19.2. Pointer version: Synaptics TM3336-004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855978] Re: linux-firmware updates breaks Intel 9260 on Bionic
So this issue happens on 9260 platforms with OEM DKMS modules that are not compatible with -46 fw. Luckily(?) enough, we have another regression in bug 1855825 that we're planning to fix those DKMS with same version used in Eoan, which happens to be compatible with -46 fw per my local test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1855978 Title: linux-firmware updates breaks Intel 9260 on Bionic Status in linux-firmware package in Ubuntu: Triaged Bug description: Bug 1852512 pulls new firmware blobs for 5.3 hwe kernel upgrade, and iwlwifi-9260-th-b0-jf-b0-46.ucode is included. This new version doesn't seem to be compatible with Bionic OEM kernels, and will fail WiFi initialization leaving the system booted without wireless connection. The previous version (1.173.12) has iwlwifi-9260-th-b0-jf-b0-43.ucode instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.13 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Dec 11 14:18:01 2019 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 InstallationDate: Installed on 2019-07-11 (152 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1855978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855817] Re: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP
This issue can be found on E-AWS, but just on the following instances: * m4.large * m5a.large * t2.small * t3.medium ** Tags added: aws -- 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/1855817 Title: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP startup='Sat Dec 7 10:43:06 2019' signal06 0 TINFO : loop = 10771 signal06 1 TFAIL : signal06.c:87: Bug Reproduced! tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854755] Re: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 10. December 2019 13:21 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1854755 Title: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 10. December 2019 13:21 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812620] Re: msg_zerocopy in net from ubuntu_kernel_selftests failed
Found on E-AWS 5.3.0-1009.10-aws Test passed with ARM64 instances a1.2xlarge but failed on the other 2, this issue can be found on AMD64 instances as well. ** Tags added: sru-20191202 -- 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/1812620 Title: msg_zerocopy in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: New Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Bug description: This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850653] Re: realmode in ubuntu_kvm_unit tests fails
** Tags added: sru-20191202 ** Tags added: aws -- 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/1850653 Title: realmode in ubuntu_kvm_unit tests fails Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-azure source package in Eoan: New Bug description: Kernel: 5.3 Cloud: Azure Test: ubuntu_kvm_unit_tests realmode fails in the 5.3 kernel on Azure, I believe this may have something to do with the instances as we don't see this failure on other clouds. Only in a few cases on AWS, on baremetal. 10/25 13:50:31 DEBUG| utils:0116| Running 'kvm-ok' 10/25 13:50:31 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists 10/25 13:50:31 DEBUG| utils:0153| [stdout] KVM acceleration can be used 10/25 13:50:31 DEBUG| utils:0116| Running '/home/azure/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/realmode' 10/25 13:50:31 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4 10/25 13:50:32 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.QHy5F7j43j -smp 1 # -initrd /tmp/tmp.9RnyRFe5YU 10/25 13:50:32 DEBUG| utils:0153| [stderr] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: null 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: shld 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 5 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 6 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop with high bits set in %esp 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pusha/popa 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pusha/popa 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 5 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cmp 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cmp 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cmp 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: add 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: add 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 5 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 6 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: clc 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: stc 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cli 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sti 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cld 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: std 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz short 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz short 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jmp short 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz near 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz near 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jmp near 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call near 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call near 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call far 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call far 2 10/25 13:50:33 DEBUG| utils:0153| [
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Tags added: kernel-unblock-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Friday, 06. December 2019 14:01 UTC reason: promote-to-proposed: Stalled -- another kernel is currently pending in Signing variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes
Found on E-AWS c5.metal (5.3.0-1009.10) ** Tags added: 1202 ** Tags removed: 1202 ** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: New Bug description: <<>> incrementing stop Name: cpuhotplug03 Date: Thu Jul 11 08:31:48 UTC 2019 Desc: Do tasks get scheduled to a newly on-lined CPU? CPU is 1 sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 4642 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4643 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4644 0.0 0.0 2020 468 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4645 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4646 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4647 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4648 0.0 0.0 2020 456 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4649 0.0 0.0 2020 508 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4650 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4651 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4652 0.0 0.0 2020 484 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4653 0.0 0.0 2020 496 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4654 0.0 0.0 2020 464 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4655 0.0 0.0 2020 492 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4656 0.0 0.0 2020 448 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4657 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4661 0.0 0.0 7540 648 pts/0S08:31 0:00 grep cpuhotplug_do_spin_loop cpuhotplug03 1 TINFO: Onlining CPU 1 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=1060 cstime=9 <<>> Test passed on ThunderX ARM64, probably a test case issue. Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDe
[Kernel-packages] [Bug 1845863] Re: vma05 in mm from ubuntu_ltp failed on B-hwe-edge 5.3
Found on E-AWS 5.3 (5.3.0-1009.10) across all AMD64 instances (not on ARM64 instances) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1845863 Title: vma05 in mm from ubuntu_ltp failed on B-hwe-edge 5.3 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oracle package in Ubuntu: New Bug description: Test failed with: tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 Need to check if it has something to do with AppArmor startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854746] Re: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker
5.3.0-1009.10 - aws Regression test CMPL, RTB. Issue to note in arm64 (aws): ubuntu_kernel_selftests - test_blackhole_dev in net (bug 1851619) ip_defrag.sh in net (bug 1826848) frm_policy.sh / pmtu.sh / udpgso_bench.sh timeout in net (bug 1856010) msg_zerocopy in net (bug 1812620) ubuntu_ltp - proc01 (bug 1829849) mtest06 (bug 1854722) cpuacct_100_100 (bug 1829978) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) memcg_subgroup_charge (bug 1847982) hugemmap01 (bug 1851777) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh in commands (bug 1853610) getaddrinfo_01 (bug 1829995) ubuntu_ltp_syscalls - msgstress03 on some nodes (bug 1783881) Skipped / blacklisted: * iosched_bugs * libhugetlbfs * tsc * ubuntu_32_on_64 * ubuntu_seccomp * ubuntu_sysdig_smoke_test Issue to note in x86_64 (aws): tsc - failed on c5.metal, i3.metal (bug 1851607) ubuntu_kernel_selftests - test_blackhole_dev in net (bug 1851619) ip_defrag.sh in net (bug 1826848) frm_policy.sh / pmtu.sh / udpgso_bench.sh timeout in net (bug 1856010) msg_zerocopy in net (bug 1812620) ubuntu_kvm_unit_tests - realmode (bug 1850653) vmx (bug 1821394) vmx_apicv_test (bug 1827866) failed on bare-metal nodes ubuntu_ltp - proc01 (bug 1829849) vma05 (bug 1845863) cpuacct_100_100 (bug 1829978) cpuset_hotplug (bug 1834006) cpuset_sched_domains (bug 1830361) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_subgroup_charge (bug 1847982) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cgroup_fj_* failure caused by memcg_test_3 (bug 1836694) cpuhotplug03 (bug 1836167) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh in commands (bug 1853610) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - msgstress03 on some nodes (bug 1783881) signal06 on some instances (bug 1855817) ubuntu_sysdig_smoke_test - test failed with 0 read / write event from dd (bug 1844493) Skipped / blacklisted: * libhugetlbfs ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854746 Title: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1854745 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
"realtime-scheduling = no" no change -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
there is sound after 18.10 (19.04, 19.10) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
it makes sense to wait for the next LTS version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854746] Re: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1854745 variant: debs -- 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/1854746 Title: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1854745 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
Same issue here with Sony WH-1000XM3 and Ubuntu 19.10. When it connects automatically it connects with HSP and I'm not able to select A2DP in Bluez. However when I disconnect the headset using bluez and reconnect it as Audio Sink, it works properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854329] Re: Synaptics Touchpad "loosing sync" on HP laptop
I have attached dmesg | grep psmouse before, this is full dmesg. Currently my laptop's log is being spammed by Realtek WiFi problems, so it's pretty short and includes only a few psmouse parts. ** Attachment added: "dmesg_2019-12-11_11-28.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854329/+attachment/5311721/+files/dmesg_2019-12-11_11-28.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854329 Title: Synaptics Touchpad "loosing sync" on HP laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with the touchpad on HP 15-db1041nm (AMD Ryzen 5 3500U). The touchpad freezes for a few seconds then resumes working. There are also freezes when typing where letters repeat, so instead of the letter r i get r. This may be a different and unrelated bug which I will open, but I'm mentioning as the built-in keyboard could be attached to the same bus? This is similar to bug #1803171, but on HP. I was instructed to report a new bug. Attached is dmesg | grep psmouse showing the sync problems that appear. Description: Ubuntu 19.10 Release: 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) Tags: eoan Uname: Linux 5.4.0-050400-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: milan 951 F pulseaudio /dev/snd/controlC0: milan 951 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: HP HP Laptop 15-db1xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c6d5dded-989d-4d10-a52c-4e53aaaba9d2 ro mitigations=off quiet splash mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/27/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85EA dmi.board.vendor: HP dmi.board.version: 51.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db1xxx dmi.product.sku: 6VK24EA#BED dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854825] Re: xenial/linux-cascade: 4.4.0-1012.14 -proposed tracker
This kernel is not published to the archives, so automated-testing is not applicable. Certification-testing is also not needed. Marking tasks as 'Invalid'. ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854825 Title: xenial/linux-cascade: 4.4.0-1012.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Testing phase-changed: Tuesday, 10. December 2019 13:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854825] Re: xenial/linux-cascade: 4.4.0-1012.14 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Testing phase-changed: Tuesday, 10. December 2019 13:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854825 Title: xenial/linux-cascade: 4.4.0-1012.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Testing phase-changed: Tuesday, 10. December 2019 13:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850653] Re: realmode in ubuntu_kvm_unit tests fails on Eoan
** Summary changed: - realmode in ubuntu_kvm_unit tests fails + realmode in ubuntu_kvm_unit tests fails on Eoan -- 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/1850653 Title: realmode in ubuntu_kvm_unit tests fails on Eoan Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-azure source package in Eoan: New Bug description: Kernel: 5.3 Cloud: Azure Test: ubuntu_kvm_unit_tests realmode fails in the 5.3 kernel on Azure, I believe this may have something to do with the instances as we don't see this failure on other clouds. Only in a few cases on AWS, on baremetal. 10/25 13:50:31 DEBUG| utils:0116| Running 'kvm-ok' 10/25 13:50:31 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists 10/25 13:50:31 DEBUG| utils:0153| [stdout] KVM acceleration can be used 10/25 13:50:31 DEBUG| utils:0116| Running '/home/azure/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/realmode' 10/25 13:50:31 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4 10/25 13:50:32 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.QHy5F7j43j -smp 1 # -initrd /tmp/tmp.9RnyRFe5YU 10/25 13:50:32 DEBUG| utils:0153| [stderr] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: null 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: shld 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 5 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop 6 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: push/pop with high bits set in %esp 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pusha/popa 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pusha/popa 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: mov 5 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cmp 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cmp 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cmp 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: add 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: add 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sub 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: xor 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 3 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 4 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 5 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: pio 6 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: clc 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: stc 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cli 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: sti 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: cld 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: std 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz short 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz short 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jmp short 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz near 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jnz near 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: jmp near 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call near 1 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call near 2 10/25 13:50:33 DEBUG| utils:0153| [stdout] PASS: call far 1 10/25 13:50:33 DEBUG| utils:
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 11. December 2019 08:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 11. December 2019 08:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854755] Re: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Tuesday, 10. December 2019 13:21 UTC + phase: Testing + phase-changed: Wednesday, 11. December 2019 11:16 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1854755 Title: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix 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: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 11. December 2019 11:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure
This failure can be found on Eoan bare metal node fili (5.3.0-25.27) Unhandled exception 13 #GP at ip 004071bf error_code= rflags=00010006 cs=0008 rax=0078 rcx=0809 rdx= rbx=0009 rbp=0047efdf rsi=000a rdi=03fd r8=0042568d r9=03f8 r10=000d r11= r12= r13= r14= r15=00403d36 cr0=80010031 cr2= cr3=00477000 cr4=2020 cr8=0007 STACK: @4071bf 40173d 4004dd FAIL vmx_apicv_test ** Tags added: eoan sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux-oracle source package in Bionic: New Bug description: vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: FAIL vmx_apicv_test (timeout; duration=10) the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 6 10:47:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798358] Re: failed to start KVM with uvtool on P8 Bionic
The error on Eoan 5.3 P8 (node modoc) is:
uvt-kvm create bjf-test release=eoan arch=ppc64el
uvt-kvm: error: libvirt: internal error: qemu unexpectedly closed the
monitor: 2019-10-26T22:05:58.048240Z qemu-system-ppc64le: Requested safe cache
capability level not supported by kvm, try cap-cfpc=broken
uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
uvt-kvm: error: libvirt: Domain not found: no domain with matching name
'bjf-test'
** Summary changed:
- failed to start KVM with uvtool on P8 Bionic
+ failed to start KVM with uvtool on P8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798358
Title:
failed to start KVM with uvtool on P8
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Bug description:
The KVM smoke test failed on P8 systems with Bionic kernel.
75. INFO: /dev/kvm exists
76. KVM acceleration can be used
77. Generating public/private rsa key pair.
78. Your identification has been saved in /home/ubuntu/.ssh/id_rsa.
79. Your public key has been saved in /home/ubuntu/.ssh/id_rsa.pub.
80. The key fingerprint is:
81. SHA256:pN33OKlzvk59wTVkKO0vsWzIkS68IRl8miAc5iS7M9Y ubuntu@entei
82. The key's randomart image is:
83. +---[RSA 2048]+
84. | . .o |
85. | . + . oo |
86. | B . . . + ..|
87. | . + . * o o o. o|
88. | o . o S + = +o |
89. | = E = + = X ..|
90. |. o . + * + .|
91. | ..o.. . |
92. | .=+. |
93. +[SHA256]-+
94. ** ERROR: The codename returned from lsb_release -c was ( ) and we were
expecting 'xenial'
95. stderr:
96. + SUT=bjf-test
97. + SSH_KEY=/home/ubuntu/.ssh/id_rsa
98. + SSH_OPTIONS='-o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
99. + DISTRO=xenial
100. + ARCHITECTURE=ppc64el
101. + '[' -z ppc64el ']'
102. + kvm-ok
103. + '[' 0 '!=' 0 ']'
104. + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
105. + ssh-keygen -f /home/ubuntu/.ssh/id_rsa -t rsa -N ''
106. ++ uvt-simplestreams-libvirt query
107. ++ grep -P 'xenial.*ppc64el'
108. + image=
109. + '[' -z '' ']'
110. + uvt-simplestreams-libvirt sync release=xenial arch=ppc64el
111. + uvt-kvm create bjf-test release=xenial arch=ppc64el
112. + uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
113. uvt-kvm: error: libvirt domain 'bjf-test' is not running.
114. ++ uvt-kvm ip bjf-test
115. uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
116. + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ uname -a
117. ++ cut '-d ' -f 2
118. +++ uvt-kvm ip bjf-test
119. uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
120. ++ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ lsb_release -c
121. + RESULT=
122. + '[' '' '!=' xenial ']'
123. + echo '** ERROR: The codename returned from lsb_release -c was (' ')
and we were expecting '\''xenial'\'''
124. + exit 1
But the test can pass if you run it by hand, it looks like the wait
command needs some time to wait for the KVM to boot.
Maybe we should check this first by adding some sleep command.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 17 10:27 seq
crw-rw 1 root audio 116, 33 Oct 17 10:27 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Oct 17 11:37:34 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB:
ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
ProcLoadAvg: 0.08 0.02 0.01 1/1507 7274
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (User Name 7.3.0-16ubuntu3)) #41-User Name
[Kernel-packages] [Bug 1798358] Re: failed to start KVM with uvtool on P8
BTW this test has passed on the P9 node baltar with the same Eoan
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/1798358
Title:
failed to start KVM with uvtool on P8
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Bug description:
The KVM smoke test failed on P8 systems with Bionic kernel.
75. INFO: /dev/kvm exists
76. KVM acceleration can be used
77. Generating public/private rsa key pair.
78. Your identification has been saved in /home/ubuntu/.ssh/id_rsa.
79. Your public key has been saved in /home/ubuntu/.ssh/id_rsa.pub.
80. The key fingerprint is:
81. SHA256:pN33OKlzvk59wTVkKO0vsWzIkS68IRl8miAc5iS7M9Y ubuntu@entei
82. The key's randomart image is:
83. +---[RSA 2048]+
84. | . .o |
85. | . + . oo |
86. | B . . . + ..|
87. | . + . * o o o. o|
88. | o . o S + = +o |
89. | = E = + = X ..|
90. |. o . + * + .|
91. | ..o.. . |
92. | .=+. |
93. +[SHA256]-+
94. ** ERROR: The codename returned from lsb_release -c was ( ) and we were
expecting 'xenial'
95. stderr:
96. + SUT=bjf-test
97. + SSH_KEY=/home/ubuntu/.ssh/id_rsa
98. + SSH_OPTIONS='-o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
99. + DISTRO=xenial
100. + ARCHITECTURE=ppc64el
101. + '[' -z ppc64el ']'
102. + kvm-ok
103. + '[' 0 '!=' 0 ']'
104. + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
105. + ssh-keygen -f /home/ubuntu/.ssh/id_rsa -t rsa -N ''
106. ++ uvt-simplestreams-libvirt query
107. ++ grep -P 'xenial.*ppc64el'
108. + image=
109. + '[' -z '' ']'
110. + uvt-simplestreams-libvirt sync release=xenial arch=ppc64el
111. + uvt-kvm create bjf-test release=xenial arch=ppc64el
112. + uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
113. uvt-kvm: error: libvirt domain 'bjf-test' is not running.
114. ++ uvt-kvm ip bjf-test
115. uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
116. + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ uname -a
117. ++ cut '-d ' -f 2
118. +++ uvt-kvm ip bjf-test
119. uvt-kvm: error: no IP address found for libvirt machine 'bjf-test'.
120. ++ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@ lsb_release -c
121. + RESULT=
122. + '[' '' '!=' xenial ']'
123. + echo '** ERROR: The codename returned from lsb_release -c was (' ')
and we were expecting '\''xenial'\'''
124. + exit 1
But the test can pass if you run it by hand, it looks like the wait
command needs some time to wait for the KVM to boot.
Maybe we should check this first by adding some sleep command.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 17 10:27 seq
crw-rw 1 root audio 116, 33 Oct 17 10:27 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Oct 17 11:37:34 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB:
ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
ProcLoadAvg: 0.08 0.02 0.01 1/1507 7274
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (User Name 7.3.0-16ubuntu3)) #41-User Name SMP Wed Oct 10
10:57:45 UTC 2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_smt: SMT is off
T
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Tags removed: kernel-unblock-proposed ** Tags added: kernel-unblock-ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. December 2019 11:56 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Holding before Promote to Proposed - phase-changed: Friday, 06. December 2019 14:01 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 11. December 2019 11:56 UTC reason: - promote-to-proposed: Stalled -- another kernel is currently pending in Signing + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. December 2019 11:56 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Promote to Proposed phase-changed: Wednesday, 11. December 2019 12:06 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 11. December 2019 11:56 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 11. December 2019 12:06 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Promote to Proposed phase-changed: Wednesday, 11. December 2019 12:06 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854788] Re: disco/linux: 5.0.0-38.41 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1854787 bionic/linux-hwe: bug 1854785 bionic/linux-oem-osp1: bug 1854786 disco/linux-aws: bug 1854768 disco/linux-azure: bug 1854771 disco/linux-gcp: bug 1854777 disco/linux-kvm: bug 1854778 disco/linux-oracle: bug 1854781 disco/linux-raspi2: bug 1854766 disco/linux-snapdragon: bug 1854784 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854788 Title: disco/linux: 5.0.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1854787 bionic/linux-hwe: bug 1854785 bionic/linux-oem-osp1: bug 1854786 disco/linux-aws: bug 1854768 disco/linux-azure: bug 1854771 disco/linux-gcp: bug 1854777 disco/linux-kvm: bug 1854778 disco/linux-oracle: bug 1854781 disco/linux-raspi2: bug 1854766 disco/linux-snapdragon: bug 1854784 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854778] Re: disco/linux-kvm: 5.0.0-1024.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 04. December 2019 13:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1854778 Title: disco/linux-kvm: 5.0.0-1024.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 04. December 2019 13:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854835] Re: xenial/linux: 4.4.0-171.200 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 04. December 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1854833 trusty/linux-lts-xenial: bug 1854834 unknown/unknown: bug 1854820 xenial/linux-aws: bug 1854824 xenial/linux-cascade: bug 1854825 xenial/linux-fips: bug 1854832 xenial/linux-kvm: bug 1854826 xenial/linux-raspi2: bug 1854829 xenial/linux-snapdragon: bug 1854831 xenial/linux/caracalla-kernel: bug 1854820 xenial/linux/pc-kernel: bug 1854821 xenial/linux/stlouis-kernel: bug 1854822 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854835 Title: xenial/linux: 4.4.0-171.200 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 04. December 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1854833 trusty/linux-lts-xenial: bug 1854834 unknown/unknown: bug 1854820 xenial/linux-aws: bug 1854824 xenial/linux-cascade: bug 1854825 xenial/linux-fips: bug 1854832 xenial/linux-kvm: bug 1854826 xenial/linux-raspi2: bug 1854829 xenial/linux-snapdragon: bug 1854831 xenial/linux/caracalla-kernel: bug 1854820 xenial/linux/pc-kernel: bug 1854821 xenial/linux/stlouis-kernel: bug 1854822 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854784] Re: disco/linux-snapdragon: 5.0.0-1028.30 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 04. December 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1854784 Title: disco/linux-snapdragon: 5.0.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 04. December 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854766] Re: disco/linux-raspi2: 5.0.0-1024.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 04. December 2019 13:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1854766 Title: disco/linux-raspi2: 5.0.0-1024.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854788 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 04. December 2019 13:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854819] Re: bionic/linux: 4.15.0-73.82 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854819 Title: bionic/linux: 4.15.0-73.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855058] Re: package linux-azure-tools-5.3.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package l
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1855058 Title: package linux-azure-tools-5.3.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux- aws-tools-5.3.0-1008 5.3.0-1008.9 Status in linux-azure package in Ubuntu: New Bug description: during the update ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-azure-tools-5.3.0-1008 (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 Date: Wed Dec 4 03:52:48 2019 DuplicateSignature: package:linux-azure-tools-5.3.0-1008:(not installed) Unpacking linux-azure-tools-5.3.0-1008 (5.3.0-1008.9) ... dpkg: error processing archive /tmp/apt-dpkg-install-14N46V/129-linux-azure-tools-5.3.0-1008_5.3.0-1008.9_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux-aws-tools-5.3.0-1008 5.3.0-1008.9 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux-aws-tools-5.3.0-1008 5.3.0-1008.9 InstallationDate: Installed on 2019-12-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: linux-azure Title: package linux-azure-tools-5.3.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux-aws-tools-5.3.0-1008 5.3.0-1008.9 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855058] Re: package linux-azure-tools-5.3.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package l
** Tags removed: need-duplicate-check -- 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/1855058 Title: package linux-azure-tools-5.3.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux- aws-tools-5.3.0-1008 5.3.0-1008.9 Status in linux-azure package in Ubuntu: New Bug description: during the update ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-azure-tools-5.3.0-1008 (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 Date: Wed Dec 4 03:52:48 2019 DuplicateSignature: package:linux-azure-tools-5.3.0-1008:(not installed) Unpacking linux-azure-tools-5.3.0-1008 (5.3.0-1008.9) ... dpkg: error processing archive /tmp/apt-dpkg-install-14N46V/129-linux-azure-tools-5.3.0-1008_5.3.0-1008.9_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux-aws-tools-5.3.0-1008 5.3.0-1008.9 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux-aws-tools-5.3.0-1008 5.3.0-1008.9 InstallationDate: Installed on 2019-12-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: linux-azure Title: package linux-azure-tools-5.3.0-1008 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.3.0-1008', which is also in package linux-aws-tools-5.3.0-1008 5.3.0-1008.9 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854826] Re: xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 04. December 2019 15:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1854826 Title: xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 04. December 2019 15:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 11. December 2019 08:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 11. December 2019 08:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854813] Re: xenial/linux-azure: 4.15.0-1065.70 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 06. December 2019 12:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1854811 xenial/linux-azure/azure-kernel: bug 1854810 variant: debs -- 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/1854813 Title: xenial/linux-azure: 4.15.0-1065.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 06. December 2019 12:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1854811 xenial/linux-azure/azure-kernel: bug 1854810 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854770] Re: bionic/linux-azure: 5.0.0-1028.30~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854771 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 06. December 2019 22:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1854769 variant: debs -- 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/1854770 Title: bionic/linux-azure: 5.0.0-1028.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854771 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 06. December 2019 22:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1854769 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 11. December 2019 08:11 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 11. December 2019 12:37 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Wednesday, 11. December 2019 12:41 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 11. December 2019 12:37 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 11. December 2019 12:41 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Wednesday, 11. December 2019 12:41 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Wednesday, 11. December 2019 12:41 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
same worked perfectly 18.04 gone 19.10 this week and now i have to keep manually importing then restarting mysql service because it could not access its data ,, -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Attachment added: "journalctl -b -1 -k" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5311740/+files/journalctl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
from what I can see is that its trying to do importing before the disks have been mapped because /etc/multipath.conf is being read just after zfs failed Dec 11 23:04:57 aio systemd[1]: Started Mount ZFS filesystems. Dec 11 23:04:57 aio systemd[1]: Starting Mount ZFS filesystems... Dec 11 23:04:57 aio systemd[1]: Reached target ZFS pool import target. Dec 11 23:04:57 aio systemd[1]: Failed to start Import ZFS pools by cache file. Dec 11 23:04:57 aio systemd[1]: zfs-import-cache.service: Failed with result 'exit-code'. Dec 11 23:04:57 aio systemd[1]: zfs-import-cache.service: Main process exited, code=exited, status=1/FAILURE Dec 11 23:04:57 aio zpool[3622]: a backup source. Dec 11 23:04:57 aio zpool[3622]: Destroy and re-create the pool from Dec 11 23:04:57 aio zpool[3622]: cannot import 'ZFS3WAY': no such pool or dataset Dec 11 23:04:57 aio multipathd[3627]: path checkers start up Dec 11 23:04:57 aio multipathd[3627]: read /etc/multipath.conf Dec 11 23:04:57 aio multipathd[3627]: start up Dec 11 23:04:57 aio kernel: rdac: device handler registered Dec 11 23:04:57 aio kernel: emc: device handler registered Dec 11 23:04:57 aio kernel: alua: device handler registered Dec 11 23:04:57 aio systemd[1]: Starting Import ZFS pools by cache file... Dec 11 23:04:57 aio systemd[1]: Started Install ZFS kernel module. Dec 11 23:04:57 aio systemd[1]: Starting Device-Mapper Multipath Device Controller... Dec 11 23:04:57 aio systemd[1]: Starting Install ZFS kernel module... Dec 11 23:04:57 aio systemd[1]: Started udev Wait for Complete Device Initialization. Dec 11 23:04:57 aio kernel: ZFS: Loaded module v0.8.2-1, ZFS pool version 5000, ZFS filesystem version 5 Dec 11 23:04:57 aio systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Dec 11 23:04:57 aio systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Dec 11 23:04:57 aio systemd[1]: Starting LVM event activation on device 9:0... Dec 11 23:04:57 aio systemd[1]: Created slice system-lvm2\x2dpvscan.slice. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Is it possible to try this patch? ** Patch added: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311741/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite
There was a backport for 5.3 of a timeout, I am in the process of finding out a good timeout value for the net testsuite before I can send it upstream. Let me send the value I found so far, which works for xfrm_policy.sh, which seems to be the one that takes most time. 150 would be fine here. -- 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/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually: So there must be some test in net that will cause this. From the test result it looks like the test was executed in the following sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed Dec 11 06:42:39 2019 Ec2AMI: ami-047cec24582f6ae0d Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-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: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Promote to Proposed - phase-changed: Wednesday, 11. December 2019 12:41 UTC + phase: Testing + phase-changed: Wednesday, 11. December 2019 13:42 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- review in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Wednesday, 11. December 2019 13:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Thanks Adrian, I'll test this as soon as I can. Could you confirm the steps.. I assume I need to apply this to 4.16-rc1. I think it is .. $ apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ wget https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311741/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch ---NOT SURE WHAT TO DO HERE $ make localmodconfig $ make -j`nproc` deb-pkg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847499] Re: USB Huion 1060PLUS and kernel 5.3.0 on Eoan [on hold]
Up to kernel 5.2.21 everything is fine. Kernel 5.0 from Disco is working as well. regards Henning -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847499 Title: USB Huion 1060PLUS and kernel 5.3.0 on Eoan [on hold] Status in linux package in Ubuntu: Confirmed Bug description: I am having issues with the tablet above. Since the upgrade to Eoan (I know, development..) the tablet is not working any more. Dmesg below: [ 7199.742905] usb 1-4: USB disconnect, device number 9 [ 7199.742911] usb 1-4.1: USB disconnect, device number 10 [ 7199.743381] usb 1-4.4: USB disconnect, device number 11 [ 7206.101315] usb 1-4: new high-speed USB device number 12 using xhci_hcd [ 7206.227830] usb 1-4: New USB device found, idVendor=058f, idProduct=6254, bcdDevice= 1.00 [ 7206.227836] usb 1-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 7206.227840] usb 1-4: Product: USB2.0Hub [ 7206.230807] hub 1-4:1.0: USB hub found [ 7206.230868] hub 1-4:1.0: 4 ports detected [ 7206.518332] usb 1-4.1: new full-speed USB device number 13 using xhci_hcd [ 7206.621492] usb 1-4.1: New USB device found, idVendor=256c, idProduct=006e, bcdDevice=30.00 [ 7206.621498] usb 1-4.1: New USB device strings: Mfr=5, Product=6, SerialNumber=0 [ 7206.627684] usb 1-4.1: can't set config #1, error -32 [ 7206.703319] usb 1-4.4: new high-speed USB device number 14 using xhci_hcd [ 7206.794338] usb 1-4.4: New USB device found, idVendor=058f, idProduct=6366, bcdDevice= 1.00 [ 7206.794346] usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7206.794351] usb 1-4.4: Product: Mass Storage Device [ 7206.794353] usb 1-4.4: Manufacturer: Generic [ 7206.794356] usb 1-4.4: SerialNumber: 058F0OB1 [ 7206.799699] usb-storage 1-4.4:1.0: USB Mass Storage device detected Unfortunately there is not much to be found regarding the >>can't set config<< thing with the code 32. The digimind driver compiles fine. The funny part is: After a suspend and resume the tablet is working until unplugged and plugged in. Any sugestions? Kernel 5.2 is working fine, have to sort out the ZFS module though and it would be nice to stick with the official components. Cheers, Henning ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-13-lowlatency 5.3.0-13.14 ProcVersionSignature: Ubuntu 5.3.0-13.14-lowlatency 5.3.0 Uname: Linux 5.3.0-13-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henninge 2253 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 9 17:42:28 2019 InstallationDate: Installed on 2018-10-24 (349 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire VN7-572G ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-lowlatency root=UUID=b0b1c52f-0c00-4a1a-aa55-bcf97ee20897 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-lowlatency N/A linux-backports-modules-5.3.0-13-lowlatency N/A linux-firmware 1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago) dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-572G dmi.board.vendor: Acer dmi.board.version: V1.05 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd09/25/2015:svnAcer:pnAspireVN7-572G:pvrV1.05:rvnAcer:rnAspireVN7-572G:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: SKL dmi.product.name: Aspire VN7-572G dmi.product.sku: Aspire VN7-572G_1037_1.05 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855232] Re: Touchpad not working.
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1855232 Title: Touchpad not working. Status in linux package in Ubuntu: Confirmed Bug description: The laptop was working perfectly fine when I switched it off at night. This was after an update I had received from Ubuntu on December 3, 2019. When I switched it on in the morning, the touchpad wasn't working. Now I am using a USB connected mouse, which is working perfectly fine for now. Laptop Model: Dell Inspiron 14 3000 Series Processor: Intel® Core™ i3-6006U CPU @ 2.00GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tanya 1815 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 11:55:49 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-29 (919 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 14-3467 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=9f326190-8d51-44b3-93fc-45d010a7a54b ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0WPN9K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0WPN9K:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856042] [NEW] Trackpad on HP Stream 11 no longer works with linux-image-4.15.0-72-generic
Public bug reported: The trackpad on my HP Stream 11 laptop stopped working when I upgraded the kernel to linux-image-4.15.0-72-generic. It works fine with linux- image-4.15.0-70-generic. An external USB mouse also works fine. I reported this bug with "ubuntu-bug linux" under linux- image-4.15.0-72-generic with the non-working trackpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rb 888 F pulseaudio /dev/snd/controlC0: rb 888 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 14:15:09 2019 MachineType: Hewlett-Packard HP Stream Notebook PC 11 ProcEnviron: TERM=dumb PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic root=/dev/mapper/vg0-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8023 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.12 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd12/26/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Stream Notebook PC 11 dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1856042 Title: Trackpad on HP Stream 11 no longer works with linux- image-4.15.0-72-generic Status in linux package in Ubuntu: New Bug description: The trackpad on my HP Stream 11 laptop stopped working when I upgraded the kernel to linux-image-4.15.0-72-generic. It works fine with linux-image-4.15.0-70-generic. An external USB mouse also works fine. I reported this bug with "ubuntu-bug linux" under linux- image-4.15.0-72-generic with the non-working trackpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rb 888 F pulseaudio /dev/snd/controlC0: rb 888 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 14:15:09 2019 MachineType: Hewlett-Packard HP Stream Notebook PC 11 ProcEnviron: TERM=dumb PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic root=/dev/mapper/vg0-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8023 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.12 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd12/26/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Stream Notebook PC 11 dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Actually it should apply cleanly to any kernel from 4.17 onward (4.16 would require a little backporting) To apply the patch, in the linux git directory: git am 0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
$ git am 0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch Then compile the kernel as usual. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856042] 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/1856042 Title: Trackpad on HP Stream 11 no longer works with linux- image-4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Bug description: The trackpad on my HP Stream 11 laptop stopped working when I upgraded the kernel to linux-image-4.15.0-72-generic. It works fine with linux-image-4.15.0-70-generic. An external USB mouse also works fine. I reported this bug with "ubuntu-bug linux" under linux- image-4.15.0-72-generic with the non-working trackpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rb 888 F pulseaudio /dev/snd/controlC0: rb 888 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 14:15:09 2019 MachineType: Hewlett-Packard HP Stream Notebook PC 11 ProcEnviron: TERM=dumb PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic root=/dev/mapper/vg0-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8023 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.12 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd12/26/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Stream Notebook PC 11 dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855312] Re: Fix unusable USB hub on Dell TB16 after S3
** Description changed: [Impact] Sometimes USB hub on Dell TB16 stop working after S3. [Fix] Attempt to power cycle USB device when a it's stuck at eSS.Disabled - state, it's basically not recoverable. - + state, it's basically not recoverable. + [Test] After applying the patch, USB ports and USB ethernet are still working after 100 times S3 stress test. + Tested on other platforms and didn't observe any regression. + However, I have never seen any other USB device stuck in eSS.Disabled state, + so the code path wasn't executed at all. + [Regression Potential] Low. This is a last resort attempt, in most cases this code path won't be reached. -- 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/1855312 Title: Fix unusable USB hub on Dell TB16 after S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: In Progress Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] Sometimes USB hub on Dell TB16 stop working after S3. [Fix] Attempt to power cycle USB device when a it's stuck at eSS.Disabled state, it's basically not recoverable. [Test] After applying the patch, USB ports and USB ethernet are still working after 100 times S3 stress test. Tested on other platforms and didn't observe any regression. However, I have never seen any other USB device stuck in eSS.Disabled state, so the code path wasn't executed at all. [Regression Potential] Low. This is a last resort attempt, in most cases this code path won't be reached. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Promote to Proposed phase-changed: Wednesday, 11. December 2019 12:06 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Signing signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Promote to Proposed phase-changed: Wednesday, 11. December 2019 12:06 UTC reason: promote-to-proposed: Ongoing -- package copied to Signing signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
For bionic and xenial: https://lists.ubuntu.com/archives/kernel- team/2019-December/106317.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855978] Re: linux-firmware updates breaks Intel 9260 on Bionic
Confirmed this can also be fixed by proposed fix in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1855825 for bug 1855825. I also noticed that although WiFi is up with 7906 + 5.3 kernel, the authentication will never be completed on 9260, but I think there should be already a public bug for this, and now we can finally have a chance to reproduce it. Since this is already out of the scope here, I will address such issue in another bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1855978 Title: linux-firmware updates breaks Intel 9260 on Bionic Status in linux-firmware package in Ubuntu: Triaged Bug description: Bug 1852512 pulls new firmware blobs for 5.3 hwe kernel upgrade, and iwlwifi-9260-th-b0-jf-b0-46.ucode is included. This new version doesn't seem to be compatible with Bionic OEM kernels, and will fail WiFi initialization leaving the system booted without wireless connection. The previous version (1.173.12) has iwlwifi-9260-th-b0-jf-b0-43.ucode instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.13 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Dec 11 14:18:01 2019 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 InstallationDate: Installed on 2019-07-11 (152 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1855978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
@Wayne, I believe this can be fixed in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1855825, which should be landed soon into Eoan/Focal if you prefer a DKMS based solution. It would take some more time to fix generic kernel in Eoan. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Confirmed Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
An example of dns update after putting:
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf
in the openvpn .config file:
Wed Dec 11 15:04:25 2019 /etc/openvpn/update-resolv-conf tun0 1500 1558
10.172.67.194 255.255.192.0 init
update-resolv-conf uses:
[ -x /sbin/resolvconf ] || exit 0
so I guess it needs a systemd-resolved.service integration instead.
** Changed in: openvpn (Ubuntu)
Importance: Undecided => Medium
** Changed in: openvpn (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : ke
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Promote to Proposed - phase-changed: Wednesday, 11. December 2019 12:06 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 11. December 2019 15:31 UTC reason: - promote-to-proposed: Ongoing -- package copied to Signing signed:building + promote-signing-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Wednesday, 11. December 2019 15:31 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856042] Re: Trackpad on HP Stream 11 no longer works with linux-image-4.15.0-72-generic
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Seems a duplicate of bug 1854798. Please try bionic kernel 4.15.0-73 from the proposed channel. ** This bug has been marked a duplicate of bug 1854798 Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856042 Title: Trackpad on HP Stream 11 no longer works with linux- image-4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Bug description: The trackpad on my HP Stream 11 laptop stopped working when I upgraded the kernel to linux-image-4.15.0-72-generic. It works fine with linux-image-4.15.0-70-generic. An external USB mouse also works fine. I reported this bug with "ubuntu-bug linux" under linux- image-4.15.0-72-generic with the non-working trackpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rb 888 F pulseaudio /dev/snd/controlC0: rb 888 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 14:15:09 2019 MachineType: Hewlett-Packard HP Stream Notebook PC 11 ProcEnviron: TERM=dumb PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic root=/dev/mapper/vg0-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8023 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.12 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd12/26/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Stream Notebook PC 11 dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855900] Re: touchPad not detected
** Description changed: - I: Bus=0019 Vendor= Product=0003 Version= - N: Name="Sleep Button" - P: Phys=PNP0C0E/button/input0 - S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 - U: Uniq= - H: Handlers=kbd event0 - B: PROP=0 - B: EV=3 - B: KEY=4000 0 0 - - I: Bus=0019 Vendor= Product=0005 Version= - N: Name="Lid Switch" - P: Phys=PNP0C0D/button/input0 - S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 - U: Uniq= - H: Handlers=event1 - B: PROP=0 - B: EV=21 - B: SW=1 - - I: Bus=0019 Vendor= Product=0001 Version= - N: Name="Power Button" - P: Phys=LNXPWRBN/button/input0 - S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 - U: Uniq= - H: Handlers=kbd event2 - B: PROP=0 - B: EV=3 - B: KEY=10 0 - - I: Bus=0011 Vendor=0001 Product=0001 Version=ab54 - N: Name="AT Translated Set 2 keyboard" - P: Phys=isa0060/serio0/input0 - S: Sysfs=/devices/platform/i8042/serio0/input/input3 - U: Uniq= - H: Handlers=sysrq kbd event3 leds - B: PROP=0 - B: EV=120013 - B: KEY=40200 3803078f800d001 fedfffef fffe - B: MSC=10 - B: LED=7 - - I: Bus=0019 Vendor= Product=0006 Version= - N: Name="Video Bus" - P: Phys=LNXVIDEO/video/input0 - S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 - U: Uniq= - H: Handlers=kbd event4 - B: PROP=0 - B: EV=3 - B: KEY=3e000b 0 0 0 - - I: Bus=0019 Vendor=17aa Product=5054 Version=4101 - N: Name="ThinkPad Extra Buttons" - P: Phys=thinkpad_acpi/input0 - S: Sysfs=/devices/platform/thinkpad_acpi/input/input7 - U: Uniq= - H: Handlers=rfkill kbd event5 - B: PROP=0 - B: EV=33 - B: KEY=10040 0 1804 0 501000 0 1701b02102004 c000280041114000 10e 0 - B: MSC=10 - B: SW=8 - - I: Bus= Vendor= Product= Version= - N: Name="HDA Intel PCH Mic" - P: Phys=ALSA - S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 - U: Uniq= - H: Handlers=event6 - B: PROP=0 - B: EV=21 - B: SW=10 - - I: Bus= Vendor= Product= Version= - N: Name="HDA Intel PCH Headphone" - P: Phys=ALSA - S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 - U: Uniq= - H: Handlers=event7 - B: PROP=0 - B: EV=21 - B: SW=4 - - I: Bus= Vendor= Product= Version= - N: Name="HDA Intel PCH HDMI/DP,pcm=3" - P: Phys=ALSA - S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 - U: Uniq= - H: Handlers=event8 - B: PROP=0 - B: EV=21 - B: SW=140 - - I: Bus= Vendor= Product= Version= - N: Name="HDA Intel PCH HDMI/DP,pcm=7" - P: Phys=ALSA - S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 - U: Uniq= - H: Handlers=event9 - B: PROP=0 - B: EV=21 - B: SW=140 - - I: Bus= Vendor= Product= Version= - N: Name="HDA Intel PCH HDMI/DP,pcm=8" - P: Phys=ALSA - S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 - U: Uniq= - H: Handlers=event10 - B: PROP=0 - B: EV=21 - B: SW=140 - - I: Bus= Vendor= Product= Version= - N: Name="HDA Intel PCH HDMI/DP,pcm=9" - P: Phys=ALSA - S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 - U: Uniq= - H: Handlers=event11 - B: PROP=0 - B: EV=21 - B: SW=140 - - I: Bus= Vendor= Product= Version= - N: Name="HDA Intel PCH HDMI/DP,pcm=10" - P: Phys=ALSA - S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 - U: Uniq= - H: Handlers=event12 - B: PROP=0 - B: EV=21 - B: SW=140 - - I: Bus=0003 Vendor=046d Product=c077 Version=0111 - N: Name="Logitech USB Optical Mouse" - P: Phys=usb-:00:14.0-1/input0 - S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C077.0002/input/input20 - U: Uniq= - H: Handlers=mouse0 event13 - B: PROP=0 - B: EV=17 - B: KEY=ff 0 0 0 0 - B: REL=103 - B: MSC=10 - - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: linux-image-4.15.0-72-generic 4.15.0-72.81 - ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 - Uname: Linux 4.15.0-72-generic x86_64 - ApportVersion: 2.20.9-0ubuntu7.9 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ibennour 3313 F pulseaudio - CurrentDesktop: ubuntu:GNOME - Date: Tue Dec 10 16:35:19 2019 - HibernationDevice: RESUME=UUID=329a7fb2-1836-48ca-b5aa-2ff99cec163e - InstallationDate: Installed on 2018-08-24 (473 days ago) - InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) - Lsusb: - Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - MachineType: LENOVO 20KHS0SA00 - ProcFB: 0 inteldrmfb - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 - RelatedPackageVersions: - linux-restricted-modules-4.15.0-72-generic N/A -
[Kernel-packages] [Bug 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
*** This bug is a duplicate of bug 1855059 *** https://bugs.launchpad.net/bugs/1855059 ** This bug has been marked a duplicate of bug 1855059 [Regression] 4.15.0-73.82 Can not boot ThunderX -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: Confirmed Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it
** Changed in: kunpeng920/ubuntu-19.10 Assignee: Ike Panhc (ikepanhc) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it Status in kunpeng920: New Status in kunpeng920 ubuntu-18.04 series: Triaged Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Triaged Status in kunpeng920 ubuntu-19.10 series: Triaged Status in kunpeng920 ubuntu-20.04 series: Triaged Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 8c39673d5474b scsi: hisi_sas: Check sas_port before using it [Regression Risk] Patch restricted to hisi_sas driver. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
