[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
Hello, i installed v4.17-rc6 and this problem seems fixed, no emtpy line in /proc/PID/status, but i also miss the line Speculation_Store_Bypass which was existing in 4.4.0-127-generic #153-Ubuntu So may be this is fixed because meltdown/spectre patches are not applied? Iam not sure, so i hesitate to set tag kernel-fixed-upstream. What do you think? For information: I could not install linux- headers-4.17.0-041700rc6-generic, there is a dependency to libssl1.1 which is not available currently for xenial. 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/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Problem persists in kernel 4.16.11 #uname -r 4.16.11-041611-generic #ls /sys/class/drm card0 card0-eDP-1 card0-HDMI-A-1 renderD128 ttm version #dmesg | grep drm [1.783188] [drm] radeon kernel modesetting enabled. [1.784832] fb: switching to radeondrmfb from EFI VGA [1.831813] [drm] amdgpu kernel modesetting enabled. [1.840215] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130A 0x17AA:0x3988 0x00). [1.840237] [drm] register mmio base: 0xF0B0 [1.840239] [drm] register mmio size: 262144 [1.865264] [drm] BIOS signature incorrect 0 0 [1.865367] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [1.865387] [drm] Detected VRAM RAM=1024M, BAR=1024M [1.865390] [drm] RAM width 64bits UNKNOWN [1.865779] [drm] amdgpu: 1024M of VRAM memory ready [1.865783] [drm] amdgpu: 3072M of GTT memory ready. [1.865807] [drm] GART: num cpu pages 262144, num gpu pages 262144 [1.865894] [drm] PCIE GART of 1024M enabled (table at 0x00F40004). [1.866040] [drm] Internal thermal controller without fan control [1.866046] [drm] amdgpu: dpm initialized [1.867349] [drm] Found UVD firmware Version: 1.55 Family ID: 9 [1.867789] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [1.869984] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.870074] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.870200] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.870309] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 [1.884255] [drm] Display Core initialized with v3.1.27! [1.891240] [drm] SADs count is: -2, don't need to read it [1.891668] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.891674] [drm] Driver supports precise vblank timestamp query. [1.910078] [drm] UVD initialized successfully. [2.02] [drm] VCE initialized successfully. [2.056074] [drm] fb mappable at 0xA042A000 [2.056083] [drm] vram apper at 0xA000 [2.056087] [drm] size 8294400 [2.056090] [drm] fb depth is 24 [2.056093] [drm]pitch is 7680 [2.056218] fbcon: amdgpudrmfb (fb0) is primary device [2.113975] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device [2.130285] [drm] Initialized amdgpu 3.23.0 20150101 for :00:01.0 on minor 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
The problem still here... ** Changed in: linux (Ubuntu) Status: Fix Released => 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/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: comm
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-124-generic x86_64) The problem still here... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] faile
[Kernel-packages] [Bug 1772682] Re: No sound for Dell Inspiron 5758
** Summary changed: - No sound + No sound for Dell Inspiron 5758 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772682 Title: No sound for Dell Inspiron 5758 Status in linux package in Ubuntu: Confirmed Bug description: I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have I tried to update system but the computer did not finish updating, and informed me that there is no internet connection, while the connection was OK. As a result, I still have not been any sound in the computer. Sincerely yours, Andrew. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-147-generic 3.13.0-147.196 ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39 Uname: Linux 3.13.0-147-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue May 22 19:03:51 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436 InstallationDate: Installed on 2016-01-25 (848 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5758 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-147-generic N/A linux-backports-modules-3.13.0-147-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09CGRW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5758 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/1772682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756768] Re: package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package linux-image-4.4.0-66-generic is not ready for configuration cannot configure (cu
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756768 Title: package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package linux-image-4.4.0-66-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Expired Bug description: This error keeps popping up, every-time I start the computer ... HELP !!! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sean 1853 F pulseaudio /dev/snd/controlC0: sean 1853 F pulseaudio /dev/snd/seq:timidity987 F timidity Date: Sun Mar 18 21:41:35 2018 DuplicateSignature: package:linux-image-4.4.0-66-generic:4.4.0-66.87 Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ... dpkg: error processing package linux-image-4.4.0-66-generic (--configure): package linux-image-4.4.0-66-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-66-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=74f46aa5-3960-4696-946a-2279ff2d892c InstallationDate: Installed on 2016-11-07 (496 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6410 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=7155d0a6-cd81-41b5-a211-32b1f03f9a7b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.15 SourcePackage: linux Title: package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package linux-image-4.4.0-66-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/26/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745945] Re: Kernel update makes HDMI unresponsive
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745945 Title: Kernel update makes HDMI unresponsive Status in linux package in Ubuntu: Expired Bug description: I've update to 4.13.0-32-generic in attempts to fix the same problem listed in Bug #1734084. The only reason I've made this bug is because I'm on 17.10 not 17.04. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy linux-image-4.13.0-32-generic linux-image-4.13.0-32-generic: Installed: 4.13.0-32.35 Candidate: 4.13.0-32.35 Version table: *** 4.13.0-32.35 500 500 http://mirror.kayo.moe/ubuntu artful-updates/main amd64 Packages 500 http://mirror.kayo.moe/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caymon 1499 F pulseaudio /dev/snd/pcmC1D0p: caymon 1499 F...m pulseaudio /dev/snd/controlC1: caymon 1499 F pulseaudio CurrentDesktop: GNOME Date: Mon Jan 29 00:55:27 2018 HibernationDevice: RESUME=UUID=29e48daf-947d-44ac-bf09-520219553efe InstallationDate: Installed on 2017-10-23 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76 Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76 dmi.board.version: lemu7 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/25/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Lemur dmi.product.version: lemu7 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank
After several weekends of testing, I believe I can report with high confidence that the kernel update to 4.17-rc2 fixes the second of the two problems; specifically, we no longer see kernel crashes after using Alt-SysRq-k to recover from frozen/hanging blank screens. However, the unable-to-unblank problem remains; after normal screen blanking, about 50% of the time we are unable to recover by moving the cursor or typing a key. Instead, only Alt-SysRq-k allows us to recover back to a guest login screen. There doesn't seem to be much in the system logs that I can find, except possibly this: May 20 20:41:04 Comprm8 gnome-session[7919]: gnome-session-binary[7919]: GLib-GIO-CRITICAL: g_dbus_connection_call_internal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed May 20 20:41:04 Comprm8 gnome-session-binary[7919]: GLib-GIO-CRITICAL: g_dbus_connection_call_internal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed Some seemingly similar bug reports from out in the wild: https://askubuntu.com/questions/795014/ubuntu-16-04-occasionally-hangs-with-screen-off-after-switching-ttys-or-turning https://askubuntu.com/questions/949764/ubuntu-hangs-when-unlocking-screen Can you recommend any approaches to help debug the root cause of this problem, presumably in X and/or the radeon driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763273 Title: kernel panic in Radeon driver while screen blank Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I maintain a set of older kiosks running a mix of stock Ubuntu 14.04 LTS and 16.04. As we have gradually transitioned them to 16.04, we have noticed that the machines running 16.04.1 now regularly exhibit problems restoring from the blank screen which appears after a period of inactivity. This only occurs on the machines where we've installed 16.04. All of the 16.04.1 installations are "fresh", that is, complete re-installs from scratch, and we install all security and other updates on a regular basis. This problem has persisted right from the beginning when we started using 16.04. Following a period of user inactivity, the screen goes blank; this is, of course, expected. When the user tries to restore the session by typing a key or moving the mouse, one of three outcomes occurs. Sometimes, the session restores normally. Other times, the screen remains blank regardless of all normal keyboard input, until a magic SysRq sequence is performed. After Alt-SysRq-k, either the virtual console resets to a login screen (as expected after this SysRq sequence), or we get a kernel panic text screen (see attached screen photo) and can only restore via a hard power-cycle reboot. I will continue to try to capture a better trace output from one of these conditions, perhaps from /var/log/kern.log or by installing linux-crashdump (although these old machines may not have enough memory for the stock package). But in the meantime, I'm attaching a photo of the kernel panic we see, which suggests a problem may reside in the Radeon driver ... which would seem possible, given the general blank-screen no-resume problem on these systems. Any advice on how to further capture any other needed details would be appreciated. Thanks very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
** Tags added: verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux-firmware source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: New Status in wireless-regdb source package in Xenial: New Status in linux source package in Bionic: In Progress Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in wireless-regdb source package in Bionic: New Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
Verified the new firmwares in xenial-proposed and xenial-bionic are correct. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in wireless-regdb package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux-firmware source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: New Status in wireless-regdb source package in Xenial: New Status in linux source package in Bionic: In Progress Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in wireless-regdb source package in Bionic: New Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
apport information ** Tags added: apport-collected ** Description changed: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 May 22 21:33 seq + crw-rw 1 root audio 116, 33 May 22 21:33 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.17 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: [Errno 2] No such file or directory + CRDA: N/A + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lspci: Error: [Errno 2] No such file or directory + Lsusb: Error: [Errno 2] No such file or directory + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none + ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-124-generic N/A + linux-backports-modules-4.4.0-124-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-124-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.5 + dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.5 + dmi.sys.vendor: QEMU ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1772775/+attachment/5143070/+files/CurrentDmesg.txt -- You re
[Kernel-packages] [Bug 1772775] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1772775/+attachment/5143072/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Confirmed Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.
[Kernel-packages] [Bug 1772775] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1772775/+attachment/5143074/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Confirmed Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd0
[Kernel-packages] [Bug 1772775] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1772775/+attachment/5143075/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Confirmed Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:s
[Kernel-packages] [Bug 1772775] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1772775/+attachment/5143076/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Confirmed Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i44
[Kernel-packages] [Bug 1772775] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1772775/+attachment/5143071/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Confirmed Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd0
[Kernel-packages] [Bug 1772775] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1772775/+attachment/5143073/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Confirmed Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 21:33 seq crw-rw 1 root audio 116, 33 May 22 21:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro kaslr net.ifnames=0 nmi_watchdog=0 nr_cpus=1 pti=on console=ttyS0 vsyscall=none ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-124-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubunt
[Kernel-packages] [Bug 1772610] Re: Adding back alx WoL feature
** Description changed: [Impact] - The WoL feature is a must to pass Energy Star 6.1 and above, - the power consumption will be measured during S3 with WoL is enabled. + The WoL feature is a must to pass Energy Star 6.1 and above. + The power consumption will be measured during S3 with WoL is enabled. [Test case] Verified pass on new Dell machines without the wake up issue. [Regression potential] No regression. We disable this feature by default, so the driver behavior will be the same. We'll leave this feature disabled by default before we can fix the unintentional wake up issue. [Misc] - Upstream maintainer insists to fix the wake up issue before we can add this feature back to the driver, so make the patch in Ubuntu only. + Upstream maintainer insists to fix the wake up issue before we can add this feature back to the driver, so make the patch stay in Ubuntu kernel only. We'll verify WoL on every new machines and try to fix this issue when we encounter it. ** Tags added: originate-from-1736377 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772610 Title: Adding back alx WoL feature Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: [Impact] The WoL feature is a must to pass Energy Star 6.1 and above. The power consumption will be measured during S3 with WoL is enabled. [Test case] Verified pass on new Dell machines without the wake up issue. [Regression potential] No regression. We disable this feature by default, so the driver behavior will be the same. We'll leave this feature disabled by default before we can fix the unintentional wake up issue. [Misc] Upstream maintainer insists to fix the wake up issue before we can add this feature back to the driver, so make the patch stay in Ubuntu kernel only. We'll verify WoL on every new machines and try to fix this issue when we encounter it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1772610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772775] 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 1772775 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/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Incomplete Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
Between 4.4.0-124.148 and 4.4.0-127.153, the following commits references "sit": - sit: reload iphdr in ipip6_rcv - ipv6: sit: better validate user provided tunnel names - ipv6 sit: work around bogus gcc-8 -Wrestrict warning -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Incomplete Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Interesting read. If they are adding Dell 'features' then maybe also my built in webcam will one day work again as that also doesn't work. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772775] Re: 4.4.0-127.153 generates many "sit: non-ECT" messages
I don't know if that matters but I use fq_codel and have been for a long while. # sysctl net.core.default_qdisc net.core.default_qdisc = fq_codel ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Incomplete Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772775] [NEW] 4.4.0-127.153 generates many "sit: non-ECT" messages
Public bug reported: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=67f7ee15-64f4-4c85-805c-08386d5fed8b ro console=ttyS0 net.ifnames=0 kaslr vsyscall=none nmi_watchdog=0 possible_cpus=1 pti=on nr_cpus=1 RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: '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-2.5 dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.5 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug regression-update xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772775 Title: 4.4.0-127.153 generates many "sit: non-ECT" messages Status in linux package in Ubuntu: Incomplete Bug description: Since deploying linux-image-4.4.0-127-generic (4.4.0-127.153) on a Xenial VM with a sit tunnel, I get such messages: May 22 10:49:38 gw kernel: [ 68.121601] sit: non-ECT from 0.0.0.0 with TOS=0x5 Those are logged quite often: # grep -cF 'sit: non-ECT' /var/log/syslog 9108 Reverting to linux-image-4.4.0-124-generic (4.4.0-124.148) fixes the issue. # lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 # apt-cache policy linux-image-4.4.0-127-generic linux-image-4.4.0-127-generic: Installed: 4.4.0-127.153 Candidate: 4.4.0-127.153 Version table: *** 4.4.0-127.153 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 20:08 seq crw-rw 1 root audio 116, 33 May 22 20:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Tue May 22 21:18:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user)
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
No, /var/run/thermald/thermal-conf.xml.auto _is_ regenerated. I tried editing it. /var/run is a symbolic link to /run, which is a tmpfs. The uuids directory contains two files. One is empty, and the other contains the word "INVALID". === gjditchf@copperplate:/sys/bus/acpi$ cd /sys/bus/acpi/devices/INT3400* gjditchf@copperplate:/sys/bus/acpi/devices/INT3400:00$ ls physical_node/uuids/ available_uuids current_uuid gjditchf@copperplate:/sys/bus/acpi/devices/INT3400:00$ cat physical_node/uuids/available_uuids gjditchf@copperplate:/sys/bus/acpi/devices/INT3400:00$ file physical_node/uuids/available_uuids physical_node/uuids/available_uuids: empty gjditchf@copperplate:/sys/bus/acpi/devices/INT3400:00$ cat physical_node/uuids/current_uuid 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/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sam
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
** Description changed: When I boot a Dell Inspiron 7559 with an external monitor connected to - the hdmi port I get a crash on bootup. I can see the following stack - trace in journalctl: - + the hdmi port, it consistently shows only a blank screen after grub and + I have to hard power off the laptop. I can see the following stack trace + in journalctl: syslog contains: - kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers + kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers + This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq + LA2405wg connected via HDMI-to-DVI adapter. - Description: Ubuntu 18.04 LTS - Release: 18.04 - - linux-image-4.15.0-20-generic: - Installed: 4.15.0-20.21 - Candidate: 4.15.0-20.21 - Version table: - *** 4.15.0-20.21 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status - - Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC - 2018 x86_64 x86_64 x86_64 GNU/Linux - - 3) What you expected to happen - I expected the laptop to boot to the login screen. - 4) What happened instead - I see a blank screen after grub and have to hard power off the laptop. + WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen + shows up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" - --- + --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: apatterson 1965 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: - linux-restricted-modules-4.15.0-20-generic N/A - linux-backports-modules-4.15.0-20-generic N/A - linux-firmware 1.173 + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it consistently shows only a blank screen after grub and I have to hard power off the laptop. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter. WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
controlaula was not shipped in 18.04. Invalid for trunk, wontfix for
artful and earlier.
** Changed in: controlaula (Ubuntu)
Status: New => Invalid
--
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 epoptes package in Ubuntu:
New
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:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
New
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 : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
re building. I think i've gotten it building. "time fakeroot debian/rules binary" takes a long time, but seems to be working re your questions: 1) it's consistent. only when booting right after grub I get a kernel crash. Every time when my monitor is connected via the HDMI connector on my laptop. 2) no, i can connect the monitor as soon as I see the ubuntu loading screen and use it no problem. I can also connect monitors after logging in. Also, cold boot reboot doesn't seem to matter. 3) I have tried two monitors, at work right now: Dell UltraSharp U2515H 25" 6ms WQHD Widescreen LED Backlight LCD Monitor IPS panel 350 cd/m2, HDMI/MHL, DisplayPort, USB3.0Hub, Height&Pivot adjustable (connect via straight hdmi cable) at home: HP Compaq LA2405wg - connect via hdmi - dvi adapter + dvi cable 4) see above PS still working on that bisect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
Sandy Patterson a few follow up questions: 1) Does the OS crash consistently if you boot up with the external monitor plugged in, or does it only happen sometimes? If sometimes, how often specifically? 2) Does the OS crash if you connect the external monitor after fully booting up and logging in? 3) As per the sticker of the monitor itself (not from the Bug Description, or the result of a terminal command), could you please provide the full manufacturer and model? 4) Are you using any dongles/converters between the computer and 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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14, so sticking with the old kernel that works for now. Kernel bluetooth bug causes bluez 97-hid2hci.rules udev rule to fail. systemd-udevd has always consumed 100% whenever a udev rule fails (could be argued that's also a bug but at least you become immediately aware there's a problem). Possibly no coincidence that the break was introduced at the same time kernel tree commits were made to btusb.c wrt. Dell 'features' being addded. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
A patch has been submitted to linux-pci, and I've confirmed this fix
works: https://lkml.org/lkml/2018/5/22/817
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771467
Title:
Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Verified on multiple DL360 Gen9 servers with up to date firmware.
Just before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent
POST, the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the
doc's resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
(01/22/2018)), the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to continue
[529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554458] Do you have a strange power saving mode enabled?
[529153.554458] Dazed and confused, but trying to continue
[529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554460] Do you have a strange power saving mode enabled?
[529153.554460] Dazed and confused, but trying to continue
[529154.953916] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529154.953917] Do you have a strange power saving mode enabled?
[529154.953918] Dazed and confused, but trying t
[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB
Thank you for your prompt attention! I can confirm your test kernel resolves this issue: # uname -v #154~lp1772575 SMP Tue May 22 16:06:05 UTC 2018 # blockdev --getsize64 /dev/nbd0 1181116006400 # fdisk -l /dev/nbd0 | head -1 Disk /dev/nbd0: 1.1 TiB, 1181116006400 bytes, 2306867200 sectors -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772575 Title: Kernel 4.4 NBD size overflow with image size exceeding 1TB Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: Release 16.04, kernel 4.4.0-124-generic There's an issue in kernel's NBD module which prevents some larger images to be correctly "connected" , largely described here: https://github.com/NetworkBlockDevice/nbd/issues/44 There is a small patch here that was accepted into mainline 4.10: https://www.spinics.net/lists/linux-block/msg07060.html This is a regression from the previous LTS 3.13 kernel. Here is a small example of the faulty behaviour: # qemu-img create -f qcow2 test.img 1100G Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 # qemu-nbd -c /dev/nbd0 test.img # blockdev --getsize64 /dev/nbd0 18446743055802302464 The correct response would be 1181116006400; this breaks most tools and makes the image unusable, e.g. # fdisk -l /dev/nbd0 fdisk: cannot open /dev/nbd0: Invalid argument --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 12:51 seq crw-rw 1 root audio 116, 33 May 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1 IwConfig: Error: [Errno 2] No such file or directory MachineType: Supermicro SYS-1028R-WTR Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_AU: TERM=xterm PATH=(custom, no user) LANG=en_AU SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.18 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-124-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 02/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: Default string dmi.board.name: X10DRW-i dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SYS-1028R-WTR dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770440] Re: Display server crashes after suspend, I have to reboot using the power button as even (ALT+F1) does not take me to the Terminal to properly reboot the system or res
Linux 4.16.11-041611-generic #201805221331 SMP Tue May 22 17:34:25 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux this fixed the bug for me ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770440 Title: Display server crashes after suspend, I have to reboot using the power button as even (ALT+F1) does not take me to the Terminal to properly reboot the system or restart X. Status in linux package in Ubuntu: Confirmed Bug description: After System is suspended, upon pressing any button to wake up, i am facing a black full screen terminal with Error massage and the system becomes not responsive. ALT+F1 to take me to Termina one to restart does not work ALT+Backspace to restart X does not work. ALT+Shift+DEL to reboot the system doesnt work. I only have the option to force shutdown using the power key and then start again the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Thu May 10 18:17:20 2018 InstallationDate: Installed on 2018-05-04 (6 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770440] Re: Display server crashes after suspend, I have to reboot using the power button as even (ALT+F1) does not take me to the Terminal to properly reboot the system or res
I have tried the lates upstream Kernel and it works just fine. Linux 4.16.11-041611-generic #201805221331 SMP Tue May 22 17:34:25 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770440 Title: Display server crashes after suspend, I have to reboot using the power button as even (ALT+F1) does not take me to the Terminal to properly reboot the system or restart X. Status in linux package in Ubuntu: Confirmed Bug description: After System is suspended, upon pressing any button to wake up, i am facing a black full screen terminal with Error massage and the system becomes not responsive. ALT+F1 to take me to Termina one to restart does not work ALT+Backspace to restart X does not work. ALT+Shift+DEL to reboot the system doesnt work. I only have the option to force shutdown using the power key and then start again the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Thu May 10 18:17:20 2018 InstallationDate: Installed on 2018-05-04 (6 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715552] Re: VMWare does not start
Thank you iLugo, your workaround instructions work for me with 18.04 and VMPlayer 12.5.9 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715552 Title: VMWare does not start Status in linux package in Ubuntu: Confirmed Bug description: Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started: /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux- gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC symbol `clock_gettime' Works under Ubuntu 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-13-generic 4.12.0-13.14 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 9336 F pulseaudio /dev/snd/controlC0: wolf 9336 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 07:53:43 2017 HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.12.0-13-generic N/A linux-backports-modules-4.12.0-13-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767706] Re: Ubuntu 18.04 no guest session
Confirmed. No Guest session on login screen. Ubuntu 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767706 Title: Ubuntu 18.04 no guest session Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 no option to switch to a guest session. Regression against 16.04 LTS. Usecase: let someone try Ubuntu, when giving a presentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772760] [NEW] Touchpad slows down and then stops working
Public bug reported: Cannot find a reason, but sometimes once a day, sometimes twice a day, my touchpad starts to work slowly, like jumping, and after a few seconds, it completely stops working. At some point, I did something with Terminal and it started working, but cannot reproduce it. The only thing that seems to be really working is to Suspend laptop and come back in Ubuntu (or restart, but that means to close everything + it takes more time). While I wrote this text, it seems to have recovered by itself, it is working right now, but this is unreliable and cannot be used in production (what about stopping it during a presentation, cannot suspend in a meeting). Hopefully, it is some kernel problem, as I reported kernel package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 01:15:44 2018 InstallationDate: Installed on 2018-04-27 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1772760 Title: Touchpad slows down and then stops working Status in linux-signed package in Ubuntu: New Bug description: Cannot find a reason, but sometimes once a day, sometimes twice a day, my touchpad starts to work slowly, like jumping, and after a few seconds, it completely stops working. At some point, I did something with Terminal and it started working, but cannot reproduce it. The only thing that seems to be really working is to Suspend laptop and come back in Ubuntu (or restart, but that means to close everything + it takes more time). While I wrote this text, it seems to have recovered by itself, it is working right now, but this is unreliable and cannot be used in production (what about stopping it during a presentation, cannot suspend in a meeting). Hopefully, it is some kernel problem, as I reported kernel package. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 01:15:44 2018 InstallationDate: Installed on 2018-04-27 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1772760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758205
Title:
Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
path (NVMe / Bolt ) (systemd?)
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
---Problem Description---
Bolt based NVMe disks (namespaces) are not displayed on lsblk and
/dev/disk/by-path
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
1 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n10S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
10 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n11S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
11 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n12S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
12 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n13S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
13 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n14S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
14 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n15S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
15 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n16S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
16 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n17S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
17 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n18S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
18 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n19S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
19 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n2 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
2 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n20S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
20 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n21S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
21 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n22S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
22 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n23S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
23 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n24S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
24 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n25S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
25 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n26S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
26 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n27S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
27 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n28S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
28 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n29S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
29 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n3 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
3 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n30S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
30 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n31S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
31 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n32S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
32 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n4 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
4 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n5 S3RVNA0J600206 PCIe3 1.6
[Kernel-packages] [Bug 1772564] Re: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko
I suffer from the same bug and doing: sudo apt-get install -f also fails, with the following output: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies...Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following additional packages will be installed: linux-image-4.13.0-43-generic Suggested packages: fdutils linux-tools The following NEW packages will be installed: linux-image-4.13.0-43-generic 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. 19 not fully installed or removed. Need to get 0 B/20.9 MB of archives. After this operation, 72.6 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 497058 files and directories currently installed.) Preparing to unpack .../linux-image-4.13.0-43-generic_4.13.0-43.48~16.04.1_amd64.deb ... Examining /etc/kernel/preinst.d/ Done. Unpacking linux-image-4.13.0-43-generic (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-4.13.0-43-generic_4.13.0-43.48~16.04.1_amd64.deb (--unpack): cannot copy extracted data for './boot/vmlinuz-4.13.0-43-generic' to '/boot/vmlinuz-4.13.0-43-generic.dpkg-new': failed to write (No space left on device) dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.13.0-43-generic /boot/vmlinuz-4.13.0-43-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.13.0-43-generic /boot/vmlinuz-4.13.0-43-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-4.13.0-43-generic_4.13.0-43.48~16.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772564 Title: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg- new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: I installed f-secure antivirus and this started to appear ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-43-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 22 09:54:07 2018 DuplicateSignature: package:linux-image-extra-4.13.0-43-generic:(not installed) Unpacking linux-image-extra-4.13.0-43-generic (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-4.13.0-43-generic_4.13.0-43.48~16.04.1_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-02-11 (99 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758205] Comment bridged from LTC Bugzilla
--- Comment From wenxi...@us.ibm.com 2018-05-22 17:45 EDT---
I built the latest upstream kernel on my briggs + Bolt. Looks the patch only
fixed lsblk issue. We can drop the following patch through this bug, then open
a new one for /dev/disk/by-path issue.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v4.16-rc6&id=8a30ecc6e0ecbb9ae95daf499b2680b885ed0349
If I disable NVME_MULTIPATH, I didn't see the issue. Since
NVME_MULTIPATH is new feature, probably still have some issues around.
I will work on /dev/disk/by-path issue in the new bug.
Thanks,
Wendy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758205
Title:
Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
path (NVMe / Bolt ) (systemd?)
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Incomplete
Bug description:
---Problem Description---
Bolt based NVMe disks (namespaces) are not displayed on lsblk and
/dev/disk/by-path
# nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
1 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n10S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
10 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n11S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
11 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n12S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
12 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n13S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
13 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n14S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
14 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n15S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
15 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n16S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
16 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n17S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
17 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n18S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
18 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n19S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
19 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n2 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
2 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n20S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
20 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n21S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
21 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n22S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
22 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n23S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
23 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n24S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
24 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n25S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
25 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n26S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
26 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n27S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
27 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n28S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
28 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n29S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
29 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n3 S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
3 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n30S3RVNA0J600206 PCIe3 1.6TB NVMe Flash Adapter II x8
30 28.67 GB / 28.67 GB 4 KiB + 0 B MN12MN12
/dev/nvme0n31
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Patch for kernel 4.16.10 to fix touchpad problems of Thomson X6 (revert PM / QoS: Fix device resume latency PM QoS patch) ** Patch added: "kernel-4.16.10-thomson-x6.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5143001/+files/kernel-4.16.10-thomson-x6.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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771826] Re: Creation of IMA file hashes fails when appraisal is enabled
I've tested with your kernel package and it works fine. 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/1771826 Title: Creation of IMA file hashes fails when appraisal is enabled Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: On a system that has IMA appraisal enabled it is impossible to create security.ima extended attribute files that contain IMA hash. For instance, consider the following use case: 1) extract application files to a staging area as non root user 2) verify that installation is correct 3) create IMA extended attributes for the installed files 4) move the files to their destination 5) change the files ownership to root With kernel 4.4.x step 3 will fail. The issues is fixed in upstream kernels by the following commit [1]: commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b Author: Mimi Zohar Date: Wed Nov 2 09:14:16 2016 -0400 Revert "ima: limit file hash setting by user to fix and log modes" [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i d=f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-124-generic 4.4.0-124.148 ProcVersionSignature: User Name 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 17 14:07 seq crw-rw 1 root audio 116, 33 May 17 14:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 17 14:08:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro biosdevname=0 net.ifnames=0 console=tty1 console=ttyS0 crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771344] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2018-05-22 14:42 EDT--- (In reply to comment #4) > I built a test kernel with commit 13a83eac373c49c0a081cbcd137e79210fe78acd. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1771344 > > Can you test this kernel and see if it resolves this bug? > > Note about installing test kernels: > ? If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > ? If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-image-unsigned, linux-modules and linux-modules-extra .deb packages. > > Thanks in advance! Thanks for the custom kernel. I tested it and it is working as expected: ? ~ uname -a Linux ubuntu 4.15.0-20-generic #22~lp1771344 SMP Wed May 16 18:34:49 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771344 Title: Fix enabling bridge MMIO windows Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Breno Leitao On boot we save the configuration space of PCIe bridges. We do this so when we get an EEH event and everything gets reset that we can restore them. Unfortunately we save this state before we've enabled the MMIO space on the bridges. Hence if we have to reset the bridge when we come back MMIO is not enabled and we end up taking an PE freeze when the driver starts accessing again. This patch forces the memory/MMIO and bus mastering on when restoring bridges on EEH. Ideally we'd do this correctly by saving the configuration space writes later, but that will have to come later in a larger EEH rewrite. For now we have this simple fix. The original bug can be triggered on a boston machine by doing: echo 0x8000 > /sys/kernel/debug/powerpc/PCI0001/err_injct_outbound On boston, this PHB has a PCIe switch on it. Without this patch, you'll see two EEH events, 1 expected and 1 the failure we are fixing here. The second EEH event causes the anything under the PHB to disappear (i.e. the i40e eth). With this patch, only 1 EEH event occurs and devices properly recover. This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should be part of Ubuntu 18.04 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1765564 Title: fsnotify: Fix fsnotify_mark_connector race Status in Linux: Incomplete Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Invalid Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Artful: Incomplete Status in linux-azure source package in Artful: Invalid Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Fix Released Bug description: On Azure we have had sporadic cases of soft lockups in fsnotify that may very well be mitigated by the following fix. The LKML thread is "kernel panics with 4.14.X". This should be applied to 4.13 and 4.15 versions of the linux-azure kernel, and possibly the 4.15 generic kernel in bionic as well. - fsnotify() acquires a reference to a fsnotify_mark_connector through the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it appears that no precautions are taken in fsnotify_put_mark() to ensure that fsnotify() drops its reference to this fsnotify_mark_connector before assigning a value to its 'destroy_next' field. This can result in fsnotify_put_mark() assigning a value to a connector's 'destroy_next' field right before fsnotify() tries to traverse the linked list referenced by the connector's 'list' field. Since these two fields are members of the same union, this behavior results in a kernel panic. This issue is resolved by moving the connector's 'destroy_next' field into the object pointer union. This should work since the object pointer access is protected by both a spinlock and the value of the 'flags' field, and the 'flags' field is cleared while holding the spinlock in fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be possible for another thread to accidentally read from the object pointer after the 'destroy_next' field is updated. The offending behavior here is extremely unlikely; since fsnotify_put_mark() removes references to a connector (specifically, it ensures that the connector is unreachable from the inode it was formerly attached to) before updating its 'destroy_next' field, a sizeable chunk of code in fsnotify_put_mark() has to execute in the short window between when fsnotify() acquires the connector reference and saves the value of its 'list' field. On the HEAD kernel, I've only been able to reproduce this by inserting a udelay(1) in fsnotify(). However, I've been able to reproduce this issue without inserting a udelay(1) anywhere on older unmodified release kernels, so I believe it's worth fixing at HEAD. References: https://bugzilla.kernel.org/show_bug.cgi?id=199437 Fixes: 08991e83b7286635167bab40927665a90fb00d81 CC: sta...@vger.kernel.org Signed-off-by: Robert Kolchmeyer Signed-off-by: Jan Kara To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1765564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
I also found the mapping between ubuntu versions and mainline versions and so tried mainline linux-image-4.15.17-041517-generic which also did not exhibit the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
Thanks for providing the dump. Unfortunately the Spectre system has bad thermal table values (Since Windows 10 is using more advanced tables, manufacturer didn't notice bad values impact.). So there may be more systems like this. So I want to implement some workaroud. Can you give me dump of # cat /sys/bus/acpi/devices/INT3400*/physical_node/uuids/* -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 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.06:bd10/13/2017:svn
[Kernel-packages] [Bug 1769730] Re: Some PCIe errors not surfaced through rasdaemon
** Description changed: [Impact] The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe errors to the AER (Advanced Error Reporting) driver, which surfaces them to userspace. However, we're currently only reporting "recoverable" errors and not errors of other types (e.g. correctable), thus hiding signs of faulty hardware from the user. [Test Case] $ sudo apt install rasdaemon # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the attached script to inject a correctable PCIe error. $ sudo ras-mc-ctl --errors # There should be an entry for the injected error, as shown below: No Memory errors. PCIe AER events: 1 2018-05-07 17:55:46 + Fatal error: Receiver Error No Extlog errors. No MCE errors. + [Fix] + There is a 2-patch upstream fix that addresses this issue and cleanly cherry-picks into Ubuntu. The solution is to not artficially limit which PCIe errors are reported down to the AER driver to those that are recoverable. + [Regression Risk] Above test was ran on x86 & ARM platforms to mitigate regression risk. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769730 Title: Some PCIe errors not surfaced through rasdaemon Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] The APEI (ACPI Platform Error Interface) interface is supposed to report PCIe errors to the AER (Advanced Error Reporting) driver, which surfaces them to userspace. However, we're currently only reporting "recoverable" errors and not errors of other types (e.g. correctable), thus hiding signs of faulty hardware from the user. [Test Case] $ sudo apt install rasdaemon # On a system that supports ACPI EINJ (dmesg | grep "ACPI: EINJ"), use the attached script to inject a correctable PCIe error. $ sudo ras-mc-ctl --errors # There should be an entry for the injected error, as shown below: No Memory errors. PCIe AER events: 1 2018-05-07 17:55:46 + Fatal error: Receiver Error No Extlog errors. No MCE errors. [Fix] There is a 2-patch upstream fix that addresses this issue and cleanly cherry-picks into Ubuntu. The solution is to not artficially limit which PCIe errors are reported down to the AER driver to those that are recoverable. [Regression Risk] Above test was ran on x86 & ARM platforms to mitigate regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
Christopher Penalver: > Without providing which kernels you tested nobody may understand why this > happened. I hadn't finished my testing. But i did test some of the mainline kernels below. I'm not certain that I installed them correctly. I was hoping to get the ubuntu kernels to build to see if I could get a negative result to confirm I'm testing properly. linux-image-4.15.0-041500-generic (no hdmi problem) linux-image-4.15.3-041503-generic (no hdmi problem) linux-image-4.15.18-041518-generic (no hdmi problem) > Yes, the instructions previously provided. I went to https://wiki.ubuntu.com/Kernel/KernelBisection I then went to https://launchpad.net/ubuntu/bionic/+source/linux in an attempt to install previously built kernels, and installed the packages matching the pattern linux-headers-4.13.0-17-generic_4.13.0-17.20_amd64.deb (685.9 KiB) linux-headers-4.13.0-17_4.13.0-17.20_all.deb (10.4 MiB) linux-image-4.13.0-17-generic_4.13.0-17.20_amd64.deb (19.9 MiB) once I booted this kernel the system didn't modeswitch on bootup. It didn't crash, but I dont' think it was a proper test. Finally I attempted to build from source directly (perhaps I didn't have modules for the kernel version?) I checked out from git: git clone git://kernel.ubuntu.com/ubuntu/ubuntu- bionic.git Now I attempted to follow the linked wiki page from KernelBisection https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel * sudo apt-get build-dep linux-image-$(uname -r) # this didn't work until I enabled the source repos * I have tried adding something like "+test1" to the chanelog in debian.master * I also had to install libusb-dev and libpci-dev perhaps this had something to do with me installing bionic using new minimal install option. I then did fakeroot debian/rules clean fakeroot debian/rules binary-headers binary-generic binary-perarch (which takes 45 minutes) but I only get the ../*_all.deb file. Also, should there be modules files? Sorry for the long post. I figured I had missed some instructions, thats why i asked first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wiresha
[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds
Thanks, jvandenbroek – Method 2 fixed it. Although naming a resume device leads to the same behaviour: when running `update-initramfs` it complains about "target cryptswap1 has a random key, skipped " and boot process is hanging again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460447 Title: Boot slow, "scanning for btrfs filesystems" takes 100 seconds Status in linux package in Ubuntu: Confirmed Bug description: I installed 14.10 and used btrfs for /home. Later, I did a clean install of 15.04, using the same /home partition. Ever since then, boots have been agonizingly slow; all the delay appears to be while the message "scanning for btrfs filesystems" is diplayed early in boot. The system is an i7 with one disk: root@i7:~# fdisk /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x7f84 Device Boot StartEndSectors Size Id Type /dev/sda1 * 2048 117186559 117184512 55.9G 83 Linux /dev/sda2 117186560 234373119 117186560 55.9G 83 Linux /dev/sda3 234375166 1953523711 1719148546 819.8G 5 Extended /dev/sda5 234375168 273434623 39059456 18.6G 82 Linux swap / Solaris /dev/sda6 273436672 1953523711 1680087040 801.1G 83 Linux root@i7:~# df -T | grep sd /dev/sda2 ext4 57542652 10103624 44492980 19% / /dev/sda6 btrfs840043520 172076728 665321064 21% /home I'll attach a bootchart, but I suspect the btrfs delay happens before the bootchart starts? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2176 F pulseaudio /dev/snd/controlC0: dank 2176 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 08:53:37 2015 HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223 InstallationDate: Installed on 2015-05-16 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: X58 Extreme dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
/var/run/thermald/thermal-conf.xml.auto will not be regenerated, if present, so you can edit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 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.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor:
[Kernel-packages] [Bug 1765564] 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 1765564 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 Status: New => Incomplete ** Changed in: linux (Ubuntu Artful) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1765564 Title: fsnotify: Fix fsnotify_mark_connector race Status in Linux: Incomplete Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Invalid Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Artful: Incomplete Status in linux-azure source package in Artful: Invalid Status in linux source package in Bionic: Incomplete Status in linux-azure source package in Bionic: Fix Released Bug description: On Azure we have had sporadic cases of soft lockups in fsnotify that may very well be mitigated by the following fix. The LKML thread is "kernel panics with 4.14.X". This should be applied to 4.13 and 4.15 versions of the linux-azure kernel, and possibly the 4.15 generic kernel in bionic as well. - fsnotify() acquires a reference to a fsnotify_mark_connector through the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it appears that no precautions are taken in fsnotify_put_mark() to ensure that fsnotify() drops its reference to this fsnotify_mark_connector before assigning a value to its 'destroy_next' field. This can result in fsnotify_put_mark() assigning a value to a connector's 'destroy_next' field right before fsnotify() tries to traverse the linked list referenced by the connector's 'list' field. Since these two fields are members of the same union, this behavior results in a kernel panic. This issue is resolved by moving the connector's 'destroy_next' field into the object pointer union. This should work since the object pointer access is protected by both a spinlock and the value of the 'flags' field, and the 'flags' field is cleared while holding the spinlock in fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be possible for another thread to accidentally read from the object pointer after the 'destroy_next' field is updated. The offending behavior here is extremely unlikely; since fsnotify_put_mark() removes references to a connector (specifically, it ensures that the connector is unreachable from the inode it was formerly attached to) before updating its 'destroy_next' field, a sizeable chunk of code in fsnotify_put_mark() has to execute in the short window between when fsnotify() acquires the connector reference and saves the value of its 'list' field. On the HEAD kernel, I've only been able to reproduce this by inserting a udelay(1) in fsnotify(). However, I've been able to reproduce this issue without inserting a udelay(1) anywhere on older unmodified release kernels, so I believe it's worth fixing at HEAD. References: https://bugzilla.kernel.org/show_bug.cgi?id=199437 Fixes: 08991e83b7286635167bab40927665a90fb00d81 CC: sta...@vger.kernel.org Signed-off-by: Robert Kolchmeyer Signed-off-by: Jan Kara To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1765564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Artful) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1765564 Title: fsnotify: Fix fsnotify_mark_connector race Status in Linux: Incomplete Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Invalid Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Artful: Incomplete Status in linux-azure source package in Artful: Invalid Status in linux source package in Bionic: Incomplete Status in linux-azure source package in Bionic: Fix Released Bug description: On Azure we have had sporadic cases of soft lockups in fsnotify that may very well be mitigated by the following fix. The LKML thread is "kernel panics with 4.14.X". This should be applied to 4.13 and 4.15 versions of the linux-azure kernel, and possibly the 4.15 generic kernel in bionic as well. - fsnotify() acquires a reference to a fsnotify_mark_connector through the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it appears that no precautions are taken in fsnotify_put_mark() to ensure that fsnotify() drops its reference to this fsnotify_mark_connector before assigning a value to its 'destroy_next' field. This can result in fsnotify_put_mark() assigning a value to a connector's 'destroy_next' field right before fsnotify() tries to traverse the linked list referenced by the connector's 'list' field. Since these two fields are members of the same union, this behavior results in a kernel panic. This issue is resolved by moving the connector's 'destroy_next' field into the object pointer union. This should work since the object pointer access is protected by both a spinlock and the value of the 'flags' field, and the 'flags' field is cleared while holding the spinlock in fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be possible for another thread to accidentally read from the object pointer after the 'destroy_next' field is updated. The offending behavior here is extremely unlikely; since fsnotify_put_mark() removes references to a connector (specifically, it ensures that the connector is unreachable from the inode it was formerly attached to) before updating its 'destroy_next' field, a sizeable chunk of code in fsnotify_put_mark() has to execute in the short window between when fsnotify() acquires the connector reference and saves the value of its 'list' field. On the HEAD kernel, I've only been able to reproduce this by inserting a udelay(1) in fsnotify(). However, I've been able to reproduce this issue without inserting a udelay(1) anywhere on older unmodified release kernels, so I believe it's worth fixing at HEAD. References: https://bugzilla.kernel.org/show_bug.cgi?id=199437 Fixes: 08991e83b7286635167bab40927665a90fb00d81 CC: sta...@vger.kernel.org Signed-off-by: Robert Kolchmeyer Signed-off-by: Jan Kara To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1765564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771181] Re: Ubuntu 18.04: LSI SAS93xx HBA detects incorrect bios version
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771181 Title: Ubuntu 18.04: LSI SAS93xx HBA detects incorrect bios version Status in linux package in Ubuntu: Triaged Bug description: Under /sys/class/scsi_host/host*/ "version_bios" is reported as 16.00.00.00 instead of the correct bios version 08.35.04.00. The number that is reported under the version_bios is actually the version of the package used to flash the card. Installer(SAS3FLSH) DOS:\sas3flash_dos_rel\sas3flash.exe 16.00.00.00 ProblemType: Bug lsb_release -rd: Description:Ubuntu 18.04 LTS Release:18.04 Uname: Linux Uname -r: 4.15.0-20-generic Date: Mon May 14 13:18 2018 Architecture: x86_64 Kernel driver in use: mpt3sas Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=199779
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771467
Title:
Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
Verified on multiple DL360 Gen9 servers with up to date firmware.
Just before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent
POST, the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the
doc's resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
(01/22/2018)), the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
[529153.554455] Do you have a strange power saving mode enabled?
[529153.554456] Dazed and confused, but trying to continue
[529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554458] Do you have a strange power saving mode enabled?
[529153.554458] Dazed and confused, but trying to continue
[529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554460] Do you have a strange power saving mode enabled?
[529153.554460] Dazed and confused, but trying to continue
[529154.953916] Uhhuh. NMI re
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the last kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:
v4.12 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/
v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/
v4.13-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/
v4.13 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/
You don't have to test every kernel, just up until the kernel that first
has this bug.
Thanks in advance!
** Tags added: performing-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
Confirmed
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772682] 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/1772682 Title: No sound Status in linux package in Ubuntu: Confirmed Bug description: I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have I tried to update system but the computer did not finish updating, and informed me that there is no internet connection, while the connection was OK. As a result, I still have not been any sound in the computer. Sincerely yours, Andrew. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-147-generic 3.13.0-147.196 ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39 Uname: Linux 3.13.0-147-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue May 22 19:03:51 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436 InstallationDate: Installed on 2016-01-25 (848 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5758 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-147-generic N/A linux-backports-modules-3.13.0-147-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09CGRW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5758 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/1772682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB
I built a test kernel with commit ef77b515243b3499d62cf446eda6ca7e0a0b079c. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1772575 Can you test this kernel and see if it resolves this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772575 Title: Kernel 4.4 NBD size overflow with image size exceeding 1TB Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: Release 16.04, kernel 4.4.0-124-generic There's an issue in kernel's NBD module which prevents some larger images to be correctly "connected" , largely described here: https://github.com/NetworkBlockDevice/nbd/issues/44 There is a small patch here that was accepted into mainline 4.10: https://www.spinics.net/lists/linux-block/msg07060.html This is a regression from the previous LTS 3.13 kernel. Here is a small example of the faulty behaviour: # qemu-img create -f qcow2 test.img 1100G Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 # qemu-nbd -c /dev/nbd0 test.img # blockdev --getsize64 /dev/nbd0 18446743055802302464 The correct response would be 1181116006400; this breaks most tools and makes the image unusable, e.g. # fdisk -l /dev/nbd0 fdisk: cannot open /dev/nbd0: Invalid argument --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 12:51 seq crw-rw 1 root audio 116, 33 May 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1 IwConfig: Error: [Errno 2] No such file or directory MachineType: Supermicro SYS-1028R-WTR Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_AU: TERM=xterm PATH=(custom, no user) LANG=en_AU SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.18 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-124-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 02/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: Default string dmi.board.name: X10DRW-i dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SYS-1028R-WTR dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
Sandy Patterson: >"penalvch, I'm having a bit of trouble. Is there instructions on building the ubuntu kernel from git?" Yes, the instructions previously provided. >"I wasn't able to find a mainline kernel which fails." Without providing which kernels you tested nobody may understand why this happened. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772573] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1772573 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: Upgrade to newer kernel failed via command line, I used Synaptic and there were 2 broken packages according to it. I removed/unmarked all but the current kernel "linux-image" files and that seems to have resolved the broken packages. I'm submitting this BEFORE I reboot just in case ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm pci_stub bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media rtsx_usb_ms memstick btusb btrtl btbcm btintel bluetooth rtl8723be btcoexist rtl8723_common rtl_pci rtlwifi mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp cfg80211 snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec intel_cstate intel_rapl_perf snd_hda_core mei_me mei lpc_ich ideapad_laptop sparse_keymap shpchp mac_hid rtsx_usb_sdmmc rtsx_usb nouveau i915 mxm_wmi r8169 wmi ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 22 06:18:12 2018 DpkgTerminalLog: Removing linux-modules-extra-4.15.0-20-generic (4.15.0-20.21) ... Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-4.15.0-20-generic (--remove): installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 DuplicateSignature: package:linux-image-4.15.0-20-generic:4.15.0-20.21 Removing linux-image-4.15.0-20-generic (4.15.0-20.21) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-4.15.0-20-generic (--remove): installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2015-03-07 (1171 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: installed linux-image-4.15.0-20-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-08 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772575 Title: Kernel 4.4 NBD size overflow with image size exceeding 1TB Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: Release 16.04, kernel 4.4.0-124-generic There's an issue in kernel's NBD module which prevents some larger images to be correctly "connected" , largely described here: https://github.com/NetworkBlockDevice/nbd/issues/44 There is a small patch here that was accepted into mainline 4.10: https://www.spinics.net/lists/linux-block/msg07060.html This is a regression from the previous LTS 3.13 kernel. Here is a small example of the faulty behaviour: # qemu-img create -f qcow2 test.img 1100G Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 # qemu-nbd -c /dev/nbd0 test.img # blockdev --getsize64 /dev/nbd0 18446743055802302464 The correct response would be 1181116006400; this breaks most tools and makes the image unusable, e.g. # fdisk -l /dev/nbd0 fdisk: cannot open /dev/nbd0: Invalid argument --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 12:51 seq crw-rw 1 root audio 116, 33 May 21 12:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1 IwConfig: Error: [Errno 2] No such file or directory MachineType: Supermicro SYS-1028R-WTR Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_AU: TERM=xterm PATH=(custom, no user) LANG=en_AU SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 RelatedPackageVersions: linux-restricted-modules-4.4.0-124-generic N/A linux-backports-modules-4.4.0-124-generic N/A linux-firmware 1.157.18 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-124-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 02/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: Default string dmi.board.name: X10DRW-i dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SYS-1028R-WTR dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model
I built a new test kernel and included the source package. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771844 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771844 Title: powerpc/livepatch: Implement reliable stack tracing for the consistency model Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Kamalesh Babulal - 2018-05-15 09:37:52 == Livepatch has a consistency model which is a hybrid of kGraft and kpatch: it uses kGraft's per-task consistency and syscall barrier switching combined with kpatch's stack trace switching. The current approach is stack checking of sleeping tasks. If no affected functions are on the stack of a given task, the task is patched. In most cases this will patch most or all of the tasks on the first try. Otherwise, it'll keep trying periodically. This patch implements the reliable stack tracing for consistency model a.k.a HAVE_RELIABLE_STACKTRACE. This will help in switching livepatching implementation to basic per- task consistency model. It is the foundation, which will help us enable security patches changing function or data semantics. This is the biggest remaining piece needed on ppc64le to make livepatch more generally useful. https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771799] Re: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks Joseph. The upgrade ground through after all (there were a couple of other auto-generated reports I think). I've followed your advise, though the system seems stable anyway. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771799 Title: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: Installed when prompted by Ubuntu. This seems to have been a failure owing to /boot being jam-packed with other kernels. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-signed-image-4.13.0-41-generic 4.13.0-41.46 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Thu May 17 11:48:04 2018 DuplicateSignature: package:linux-signed-image-4.13.0-41-generic:4.13.0-41.46 Setting up linux-signed-image-4.13.0-39-generic (4.13.0-39.44) ... cp: error writing '/boot/vmlinuz-4.13.0-39-generic.efi.signed': No space left on device dpkg: error processing package linux-signed-image-4.13.0-39-generic (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-06-19 (332 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: linux-signed Title: package linux-signed-image-4.13.0-41-generic 4.13.0-41.46 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2018-02-19 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772682] [NEW] No sound
Public bug reported: I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have I tried to update system but the computer did not finish updating, and informed me that there is no internet connection, while the connection was OK. As a result, I still have not been any sound in the computer. Sincerely yours, Andrew. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-147-generic 3.13.0-147.196 ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39 Uname: Linux 3.13.0-147-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue May 22 19:03:51 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436 InstallationDate: Installed on 2016-01-25 (848 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5758 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-147-generic N/A linux-backports-modules-3.13.0-147-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09CGRW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5758 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug staging trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772682 Title: No sound Status in linux package in Ubuntu: New Bug description: I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have I tried to update system but the computer did not finish updating, and informed me that there is no internet connection, while the connection was OK. As a result, I still have not been any sound in the computer. Sincerely yours, Andrew. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-147-generic 3.13.0-147.196 ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39 Uname: Linux 3.13.0-147-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue May 22 19:03:51 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436 InstallationDate: Installed on 2016-01-25 (848 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5758 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-147-generic N/A linux-backports-modules-3.13.0-147-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09CGRW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
I built Xenial, Artful and Bionic test kernels with commit 4bbaf2584b86b0772413edeac22ff448f36351b1. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1772593 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772593 Title: cpum_sf: ensure sample freq is non-zero Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Description: cpum_sf: ensure sample freq is non-zero Symptom: A kernel crash might occur. Problem: An FP divide exception during the sample rate initialization for the hardware sampling facility. Solution: Ensure that the sample frequency of the perf event attribute is non-zero. Reproduction: Run trinity against the perf_event_open() syscall. Upstream-ID: 4bbaf2584b86b0772413edeac22ff448f36351b1 Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765279] Re: Unable to build libhugetlbfs test on 4.15 Bionic
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => 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/1765279 Title: Unable to build libhugetlbfs test on 4.15 Bionic Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in linux-kvm source package in Bionic: New Bug description: When trying to build the libhugetlbfs test Bionic, it will fail with: CC32 obj32/linkhuge_nofd.o LD32 (hugelink test) obj32/linkhuge_nofd CC32 obj32/linkshare.o LD32 (hugelink test) obj32/linkshare LD32 (xB test) obj32/xB.linkhuge /usr/bin/x86_64-linux-gnu-ld: unrecognized option '--hugetlbfs-link=B' /usr/bin/x86_64-linux-gnu-ld: use the --help option for usage information collect2: error: ld returned 1 exit status Makefile:227: recipe for target 'obj32/xB.linkhuge' failed make[1]: *** [obj32/xB.linkhuge] Error 1 Makefile:242: recipe for target 'tests/all' failed make: *** [tests/all] Error 2 Steps: 1. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 2. cd libhugetlbfs 3. make ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1003-kvm 4.15.0-1003.3 ProcVersionSignature: User Name 4.15.0-1003.3-kvm 4.15.10 Uname: Linux 4.15.0-1003-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 04:44:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772564] Re: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux-hwe (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-hwe (Ubuntu) Status: New => Incomplete ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772564 Title: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg- new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: I installed f-secure antivirus and this started to appear ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-43-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 22 09:54:07 2018 DuplicateSignature: package:linux-image-extra-4.13.0-43-generic:(not installed) Unpacking linux-image-extra-4.13.0-43-generic (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-4.13.0-43-generic_4.13.0-43.48~16.04.1_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-02-11 (99 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772682] Re: No sound
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772682 Title: No sound Status in linux package in Ubuntu: Confirmed Bug description: I have Dell Inspiron 5758 with UBUNTU 14.04 LTS.have I tried to update system but the computer did not finish updating, and informed me that there is no internet connection, while the connection was OK. As a result, I still have not been any sound in the computer. Sincerely yours, Andrew. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-147-generic 3.13.0-147.196 ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39 Uname: Linux 3.13.0-147-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country RU: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) Date: Tue May 22 19:03:51 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=e4298f48-6ba8-489f-b77c-bdb717a22436 InstallationDate: Installed on 2016-01-25 (848 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5758 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-147-generic root=UUID=63a6a91d-fec3-47ee-982b-7dd7b57320f1 ro quiet splash radeon.modeset=0 nouveau.modeset=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-147-generic N/A linux-backports-modules-3.13.0-147-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 09CGRW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn09CGRW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5758 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/1772682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772564] [NEW] package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.
You have been subscribed to a public bug: I installed f-secure antivirus and this started to appear ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-43-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 22 09:54:07 2018 DuplicateSignature: package:linux-image-extra-4.13.0-43-generic:(not installed) Unpacking linux-image-extra-4.13.0-43-generic (4.13.0-43.48~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-4.13.0-43-generic_4.13.0-43.48~16.04.1_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-02-11 (99 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-package xenial -- package linux-image-extra-4.13.0-43-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-43-generic/kernel/drivers/hwmon/vt1211.ko.dpkg-new': Operation not permitted https://bugs.launchpad.net/bugs/1772564 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
** Changed in: linux (Ubuntu Cosmic) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Artful) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772593 Title: cpum_sf: ensure sample freq is non-zero Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Description: cpum_sf: ensure sample freq is non-zero Symptom: A kernel crash might occur. Problem: An FP divide exception during the sample rate initialization for the hardware sampling facility. Solution: Ensure that the sample frequency of the perf event attribute is non-zero. Reproduction: Run trinity against the perf_event_open() syscall. Upstream-ID: 4bbaf2584b86b0772413edeac22ff448f36351b1 Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772593 Title: cpum_sf: ensure sample freq is non-zero Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Description: cpum_sf: ensure sample freq is non-zero Symptom: A kernel crash might occur. Problem: An FP divide exception during the sample rate initialization for the hardware sampling facility. Solution: Ensure that the sample frequency of the perf event attribute is non-zero. Reproduction: Run trinity against the perf_event_open() syscall. Upstream-ID: 4bbaf2584b86b0772413edeac22ff448f36351b1 Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772641] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post-installation script subprocess re
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1772641 Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post- installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: Installed PyCharm from jetbrains > get this error when starting the application. Thx for your help! Pom ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 22 08:29:45 2018 ErrorMessage: installed linux-image-4.15.0-22-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-05-08 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.
Closing EOL tasks ** Changed in: linux-lts-vivid (Ubuntu) Status: Triaged => Won't Fix ** Changed in: linux-lts-vivid (Ubuntu Yakkety) Status: Confirmed => Won't Fix ** Changed in: linux-lts-xenial (Ubuntu Yakkety) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1433906 Title: Acer, Inc ID 5986:055a is useless after 14.04.2 installed. Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Fix Committed Status in linux-lts-vivid package in Ubuntu: Won't Fix Status in linux-lts-xenial package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux-lts-vivid source package in Yakkety: Won't Fix Status in linux-lts-xenial source package in Yakkety: Fix Released Status in linux package in Arch Linux: New Status in Fedora: Fix Released Bug description: CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic) CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on E450 or E555. 2. Log in system and open a terminal. 3. $ gst-launch-0.10 v4l2src ! xvimagesink Expected result: Camara is activated Actual result: $ gst-launch-0.10 v4l2src ! xvimagesink Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot identify device '/dev/video0'. Additional debug info: v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 02:21:31 2015 InstallationDate: Installed on 2015-03-16 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1433906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
yes, i can fix this in iotop, but i thin the main problem is kernel and there should not exist an empty line under /proc/PID/status Ubuntu Kernel Bot told me to send logs, but i cant run apport-collect for security/dataprotection reasons. 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/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
attached stack trace ** Attachment added: "python track trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+attachment/5142898/+files/iotop_stack_trace.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] Re: Kernel produces empty lines in /proc/PID/status
This fixes it on my machine:
--- data.py 2018-05-22 16:46:51.744204671 +0200
+++ data2.py2018-05-22 16:48:28.694497438 +0200
@@ -193,8 +193,11 @@
result_dict = {}
try:
for line in open('/proc/%d/status' % pid):
-key, value = line.split(':\t', 1)
-result_dict[key] = value.strip()
+try:
+key, value = line.split(':\t', 1)
+result_dict[key] = value.strip()
+except:
+pass
except IOError:
pass # No such process
return result_dict
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772671
Title:
Kernel produces empty lines in /proc/PID/status
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello,
after running updates today to linux-
image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that
iotop is not working any more. Reason are empty lines in
/proc/PID/status, which confuse iotop (and me)
In new view there is an empy line between Seccomp and
Speculation_Store_Bypass:
Seccomp:0
Speculation_Store_Bypass: vulnerable
Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a
relation to spectre/meltdown patches.
iotop is first application which is failing here, but iam afraid of
more.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)
> Hi, we still encounter this error in the latest 4.4.0 kernel. yes, unfortunately, the last patch seems to have helped reduce the frequency, but i did recently get another report of it happening again. So it seems to not be completely fixed. To clarify, as I said before, this is an event generated by the i40e nic firmware, and is entirely undocumented, and the firmware event provides no (useful/documented) information about what exactly happened that it didn't like. So, there is literally nothing that I, or any non-Intel person, can do to fix this. The only possible way this can be fixed is to let Intel know (which I have done) and hope they can either point me to another upstream patch that we have not yet backported, or in the case that it's still not fixed upstream (which is possible), provide a new upstream patch to fix it. Or, new firmware, of course. At this point, please don't add any more comments to this bug, since an upstream commit was backported and released for this bug (Intel pointed me to the upstrema commit). I have opened a new bug to continue this, bug 1772675. Please add new comments to that bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723127 Title: Intel i40e PF reset due to incorrect MDD detection (continues...) Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The upstream patch to fix this adjusts how the driver fragments TX data; the "malicious driver" detected by the firmware is a result of incorrectly crafted TX fragment descriptors (the firmware has specific complicated restrictions on this). The patch is from Intel, and they suggested this specific patch to address the problem; additionally I have checked with someone who reported this to me and provided a test kernel with the patch to them, and they have been able to run ~6 weeks so far without reproducing the issue; previously they could reproduce it as quickly as a day, but usually within 2-3 weeks. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] the patch for this alters how tx is fragmented by the driver, so a possible regression would likely cause problems in TX traffic and/or additional "malicious device detection" events. [original description] This is a continuation from bug 1713553; a patch was added in that bug to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. The issue is the i40e driver, when TSO is enabled, sometimes sees the NIC firmware issue a "MDD event" where MDD is "Malicious Driver Detection". This is vaguely defined in the i40e spec, but with no way to tell what the NIC actually saw that it didn't like. So, the driver can do nothing but print an error message and reset the PF (or VF). Unfortunately, this resets the interface, which causes an interruption in network traffic flow while the PF is resetting. See bug 1713553 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)
For details about i40e registers that may be able to help debug the cause of this, see bug 1723127 comment 10. Also, a (possible) workaround to avoid this error is to disable TSO on the i40e nic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
penalvch, I'm having a bit of trouble. Is there instructions on building the ubuntu kernel from git? I wasn't able to find a mainline kernel which fails. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Incomplete Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port I get a crash on bootup. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers Description: Ubuntu 18.04 LTS Release: 18.04 linux-image-4.15.0-20-generic: Installed: 4.15.0-20.21 Candidate: 4.15.0-20.21 Version table: *** 4.15.0-20.21 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 3) What you expected to happen I expected the laptop to boot to the login screen. 4) What happened instead I see a blank screen after grub and have to hard power off the laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772675] [NEW] Intel i40e PF reset due to incorrect MDD detection (continues...again...)
Public bug reported: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) 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/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] 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 1772671 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] [NEW] Kernel produces empty lines in /proc/PID/status
Public bug reported: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: xenial ** Package changed: dpkg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772671 Title: Kernel produces empty lines in /proc/PID/status Status in linux package in Ubuntu: Incomplete Bug description: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772671] [NEW] Kernel produces empty lines in /proc/PID/status
You have been subscribed to a public bug: Hello, after running updates today to linux- image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop is not working any more. Reason are empty lines in /proc/PID/status, which confuse iotop (and me) In new view there is an empy line between Seccomp and Speculation_Store_Bypass: Seccomp:0 Speculation_Store_Bypass: vulnerable Speculation_Store_Bypass seems to be new in /proc/PID/status, may be a relation to spectre/meltdown patches. iotop is first application which is failing here, but iam afraid of more. Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Kernel produces empty lines in /proc/PID/status https://bugs.launchpad.net/bugs/1772671 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770002] Re: linux-gcp: 4.13.0-1016.20 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1770002 Title: linux-gcp: 4.13.0-1016.20 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770002] Re: linux-gcp: 4.13.0-1016.20 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1770002 Title: linux-gcp: 4.13.0-1016.20 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
This bug seems related with 4.15.0-20, the test result on UEFI model for different combination of 16.04, 18.04 and their kernel are below: 18.04(d-i not subiquity) with 4.13 kerel: no screen blur 18.04(d-i not subiquity) with 4.15.22 kerenl: no screen blur 16.04 with 4.15.20 kernel screen blur 18.04(d-i) with 4.15.20 kernel screen blur Notes: 4.13 kernel come from 16.04.4 ISO 4.15.0-22 kernel come from upgrading installed 18.04 screen blur means blur screen picture for language select page Test with customized ISO which was replaced by vmlinux and initrd (new 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/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767400] Re: linux-gcp: 4.15.0-1007.7 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1767400 Title: linux-gcp: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743541] Re: Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is offline
This bug has now been closed in LP. If the issue is recurring with more recent kernels, could you raise a new defect referring back to this one (LP#1743541)? 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/1743541 Title: Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is offline Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Shriya R. Kulkarni - 2018-01-16 04:58:48 == Problem Description : = cpupower monitor fails to show stop states when cpu 0 is made offline. Testing : = root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online root@ltc-wspoon12:~# cpupower monitor WARNING: at least one cpu is offline No HW Cstate monitors found root@ltc-wspoon12:~# cpupower -c 12 monitor WARNING: at least one cpu is offline No HW Cstate monitors found root@ltc-wspoon12:~# root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online root@ltc-wspoon12:~# cpupower -c 12 monitor |Idle_Stats PKG |CORE|CPU | snoo | stop | stop | stop | stop 0| 12| 12| 0.00| 0.00| 0.00| 0.00| 0.01 Details : uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux OS : Ubuntu 18.04 Machine : Witherspoon ( DD2.1) and Boston (DD.01) Patch : Patch that fixes the issue : https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a == Comment: #1 - VIPIN K. PARASHAR - 2018-01-16 05:09:40 == (In reply to comment #0) > Patch : > > Patch that fixes the issue : > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/ > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a $ git log dbdc468f35ee827 -1 commit dbdc468f35ee827cab2753caa1c660bdb832243a Author: Abhishek Goel Date: Wed Nov 15 14:10:02 2017 +0530 cpupower : Fix cpupower working when cpu0 is offline cpuidle_monitor used to assume that cpu0 is always online which is not a valid assumption on POWER machines. This patch fixes this by getting the cpu on which the current thread is running, instead of always using cpu0 for monitoring which may not be online. Signed-off-by: Abhishek Goel Signed-off-by: Shuah Khan $ Commit dbdc468f3 is available with 4.15-rc2 onwards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1743541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769996] Re: linux-oem: 4.13.0-1027.30 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1769996 Title: linux-oem: 4.13.0-1027.30 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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-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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769997] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1769997 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770011] Re: linux: 4.4.0-125.150 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1770011 Title: linux: 4.4.0-125.150 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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-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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1770013 (linux-aws), bug 1770015 (linux-lts-xenial) derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 (linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770016] Re: linux-aws: 4.4.0-1058.67 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1770016 Title: linux-aws: 4.4.0-1058.67 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1770011 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767400] Re: linux-gcp: 4.15.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1767400 Title: linux-gcp: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769996] Re: linux-oem: 4.13.0-1027.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1769996 Title: linux-oem: 4.13.0-1027.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: 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-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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767409] Re: linux-kvm: 4.15.0-1009.9 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1767409 Title: linux-kvm: 4.15.0-1009.9 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770002] Re: linux-gcp: 4.13.0-1016.20 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1770002 Title: linux-gcp: 4.13.0-1016.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769997] Re: linux-azure: 4.13.0-1017.20 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1769997 Title: linux-azure: 4.13.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767403] Re: linux-aws: 4.15.0-1008.8 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1767403 Title: linux-aws: 4.15.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770013] Re: linux-aws: 4.4.0-1020.20 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1770013 Title: linux-aws: 4.4.0-1020.20 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1770011 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770011] Re: linux: 4.4.0-125.150 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable 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/1770011 Title: linux: 4.4.0-125.150 -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-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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1770013 (linux-aws), bug 1770015 (linux-lts-xenial) derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 (linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770019] Re: linux-kvm: 4.4.0-1024.29 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1770019 Title: linux-kvm: 4.4.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1770011 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
