[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))
Add "ath10k_core.debug_mask=0x4041" to kernel parameter and attach dmesg when the issue happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670706 Title: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32)) Status in linux package in Ubuntu: Confirmed Bug description: Disabled a wireless adapter via NetworkManager. Got a kernel trace in dmesg. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) uname -r 4.10.0-9-generic https://paste.ubuntu.com/24131142/ There are also usb hot-plug messages in between ath10k related ones - this is because I disabled a wireless adapter and immediately plugged in a usb type-c dock so don't mind those. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-9-generic 4.10.0-9.11 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dima 3007 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 7 17:28:37 2017 InstallationDate: Installed on 2017-02-27 (8 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet button.lid_init_state=open pcie_aspm=off RelatedPackageVersions: linux-restricted-modules-4.10.0-9-generic N/A linux-backports-modules-4.10.0-9-generic N/A linux-firmware1.163 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2017 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.name: Blade dmi.product.version: 6.06 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
Why do you need elantech_x551c at first place? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658345 Title: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10 Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not recognize the touchpad (it does recognize the touch screen nicely though). When I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, which recognizes the touchpad from Elantech. I searched online for days and I found Elantech drivers for Ubuntu 14.04, however, I was unable to load older versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad in future updates? I attached a screen shot of my xinput -list output. Please let me know if you require any additional information. Thank you. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: keary 2345 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656 InstallationDate: Installed on 2017-01-18 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U3 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2MCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Sofia-F dmi.board.vendor: LENOVO dmi.board.version: SDK0J91204WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad FLEX 4-1130 dmi.modalias: dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130: dmi.product.name: 80U3 dmi.product.version: Lenovo ideapad FLEX 4-1130 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698616] Re: 4.10.0-22 No longer suspends on Dell XPS 9560
I guess it's pretty similar to LP: #1697556. Try blacklisting nouveau. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698616 Title: 4.10.0-22 No longer suspends on Dell XPS 9560 Status in linux package in Ubuntu: Confirmed Bug description: I have to roll back to -21 to be able to suspend. Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May 2 14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux With -22, it doesn't suspend, and has lots of trouble with it. I expect to be able to suspend when I close the laptop lid, or when I go to suspend from the power menu. Instead the OS acts like it suspends, but the laptop doesn't power down anything. The display remains on, the fans continue to spin. It acts like it has, because it takes a bit for the keyboard to respond, and the mouse to move again, and the wifi was disconnected. It's just that the hardware doesn't power down at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704699] Re: Failed to run perf with linux-tools-4.11.0-11-generic in the proposed pocket
This is a library from binutils: binutils: /usr/lib/x86_64-linux-gnu/libbfd-2.28-system.so ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** 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/1704699 Title: Failed to run perf with linux-tools-4.11.0-11-generic in the proposed pocket Status in linux package in Ubuntu: Triaged Bug description: $ perf /usr/lib/linux-tools/4.11.0-11-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open shared object file: No such file or directory $ uname -a Linux amaura 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux It works with perf + 4.11.0-10 kernel + linux-tools-4.11.0-10-generic ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: User Name 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 04:00 seq crw-rw 1 root audio 116, 33 Jul 17 04:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jul 17 04:01:09 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703396] Re: linux: 3.13.0-125.174 -proposed tracker
** Tags removed: kernel-block-ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703396 Title: linux: 3.13.0-125.174 -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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703397 derivatives: -- swm properties -- boot-testing-requested: 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/1703396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703995] Re: linux: 4.4.0-86.109 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 - kernel-stable-phase-changed:Friday, 14. July 2017 05:33 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 17. July 2017 08:45 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 17. July 2017 08:45 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703995 Title: linux: 4.4.0-86.109 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 -- swm properties -- boot-testing-requested: 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/1703995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703396] Re: linux: 3.13.0-125.174 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703396 Title: linux: 3.13.0-125.174 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703397 derivatives: -- swm properties -- boot-testing-requested: 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/1703396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704001] Re: linux-aws: 4.4.0-1024.33 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1703995 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 17. July 2017 08:46 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1703995 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 17. July 2017 08:46 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1704001 Title: linux-aws: 4.4.0-1024.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1703995 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/1704001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701019] Re: linux: 4.8.0-59.64 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-yakkety ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701019 Title: linux: 4.8.0-59.64 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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 Yakkety: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: 1701020 -- swm properties -- boot-testing-requested: 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/1701019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703901] Re: linux: 4.11.0-11.16 -proposed tracker
4.11.0-11.16 - generic Regression test CMPL. http://kernel.ubuntu.com/testing/tracker-index.html Issue to note in amd64: hwclock - lodygin will have time changed to 2080, not a regression monotonic_time - failed on lodygin only ubuntu_blktrace_smoke_test - failed on lodygin only ubuntu_bpf - patch failed to apply, test case issue ubuntu_cts_kernel - perf tool issue, bug 1704699 ubuntu_kernel_selftests - memfd / net failed, test case issue ubuntu_kvm_unit_tests - pku, svm failed ubuntu_lttng_smoke_test - tracer not available, bug 1704720 ubuntu_lxc - Failed to start networking in ubuntu-cloud container ubuntu_seccomp - TRAP.handler failed ubuntu_unionmount_overlayfs_suite - failed on michael but passed on archytas xfstests - btrfs, xfs failed, not a regression Issue to note in arm64: hwclock - failed to change time libhugetlbfs - failed 5, killed by signal 7, bad config 1 ubuntu_bpf - patch failed to apply ubuntu_cts_kernel - perf tool issue, bug 1704699 ubuntu_kernel_selftests - bug 1680507, memfd / net failed, test case issue ubuntu_lttng_smoke_test - tracer not available, bug 1704720 ubuntu_zfs_xfs_generic - test 079, 317 failed Issue to note in i386: libhugetlbfs - failed 8, killed by signal 10, bad config 1 ubuntu_lttng_smoke_test - tracer not available, bug 1704720 ** Changed in: kernel-development-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703901 Title: linux: 4.11.0-11.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-11.16 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 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-development-workflow/+bug/1703901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703901] Re: linux: 4.11.0-11.16 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703901 Title: linux: 4.11.0-11.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-11.16 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 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-development-workflow/+bug/1703901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701697] Re: sock_recvmsg has dropped size argument
As these must be released before the associated kernels these will be
released today on an expedited schedule. They will also necessarily be
released to -security also.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701697
Title:
sock_recvmsg has dropped size argument
Status in iscsitarget package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Confirmed
Status in iscsitarget source package in Trusty:
Fix Committed
Status in iscsitarget source package in Xenial:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Bug description:
In linux-4.4.0-84, we backported commit
2da62906b1e298695e1bb725927041cd59942c98 ("[net] drop 'size' argument
of sock_recvmsg()"), which breaks building iscsitarget.
Cascardo.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: User Name 4.4.0-79.100-generic 4.4.67
Tags: xenial uec-images
Uname: Linux 4.4.0-79-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
modified.conffile..etc.iet.ietd.conf: [inaccessible: [Errno 13] Permission
denied: u'/etc/iet/ietd.conf']
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1701697/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703995] Re: linux: 4.4.0-86.109 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703995 Title: linux: 4.4.0-86.109 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 -- swm properties -- boot-testing-requested: 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/1703995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704001] Re: linux-aws: 4.4.0-1024.33 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- 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/1704001 Title: linux-aws: 4.4.0-1024.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1703995 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/1704001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704759] [NEW] linux 4.8.0-59.64 ADT test failure with linux 4.8.0-59.64
Public bug reported: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/l/linux/20170712_194618_34a6a@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure kernel-adt-failure-lts-trusty ** Tags added: kernel-adt-failure kernel-adt-failure-lts-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/1704759 Title: linux 4.8.0-59.64 ADT test failure with linux 4.8.0-59.64 Status in linux package in Ubuntu: New Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/l/linux/20170712_194618_34a6a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 264789] The Hyperloop Just Completed a Major Test. But the Real Challenges Lie Ahead
Hey friend, Hyperloop One this week announced that it completed the first full-scale test of its high-speed http://6-dreams.ch/images_rooms/wntrgrrl/media/images/banners/ministryx.php?f1f0 Bests, Mario Piccoli ** Attachment added: "07FA491269357B5FE8D8F2586E5DA865.jpg" https://bugs.launchpad.net/bugs/264789/+attachment/4916079/+files/07FA491269357B5FE8D8F2586E5DA865.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/264789 Title: USB Hard Drive Not Accessible, vol_id hangs Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Intrepid: Invalid Bug description: I updated to 2.6.27-2 today, and one of my hard drives is no longer recognized. It is in a Vantec NexStar GX enclosure, and was working fine on .26, and continues to work fine on a Hardy machine. Here is the dmesg for it: [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 27 [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice [ 6723.079511] hub 5-5:1.0: USB hub found [ 6723.080345] hub 5-5:1.0: 4 ports detected [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and address 27 [ 6733.124011] usb 5-5.1: new high speed USB device using ehci_hcd and address 28 [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices [ 6733.365818] usb-storage: device found at 28 [ 6733.365830] usb-storage: waiting for device to settle before scanning [ 6738.364276] usb-storage: device scan complete [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A 3.04 PQ: 0 ANSI: 0 [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.361002] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.371516] sdm: sdm1 [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0 [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information From there, the last 2 lines about Sense Key and Add Sense repeat over and over again. The 4 port hub that is a part of the enclosure continues to work fine though, with a floppy drive, a printer, and another hard drive. I have a Vantec NexStar 3 enclosure as well, and it is working just fine. Dmesg for the working enclosure: [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 19 [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices [ 4282.133561] usb-storage: device found at 19 [ 4282.133566] usb-storage: waiting for device to settle before scanning [ 4287.132002] usb-storage: device scan complete [ 4287.136004] scsi 12:0:0:0: Direct-Access ST375064 0AS PQ: 0 ANSI: 2 [ 4287.138368] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.144790] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.144800] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.144804] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.152388] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.154966] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.154975] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.154979] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.154988] sdi: sdi1 [ 4287.176965] sd 12:0:0:0: [sdi] Attached SCSI disk [ 4287.177173] sd 12:0:0:0: Attached scsi generic sg7 type 0 [ 4289.129138] kjournald starting. Commit interval 5 seconds [ 4289.130101] EXT3 FS on sdi1, internal journal [ 4289.130110] EXT3-fs: mounted filesystem with ordered data mode. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/264789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701697] Update Released
The verification of the Stable Release Update for iscsitarget has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701697
Title:
sock_recvmsg has dropped size argument
Status in iscsitarget package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Confirmed
Status in iscsitarget source package in Trusty:
Fix Released
Status in iscsitarget source package in Xenial:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Bug description:
In linux-4.4.0-84, we backported commit
2da62906b1e298695e1bb725927041cd59942c98 ("[net] drop 'size' argument
of sock_recvmsg()"), which breaks building iscsitarget.
Cascardo.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: User Name 4.4.0-79.100-generic 4.4.67
Tags: xenial uec-images
Uname: Linux 4.4.0-79-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
modified.conffile..etc.iet.ietd.conf: [inaccessible: [Errno 13] Permission
denied: u'/etc/iet/ietd.conf']
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1701697/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704764] [NEW] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-browse:23224]
Public bug reported: IT SUDDENLY APPEARED AND I HONESTLY HAVE NO IDEA WHAT TO DO WITH THESE. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:32:29 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-browse:23224] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-kerneloops artful i386 kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704764 Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium- browse:23224] Status in linux package in Ubuntu: Confirmed Bug description: IT SUDDENLY APPEARED AND I HONESTLY HAVE NO IDEA WHAT TO DO WITH THESE. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:32:29 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-browse:23224] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704763] [NEW] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1]
Public bug reported: IT JUST APPEARED ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:28:25 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-kerneloops artful i386 kernel-oops package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704763 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] Status in linux package in Ubuntu: Confirmed Bug description: IT JUST APPEARED ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:28:25 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704759] 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 1704759 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/1704759 Title: linux 4.8.0-59.64 ADT test failure with linux 4.8.0-59.64 Status in linux package in Ubuntu: Incomplete Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/l/linux/20170712_194618_34a6a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704763] 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/1704763 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] Status in linux package in Ubuntu: Confirmed Bug description: IT JUST APPEARED ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:28:25 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704764] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704764 Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium- browse:23224] Status in linux package in Ubuntu: Confirmed Bug description: IT SUDDENLY APPEARED AND I HONESTLY HAVE NO IDEA WHAT TO DO WITH THESE. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:32:29 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-browse:23224] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701697] Re: sock_recvmsg has dropped size argument
This bug was fixed in the package iscsitarget -
1.4.20.3+svn499-0ubuntu2.3
---
iscsitarget (1.4.20.3+svn499-0ubuntu2.3) trusty; urgency=medium
* d/p/(porting|compat|enable)-4.4.0-84.patch:
Add compat code to build with Ubuntu 4.4.0-84 (LP: #1701697)
-- Thadeu Lima de Souza Cascardo Wed, 12 Jul
2017 20:13:41 +
** Changed in: iscsitarget (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701697
Title:
sock_recvmsg has dropped size argument
Status in iscsitarget package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Confirmed
Status in iscsitarget source package in Trusty:
Fix Released
Status in iscsitarget source package in Xenial:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Bug description:
In linux-4.4.0-84, we backported commit
2da62906b1e298695e1bb725927041cd59942c98 ("[net] drop 'size' argument
of sock_recvmsg()"), which breaks building iscsitarget.
Cascardo.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: User Name 4.4.0-79.100-generic 4.4.67
Tags: xenial uec-images
Uname: Linux 4.4.0-79-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
modified.conffile..etc.iet.ietd.conf: [inaccessible: [Errno 13] Permission
denied: u'/etc/iet/ietd.conf']
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1701697/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701697] Re: sock_recvmsg has dropped size argument
This bug was fixed in the package iscsitarget -
1.4.20.3+svn502-2ubuntu4.3
---
iscsitarget (1.4.20.3+svn502-2ubuntu4.3) xenial; urgency=medium
* Fixed PATCH_MATCH in enable-4.4.0-84.patch so it will build with
4.4.0-8[0-3] kernels. (LP: #1701697)
iscsitarget (1.4.20.3+svn502-2ubuntu4.2) xenial; urgency=medium
* d/p/(porting|compat|enable)-4.4.0-84.patch:
Add compat code to build with Ubuntu 4.4.0-84 (LP: #1701697)
-- Thadeu Lima de Souza Cascardo Wed, 12 Jul
2017 19:00:05 +
** Changed in: iscsitarget (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: iscsitarget (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701697
Title:
sock_recvmsg has dropped size argument
Status in iscsitarget package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Confirmed
Status in iscsitarget source package in Trusty:
Fix Released
Status in iscsitarget source package in Xenial:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Bug description:
In linux-4.4.0-84, we backported commit
2da62906b1e298695e1bb725927041cd59942c98 ("[net] drop 'size' argument
of sock_recvmsg()"), which breaks building iscsitarget.
Cascardo.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: User Name 4.4.0-79.100-generic 4.4.67
Tags: xenial uec-images
Uname: Linux 4.4.0-79-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
modified.conffile..etc.iet.ietd.conf: [inaccessible: [Errno 13] Permission
denied: u'/etc/iet/ietd.conf']
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1701697/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701697] Re: sock_recvmsg has dropped size argument
This bug was fixed in the package iscsitarget -
1.4.20.3+svn499-0ubuntu2.3
---
iscsitarget (1.4.20.3+svn499-0ubuntu2.3) trusty; urgency=medium
* d/p/(porting|compat|enable)-4.4.0-84.patch:
Add compat code to build with Ubuntu 4.4.0-84 (LP: #1701697)
-- Thadeu Lima de Souza Cascardo Wed, 12 Jul
2017 20:13:41 +
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1701697
Title:
sock_recvmsg has dropped size argument
Status in iscsitarget package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Confirmed
Status in iscsitarget source package in Trusty:
Fix Released
Status in iscsitarget source package in Xenial:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Bug description:
In linux-4.4.0-84, we backported commit
2da62906b1e298695e1bb725927041cd59942c98 ("[net] drop 'size' argument
of sock_recvmsg()"), which breaks building iscsitarget.
Cascardo.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: User Name 4.4.0-79.100-generic 4.4.67
Tags: xenial uec-images
Uname: Linux 4.4.0-79-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
modified.conffile..etc.iet.ietd.conf: [inaccessible: [Errno 13] Permission
denied: u'/etc/iet/ietd.conf']
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1701697/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) 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/1696154 Title: [17.10 FEAT] Sign POWER host/NV kernels Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704759] Re: linux 4.8.0-59.64 ADT test failure with linux 4.8.0-59.64
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) 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/1704759 Title: linux 4.8.0-59.64 ADT test failure with linux 4.8.0-59.64 Status in linux package in Ubuntu: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/l/linux/20170712_194618_34a6a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Hello Kai-Heng Feng, Thank you for your continued efforts in this area. Unfortunately, I also have no success after installing the lp1653456+mt kernel you linked (ubuntu 17.04, dual-boot with Win10). I have the same hardware as the others in this thread: Asus ROG g752vs. After unplugging my USB mouse, xinput lists the following: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKeyid=14 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKeyid=15 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpadid=16 [slave pointer (2)] I also note the same issue with function keys (only volume controls working). One other issue that I doubt is related, but I list for completeness: the laptop is never shown as "charging" when plugged in. The system just reports that the battery is not draining. Regards, Ben -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uni
[Kernel-packages] [Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
elantech is the touchpad that Ubuntu cannot recognize. Without it, I do not have a mouse unless I use an external one or touchscreen. Also, I currently use kernel 4.8.0-45 and the touchscreen works. When I tried the kernels you provided, the touchscreen does not show up in xinput -list. In kernel 4.8.0-45 it shows up as "SYNA7300:00 06CB:177C". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658345 Title: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10 Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.10 on my Lenovo Ideapad Flex 4 laptop. Ubuntu does not recognize the touchpad (it does recognize the touch screen nicely though). When I run xinput -list, I do not see the touchpad. I dual boot with Windows 10, which recognizes the touchpad from Elantech. I searched online for days and I found Elantech drivers for Ubuntu 14.04, however, I was unable to load older versions of Ubuntu on my laptop. Do you expect to support the Elantech touchpad in future updates? I attached a screen shot of my xinput -list output. Please let me know if you require any additional information. Thank you. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: keary 2345 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=dbfec3b4-a8be-406e-9f39-5258c004c656 InstallationDate: Installed on 2017-01-18 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57fc Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U3 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=5be7438e-36fd-4960-a4cd-2371715adfa2 ro quiet splash i8042.kbdreset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2MCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Sofia-F dmi.board.vendor: LENOVO dmi.board.version: SDK0J91204WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad FLEX 4-1130 dmi.modalias: dmi:bvnLENOVO:bvr2MCN24WW:bd11/01/2016:svnLENOVO:pn80U3:pvrLenovoideapadFLEX4-1130:rvnLENOVO:rnSofia-F:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1130: dmi.product.name: 80U3 dmi.product.version: Lenovo ideapad FLEX 4-1130 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels
** Changed in: ubuntu-power-systems 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/1696154 Title: [17.10 FEAT] Sign POWER host/NV kernels Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704759] Re: linux 4.8.0-59.64 ADT test failure with linux 4.8.0-59.64
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704759 Title: linux 4.8.0-59.64 ADT test failure with linux 4.8.0-59.64 Status in linux package in Ubuntu: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/l/linux/20170712_194618_34a6a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704720] Re: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11
Checked against 4.12.0-6-generic and 4.11.0-8.13-generic, fix works fine with the regression tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704720 Title: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11 Status in linux package in Ubuntu: In Progress Bug description: After bug 1699755, this test was found failed on Artful again with kernel 4.11.0-11 $ dmesg | grep lttng [ 8282.279726] lttng_kretprobes: loading out-of-tree module taints kernel. [ 8282.279754] lttng_kretprobes: module verification failed: signature and/or required key missing - tainting kernel [ 8282.282192] lttng_tracer: Unknown symbol lttng_ftrace_unregister (err 0) [ 8282.282205] lttng_tracer: Unknown symbol lttng_ftrace_register (err 0) [ 8282.282216] lttng_tracer: Unknown symbol lttng_ftrace_destroy_private (err 0) $ sudo ./ubuntu_lttng_smoke_test.sh == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == Error: Unable to list kernel events: Kernel tracer not available Error: Command error FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event open: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event openat: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event close: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: User Name 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 04:00 seq crw-rw 1 root audio 116, 33 Jul 17 04:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jul 17 06:22:17 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704720] Re: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11
The ftrace header check for 4.12 should also be used for Ubuntu 4.11 headers. Minor fix required. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Won't Fix => In Progress ** 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/1704720 Title: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11 Status in linux package in Ubuntu: In Progress Bug description: After bug 1699755, this test was found failed on Artful again with kernel 4.11.0-11 $ dmesg | grep lttng [ 8282.279726] lttng_kretprobes: loading out-of-tree module taints kernel. [ 8282.279754] lttng_kretprobes: module verification failed: signature and/or required key missing - tainting kernel [ 8282.282192] lttng_tracer: Unknown symbol lttng_ftrace_unregister (err 0) [ 8282.282205] lttng_tracer: Unknown symbol lttng_ftrace_register (err 0) [ 8282.282216] lttng_tracer: Unknown symbol lttng_ftrace_destroy_private (err 0) $ sudo ./ubuntu_lttng_smoke_test.sh == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == Error: Unable to list kernel events: Kernel tracer not available Error: Command error FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event open: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event openat: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event close: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: User Name 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 04:00 seq crw-rw 1 root audio 116, 33 Jul 17 04:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jul 17 06:22:17 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701013] Re: linux: 4.10.0-28.32 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701013 Title: linux: 4.10.0-28.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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 Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1701014 derivatives: 1701017 -- swm properties -- boot-testing-requested: 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/1701013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701013] Re: linux: 4.10.0-28.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-zesty ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701013 Title: linux: 4.10.0-28.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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 Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1701014 derivatives: 1701017 -- swm properties -- boot-testing-requested: 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/1701013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701019] Re: linux: 4.8.0-59.64 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701019 Title: linux: 4.8.0-59.64 -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: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: 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: derivatives: 1701020 -- swm properties -- boot-testing-requested: 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/1701019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701019] Re: linux: 4.8.0-59.64 -proposed tracker
This bug was fixed in the package linux - 4.8.0-59.64 --- linux (4.8.0-59.64) yakkety; urgency=low * linux: 4.8.0-59.64 -proposed tracker (LP: #1701019) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * CVE-2017-7895 - nfsd4: minor NFSv2/v3 write decoding cleanup - nfsd: stricter decoding of write-like NFSv2/v3 ops * CVE-2017-5551 - tmpfs: clear S_ISGID when setting posix ACLs * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * CVE-2017-9150 - bpf: don't let ldimm64 leak map addresses on unprivileged * CVE-2017-5576 - drm/vc4: Fix an integer overflow in temporary allocation layout. * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * CVE-2016-9755 - netfilter: ipv6: nf_defrag: drop mangled skb on ream error * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * CVE-2017-8924 - USB: serial: io_ti: fix information leak in completion handler * CVE-2017-8925 - USB: serial: omninet: fix reference leaks at open * CVE-2017-9074 - ipv6: Check ip6_find_1stfragopt() return value properly. * CVE-2014-9900 - net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol() * OpenPower: Some multipaths temporarily have only a single path (LP: #1696445) - scsi: ses: don't get power status of SES device slot on probe -- Thadeu Lima de Souza Cascardo Thu, 29 Jun 2017 14:34:32 -0300 ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-9900 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-9755 ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000380 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5551 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5576 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7346 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7895 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8924 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8925 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9074 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9150 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9605 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701019 Title: linux: 4.8.0-59.64 -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: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: 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: derivatives: 1701020 -- swm properties -- boot-testing-requested: 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/1701019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698264] Re: Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker
This bug was fixed in the package linux - 4.8.0-59.64
---
linux (4.8.0-59.64) yakkety; urgency=low
* linux: 4.8.0-59.64 -proposed tracker (LP: #1701019)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device
* CVE-2017-7895
- nfsd4: minor NFSv2/v3 write decoding cleanup
- nfsd: stricter decoding of write-like NFSv2/v3 ops
* CVE-2017-5551
- tmpfs: clear S_ISGID when setting posix ACLs
* CVE-2017-9605
- drm/vmwgfx: Make sure backup_handle is always valid
* CVE-2017-1000380
- ALSA: timer: Fix race between read and ioctl
- ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT
* CVE-2017-9150
- bpf: don't let ldimm64 leak map addresses on unprivileged
* CVE-2017-5576
- drm/vc4: Fix an integer overflow in temporary allocation layout.
* Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu +
Docker (LP: #1698264)
- pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes
* CVE-2016-9755
- netfilter: ipv6: nf_defrag: drop mangled skb on ream error
* CVE-2017-7346
- drm/vmwgfx: limit the number of mip levels in
vmw_gb_surface_define_ioctl()
* CVE-2017-8924
- USB: serial: io_ti: fix information leak in completion handler
* CVE-2017-8925
- USB: serial: omninet: fix reference leaks at open
* CVE-2017-9074
- ipv6: Check ip6_find_1stfragopt() return value properly.
* CVE-2014-9900
- net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol()
* OpenPower: Some multipaths temporarily have only a single path
(LP: #1696445)
- scsi: ses: don't get power status of SES device slot on probe
-- Thadeu Lima de Souza Cascardo Thu, 29 Jun
2017 14:34:32 -0300
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-9900
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-9755
** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000380
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5551
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5576
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7346
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7895
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8924
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8925
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9074
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9150
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9605
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1698264
Title:
Processes in "D" state due to zap_pid_ns_processes kernel call with
Ubuntu + Docker
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Committed
Bug description:
SRU Justification
Impact: In some cases some docker processes can be stuck in the D
state after a container has terminated. They will remain in this state
until reboot.
Fix: Cherry pick upstream commit
b9a985db98961ae1ba0be169f19df1c567e4ffe0, which has already been
included as a stable commit in maintained upstream stable kernels.
Test case: See below.
Regression potential: Low, this is a simple change and as stated above
the patch has already been shipped out in upstream stable kernels.
---
(please refer to
https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
context)
Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)
Steps to reproduce:
- Install latest Docker
- Run 300 containers with health check (for i in {1..300}; do docker run -d
-it --restart=always --name poc_$i talves/health_poc; done)
- Send termination signal to the containers (docker kill -s TERM $(docker ps
-q)
- A few processes are going to be stuck in "uninterruptible sleep" ("D"
state). The only know way to recover from this is host reboot
Expected behavior:
- All containers should be terminated without any dangling process
Actual behavior:
- Some processes are left in "D" state. In our production environment this
leads over time to performance degradation and maintenance issues due to
containers that cannot be stopped / removed.
A fix is provided on kernel 4.12 - it would be nice if it could be
backported and included in the next Ubuntu release within the
supported kernel.
Thanks in advance
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 29 16:54 seq
crw-rw 1 root audio 116, 33 May 29 16:54 tim
[Kernel-packages] [Bug 1701019] Re: linux: 4.8.0-59.64 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701019 Title: linux: 4.8.0-59.64 -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: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: 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: derivatives: 1701020 -- swm properties -- boot-testing-requested: 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/1701019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699651] Re: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device
This bug was fixed in the package linux - 4.8.0-59.64 --- linux (4.8.0-59.64) yakkety; urgency=low * linux: 4.8.0-59.64 -proposed tracker (LP: #1701019) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * CVE-2017-7895 - nfsd4: minor NFSv2/v3 write decoding cleanup - nfsd: stricter decoding of write-like NFSv2/v3 ops * CVE-2017-5551 - tmpfs: clear S_ISGID when setting posix ACLs * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * CVE-2017-9150 - bpf: don't let ldimm64 leak map addresses on unprivileged * CVE-2017-5576 - drm/vc4: Fix an integer overflow in temporary allocation layout. * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * CVE-2016-9755 - netfilter: ipv6: nf_defrag: drop mangled skb on ream error * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * CVE-2017-8924 - USB: serial: io_ti: fix information leak in completion handler * CVE-2017-8925 - USB: serial: omninet: fix reference leaks at open * CVE-2017-9074 - ipv6: Check ip6_find_1stfragopt() return value properly. * CVE-2014-9900 - net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol() * OpenPower: Some multipaths temporarily have only a single path (LP: #1696445) - scsi: ses: don't get power status of SES device slot on probe -- Thadeu Lima de Souza Cascardo Thu, 29 Jun 2017 14:34:32 -0300 ** Changed in: linux (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-9900 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-9755 ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000380 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5551 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5576 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7346 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7895 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8924 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8925 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9074 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9150 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9605 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699651 Title: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: Steps: 1. Install Ubuntu 16.04 2. Search BT 4.0 devices Expected results: KILLER1435-S BT can search BT 4.0 devide normally Actual results: KILLER1435-S BT cannot search BT 4.0 devide To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1699651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696445] Re: OpenPower: Some multipaths temporarily have only a single path
This bug was fixed in the package linux - 4.8.0-59.64 --- linux (4.8.0-59.64) yakkety; urgency=low * linux: 4.8.0-59.64 -proposed tracker (LP: #1701019) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * CVE-2017-7895 - nfsd4: minor NFSv2/v3 write decoding cleanup - nfsd: stricter decoding of write-like NFSv2/v3 ops * CVE-2017-5551 - tmpfs: clear S_ISGID when setting posix ACLs * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * CVE-2017-9150 - bpf: don't let ldimm64 leak map addresses on unprivileged * CVE-2017-5576 - drm/vc4: Fix an integer overflow in temporary allocation layout. * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * CVE-2016-9755 - netfilter: ipv6: nf_defrag: drop mangled skb on ream error * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * CVE-2017-8924 - USB: serial: io_ti: fix information leak in completion handler * CVE-2017-8925 - USB: serial: omninet: fix reference leaks at open * CVE-2017-9074 - ipv6: Check ip6_find_1stfragopt() return value properly. * CVE-2014-9900 - net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol() * OpenPower: Some multipaths temporarily have only a single path (LP: #1696445) - scsi: ses: don't get power status of SES device slot on probe -- Thadeu Lima de Souza Cascardo Thu, 29 Jun 2017 14:34:32 -0300 ** Changed in: linux (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2014-9900 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-9755 ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000380 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5551 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5576 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7346 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7895 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8924 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-8925 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9074 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9150 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9605 ** Changed in: linux (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696445 Title: OpenPower: Some multipaths temporarily have only a single path Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: [Impact] * The SES driver causes a long delay in disk discovery when a large number of disks is present in the disk enclosure, which increases with the number of disks attached. * This delays the addition and visibility of the disk devices to userspace, which among other things causes multipath not to have multiple paths, actually, until the disk discovery eventually/finally finishes. * The fix significantly shortens the time taken by the SES driver to handle disk discovery, causing no extra delays, by removing a superfluous SCSI command sent to enclosure. [Test Case] * Load the module to access the enclosure and its disks; e.g., $ sudo modprobe mpt3sas * Notice the interval between the discovery of each disk; e.g., dmesg $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk * The interval should be in the same second or so range with the fix. $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Wed Jun 7 13:11:59 2017] sd 18:0:176:0: [sdly] Attached SCSI disk [Wed Jun 7 13:11:59 2017] sd 18:0:175:0: [sdlx] Attached SCSI disk [Regression Potential] * The power status of the disks in the enclosure is no longer checked during probe time. However, the patch demonstrates that initial value was never used in any way. So, little regression potential. * Nonetheless, users of SES enclosures which verify the power status of disks in the enclosure might _theoretically_ see a p
[Kernel-packages] [Bug 1696445] Re: OpenPower: Some multipaths temporarily have only a single path
This bug was fixed in the package linux - 4.8.0-59.64 --- linux (4.8.0-59.64) yakkety; urgency=low * linux: 4.8.0-59.64 -proposed tracker (LP: #1701019) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * CVE-2017-7895 - nfsd4: minor NFSv2/v3 write decoding cleanup - nfsd: stricter decoding of write-like NFSv2/v3 ops * CVE-2017-5551 - tmpfs: clear S_ISGID when setting posix ACLs * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * CVE-2017-9150 - bpf: don't let ldimm64 leak map addresses on unprivileged * CVE-2017-5576 - drm/vc4: Fix an integer overflow in temporary allocation layout. * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * CVE-2016-9755 - netfilter: ipv6: nf_defrag: drop mangled skb on ream error * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * CVE-2017-8924 - USB: serial: io_ti: fix information leak in completion handler * CVE-2017-8925 - USB: serial: omninet: fix reference leaks at open * CVE-2017-9074 - ipv6: Check ip6_find_1stfragopt() return value properly. * CVE-2014-9900 - net: Zeroing the structure ethtool_wolinfo in ethtool_get_wol() * OpenPower: Some multipaths temporarily have only a single path (LP: #1696445) - scsi: ses: don't get power status of SES device slot on probe -- Thadeu Lima de Souza Cascardo Thu, 29 Jun 2017 14:34:32 -0300 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696445 Title: OpenPower: Some multipaths temporarily have only a single path Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: [Impact] * The SES driver causes a long delay in disk discovery when a large number of disks is present in the disk enclosure, which increases with the number of disks attached. * This delays the addition and visibility of the disk devices to userspace, which among other things causes multipath not to have multiple paths, actually, until the disk discovery eventually/finally finishes. * The fix significantly shortens the time taken by the SES driver to handle disk discovery, causing no extra delays, by removing a superfluous SCSI command sent to enclosure. [Test Case] * Load the module to access the enclosure and its disks; e.g., $ sudo modprobe mpt3sas * Notice the interval between the discovery of each disk; e.g., dmesg $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk * The interval should be in the same second or so range with the fix. $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Wed Jun 7 13:11:59 2017] sd 18:0:176:0: [sdly] Attached SCSI disk [Wed Jun 7 13:11:59 2017] sd 18:0:175:0: [sdlx] Attached SCSI disk [Regression Potential] * The power status of the disks in the enclosure is no longer checked during probe time. However, the patch demonstrates that initial value was never used in any way. So, little regression potential. * Nonetheless, users of SES enclosures which verify the power status of disks in the enclosure might _theoretically_ see a problem, iff the fix has a problem (which has not been found yet). [Other Info] * None at this time. Problem Description: This week, I went ahead and scaled up my test configuration to max configuration 2x5U84_Enclosures,_MaxCfg_168HDDs. This time, it hit a different issue. The issue is that some multipaths only have a single path and no redundancy. Others have multiple paths and redundancy. Checkpoint #1: == - system reboot around 2pm (14:00) Checkpoint # 2: === - It took several minutes for first disk to be detected. root@smb1p1:~# multipath -ll|grep dm |wc -l 103 root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' | grep 'Attached SCSI disk' | tail [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk [Thu Jun 1 14:18:40 2017] sd 17:0:102:0: [sdct] Attached SCSI disk [Thu Jun 1 14:18:44 2017] sd 17:0:103:0: [sdcu] Attached SCSI disk [Thu
[Kernel-packages] [Bug 1704001] Re: linux-aws: 4.4.0-1024.33 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1704001 Title: linux-aws: 4.4.0-1024.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1703995 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/1704001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703995] Re: linux: 4.4.0-86.109 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703995 Title: linux: 4.4.0-86.109 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 -- swm properties -- boot-testing-requested: 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/1703995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701013] Re: linux: 4.10.0-28.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701013 Title: linux: 4.10.0-28.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: 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: 1701014 derivatives: 1701017 -- swm properties -- boot-testing-requested: 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/1701013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701019] Re: linux: 4.8.0-59.64 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: 1701020 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Promoted to security + kernel-stable-phase-changed:Monday, 17. July 2017 12:03 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: 1701020 -- swm properties -- boot-testing-requested: true - phase: Promoted to proposed + phase: Promoted to security proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Promoted to security - kernel-stable-phase-changed:Monday, 17. July 2017 12:03 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701019 Title: linux: 4.8.0-59.64 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: 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: derivatives: 1701020 -- swm properties -- boot-testing-requested: true phase: Promoted to security proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699627] Re: XDP eBPF programs fail to verify on Zesty ppc64el
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1700077] Re: aacraid driver may return uninitialized stack data to userspace
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1698844] Re: Fix /proc/cpuinfo revision for POWER9 DD2
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1699651] Re: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1698954] Re: HiSilicon D05: installer doesn't appear on VGA
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1698700] Re: hibmc driver does not include "pci:" prefix in bus ID
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1696031] Re: Bugfixes for hns network driver
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1696445] Re: OpenPower: Some multipaths temporarily have only a single path
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1701013] Re: linux: 4.10.0-28.32 -proposed tracker
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1695999] Re: hisi_sas driver updates
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1696165] Re: [SRU][Zesty] fix soft lockup on overcommited hugepages
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Hi Benjamin Wynne, function keys are working ok only with kernel 4.12 (with which among other problems wifi doesn't work too). On my laptop with Windows 10 charging sometimes stops at 95% or 97% with the notification "Plugged in not charging", and sometimes it goes to full 100%. With Ubuntu I have "charging", or most of the time "Battery (estimating...)". Here's what I believe is a correct explanation: https://rog.asus.com/forum/showthrea...n-Not-Charging "This is 100% normal, standard behaviour for all laptops that I have seen in the past 5 years. What you described in your post sounded more like your battery not charging at all, just discharging. What's actually happening is your computer using a standard method of battery preservation and Windows knows this, which is why it's telling you that it's plugged in but not charging - simply because it does not need to. You should actually worry about your battery being at 100%, not about it being at less than that. The idea is that once the battery hits around 95-98% charge, charging stops in order to prevent battery life loss as these batteries should not be charged to full. This is controlled by the built-in power/energy controller. Once it hits that point the battery begins being trickle charged, just enough to keep it at a steady level. Otherwise you would see the battery drop to 97, 96, 95 etc as each day passes by. Your battery continues to be charged extremely slowly to keep it at 98% until you actually use the battery. In order to make sure your battery will last as long as possible, fully discharge it once a month. It'll last years. You were almost going to try "fixing" your 100% functional battery, heh. At least you spared yourself the laugh the tech people would have given you at the computer store. You have nothing to worry about." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/
[Kernel-packages] [Bug 1696143] Re: [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy driver.
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1698264] Re: Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support
This bug was fixed in the package linux - 4.10.0-28.32 --- linux (4.10.0-28.32) zesty; urgency=low * linux: 4.10.0-28.32 -proposed tracker (LP: #1701013) * KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651) - Bluetooth: btusb: Add support for 0489:e0a2 QCA_ROME device * aacraid driver may return uninitialized stack data to userspace (LP: #1700077) - SAUCE: scsi: aacraid: Don't copy uninitialized stack memory to userspace * CVE-2017-9605 - drm/vmwgfx: Make sure backup_handle is always valid * CVE-2017-1000380 - ALSA: timer: Fix race between read and ioctl - ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT * XDP eBPF programs fail to verify on Zesty ppc64el (LP: #1699627) - [Config] ppc64el: build for Power8 not Power7 * AACRAID for power9 platform (LP: #1689980) - scripts/spelling.txt: add "therfore" pattern and fix typo instances - scsi: aacraid: fix PCI error recovery path - scsi: aacraid: pci_alloc_consistent() failures on ARM64 - scsi: aacraid: Remove __GFP_DMA for raw srb memory - scsi: aacraid: Fix DMAR issues with iommu=pt - scsi: aacraid: Added 32 and 64 queue depth for arc natives - scsi: aacraid: Set correct Queue Depth for HBA1000 RAW disks - scsi: aacraid: Remove reset support from check_health - scsi: aacraid: Change wait time for fib completion - scsi: aacraid: Log count info of scsi cmds before reset - scsi: aacraid: Print ctrl status before eh reset - scsi: aacraid: Using single reset mask for IOP reset - scsi: aacraid: Rework IOP reset - scsi: aacraid: Add periodic checks to see IOP reset status - scsi: aacraid: Rework SOFT reset code - scsi: aacraid: Rework aac_src_restart - scsi: aacraid: Use correct function to get ctrl health - scsi: aacraid: Make sure ioctl returns on controller reset - scsi: aacraid: Enable ctrl reset for both hba and arc - scsi: aacraid: Add reset debugging statements - scsi: aacraid: Remove reference to Series-9 - scsi: aacraid: Update driver version to 50834 * arm64 kernel crashdump support (LP: #1694859) - memblock: add memblock_clear_nomap() - memblock: add memblock_cap_memory_range() - arm64: limit memory regions based on DT property, usable-memory-range - arm64: kdump: reserve memory for crash dump kernel - arm64: mm: add set_memory_valid() - arm64: mm: use phys_addr_t instead of unsigned long in __map_memblock - arm64: kdump: protect crash dump kernel memory - arm64: hibernate: preserve kdump image around hibernation - arm64: kdump: implement machine_crash_shutdown() - arm64: kdump: add VMCOREINFO's for user-space tools - [Config] CONFIG_CRASH_DUMP=y on arm64 - arm64: kdump: provide /proc/vmcore file - Documentation: kdump: describe arm64 port - Documentation: dt: chosen properties for arm64 kdump - efi/libstub/arm*: Set default address and size cells values for an empty dtb * hibmc driver does not include "pci:" prefix in bus ID (LP: #1698700) - SAUCE: drm: hibmc: Use set_busid function from drm core * Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker (LP: #1698264) - pid_ns: Sleep in TASK_INTERRUPTIBLE in zap_pid_ns_processes * Bugfixes for hns network driver (LP: #1696031) - hns_enet: use cpumask_var_t for on-stack mask - net: hns: fix uninitialized data use - net: hns: avoid gcc-7.0.1 warning for uninitialized data - net: hns: Add ACPI support to check SFP present - net: hns: Fix the implementation of irq affinity function - net: hns: Modify GMAC init TX threshold value - net: hns: Optimize the code for GMAC pad and crc Config - net: hns: Remove redundant memset during buffer release - net: hns: bug fix of ethtool show the speed - net: hns: Optimize hns_nic_common_poll for better performance - net: hns: Fix to adjust buf_size of ring according to mtu - net: hns: Replace netif_tx_lock to ring spin lock - net: hns: Correct HNS RSS key set function - net: hns: Remove the redundant adding and deleting mac function - net: hns: Remove redundant mac_get_id() - net: hns: Remove redundant mac table operations - net: hns: Clean redundant code from hns_mdio.c file - net: hns: Optimise the code in hns_mdio_wait_ready() - net: hns: Simplify the exception sequence in hns_ppe_init() - net: hns: Adjust the SBM module buffer threshold - net: hns: Avoid Hip06 chip TX packet line bug - net: hns: Some checkpatch.pl script & warning fixes - net: hns: support deferred probe when can not obtain irq - net: hns: support deferred probe when no mdio - net: hns: fix ethtool_get_strings overflow in hns driver * CVE-2017-7346 - drm/vmwgfx: limit the number of mip levels in vmw_gb_surface_define_ioctl() * [SRU][Zesty] qcom_emac is unable to get ip address with at803x phy
[Kernel-packages] [Bug 1704374] Re: system randomly hangs itself
@kai I'm using the usual way after managing every dimms to test them by memtest singly, coupled and together. IF the problem should occur again I'll apply the workaround. However I've just red some interesting news about 4.13 kernel on improvements on power management.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704374 Title: system randomly hangs itself Status in linux package in Ubuntu: Incomplete Bug description: this problem affect my system on Kubuntu 17.04 64bit Kde Plasma: 5.10.3 kernel: 4.10.0.26 Kde frameworks: 5.36.0 Qt release: 5.7.1 Probably I've solved with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1" Randomly the operating system hangs both eist and or c1e options enabled or disabled. I hope that Kubuntu has not damaged my hardware. However what kind of workaround should be made on the klernel to have this problem solved once and forever? My hardware specs: maximus eteme; latest bios; 8gb ram 4x2gb corsaire xms 1333; gigabyte gt 730 1gb OC xonar d2x. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic 4.10.0-26.30 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 1353 F pulseaudio /dev/snd/controlC1: james 1353 F pulseaudio CurrentDesktop: KDE Date: Fri Jul 14 12:39:32 2017 InstallationDate: Installed on 2017-04-25 (79 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer Maximus Extreme ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=52f9b441-fe75-4643-bbec-f912736d397b ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Maximus Extreme dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/24/2009:svnSystemmanufacturer:pnMaximusExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: Maximus Extreme dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset
** Description changed: + SRU Justification + + Impact: The redpine driver in xenial has been updated, and a + corresponding firmware update is also required. + + Fix: Add new firmware files. + + Test case: Test with affected hw and with a kernel which has the driver + update. + + Regression potential: These are new files used by a single driver, so no + regressions are possible outside of that driver. + + --- + Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git ** Also affects: linux-firmware (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: Triaged => Invalid ** Changed in: linux-firmware (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701013] Re: linux: 4.10.0-28.32 -proposed tracker
** 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/1701013 Title: linux: 4.10.0-28.32 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: 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: 1701014 derivatives: 1701017 -- swm properties -- boot-testing-requested: true phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704763] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1]
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 (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704763 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] Status in linux package in Ubuntu: Incomplete Bug description: IT JUST APPEARED ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:28:25 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704471] Re: package linux-image-4.10.0-26-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
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 (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704471 Title: package linux-image-4.10.0-26-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Non so perché si è verificato questo errore ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-lowlatency (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15 Uname: Linux 4.10.0-24-lowlatency i686 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vittorio 1238 F pulseaudio /dev/snd/controlC0: vittorio 1238 F pulseaudio Date: Fri Jul 14 19:33:03 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=0e09baa8-8c43-499d-8006-7275dc5c1086 InstallationDate: Installed on 2017-05-08 (67 days ago) InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release i386 (20161012.1) MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-lowlatency root=UUID=5395e556-416c-40c3-a8ef-6790431337c1 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~beta3-4ubuntu2.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-26-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-06-16 (28 days ago) dmi.bios.date: 06/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704718] Re: random freeze of AMD Ryzen based workstations
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 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.13-rc1/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704718 Title: random freeze of AMD Ryzen based workstations Status in linux package in Ubuntu: Incomplete Bug description: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704470] Re: playback fails using alsa in mpd
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 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.13-rc1/
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: needs-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/1704470
Title:
playback fails using alsa in mpd
Status in linux package in Ubuntu:
Incomplete
Bug description:
Using 4.11.0-10.15 kernel from playback fails using this mpd.conf
##Pulseaudio
#audio_output {
# type "pulse"
# name "Local MPD"
# server "127.0.0.1"
#}
##Alsa
audio_output {
type "alsa"
name "Cambridge Audio DAC100 USB 2 - USB Audio"
device "hw:1,0"
auto_resample "no"
auto_format "no"
auto_channels "no"
replay_gain_handler "none"
mixer_type "none"
}
If I reboot into 4.10.0-26 then playback with alsa works.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.11.0-10-generic 4.11.0-10.15
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wolf 1742 F pulseaudio
/dev/snd/pcmC1D0p: wolf 1742 F...m pulseaudio
/dev/snd/controlC1: wolf 1742 F pulseaudio
CurrentDesktop: XFCE
Date: Fri Jul 14 20:27:17 2017
HibernationDevice: RESUME=UUID=9f10a8f1-df29-4691-b2cc-7fbe68244587
MachineType: NOVATECH LTD MBB-44608
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic
root=UUID=c81d4267-4905-4511-9011-d51db8eb0c3a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.11.0-10-generic N/A
linux-backports-modules-4.11.0-10-generic N/A
linux-firmware 1.167
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: 7383241-001
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: V1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
dmi.product.name: MBB-44608
dmi.product.version: V1.0
dmi.sys.vendor: NOVATECH LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704470/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704764] Re: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-browse:23224]
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 (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704764 Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium- browse:23224] Status in linux package in Ubuntu: Incomplete Bug description: IT SUDDENLY APPEARED AND I HONESTLY HAVE NO IDEA WHAT TO DO WITH THESE. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4852 F pulseaudio yoogeun8331 F pulseaudio Date: Mon Jul 17 16:32:29 2017 Failure: oops HibernationDevice: RESUME=UUID=4959b0ef-4074-4fad-a92e-aa2dbedbcc41 InstallationDate: Installed on 2016-10-06 (283 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LG Electronics 15ZD960-GX36K ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [chromium-browse:23224] UpgradeStatus: Upgraded to artful on 2017-06-02 (45 days ago) dmi.bios.date: 02/17/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 15ZA1570 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z960 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr15ZA1570X64:bd02/17/2016:svnLGElectronics:pn15ZD960-GX36K:pvr0.1:rvnLGElectronics:rn15Z960:rvrFAB1:cvnLGElectronics:ct9:cvr0.1: dmi.product.name: 15ZD960-GX36K dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704435] Re: [Xenial] nvme: Quirks for PM1725 controllers
** Tags added: kernel-da-key ** Tags added: artful xenial yakkety zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704435 Title: [Xenial] nvme: Quirks for PM1725 controllers Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Triaged Bug description: == SRU Xenial == Pick up the following device quirk to resolve a hardware/firmware bug affectung some NVMe drives that use the PM1725 controller. Under adverse circumstances the bug can result in data corruption and loss. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d554b5e1ca64d23e4f839e6531490fee8479fbaf nvme: Quirks for PM1725 controllers PM1725 controllers have a couple of quirks that need to be handled in the driver: - I/O queue depth must be limited to 64 entries on controllers that do not report MQES. - The host interface registers go offline briefly while resetting the chip. Thus a delay is needed before checking whether the controller is ready. Note that the admin queue depth is also limited to 64 on older versions of this board. Since our NVME_AQ_DEPTH is now 32 that is no longer an issue. Signed-off-by: Martin K. Petersen Signed-off-by: Sagi Grimberg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701271] Re: linux: 4.11.0-10.15 -proposed tracker
** 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/1701271 Title: linux: 4.11.0-10.15 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: This bug is for tracking the 4.11.0-10.15 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 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1701271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704614] Re: very long kernel boot time with some KVM switch
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 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.13-rc1/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704614 Title: very long kernel boot time with some KVM switch Status in linux package in Ubuntu: Incomplete Bug description: I am using a Aten KVM switch CS1794 hooked on my computer. It allows the switching for USB, HDMI, and audio. http://www.aten.com/global/en/products/kvm/desktop-kvm-switches/cs1794/#.WWrnguk9iUk I run a Ubuntu 17.04 system. I experience a very long boot time, having done an analysis it appears that the main problem is the kernel boot time and more specifically the time it takes to start its USB subsystem. when you look at the dsmg output you can clearly see a gap between 4-78s and 79-91s, all in the USB sub-process. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: stranche 3670 F pulseaudio /dev/snd/controlC1: stranche 3670 F pulseaudio /dev/snd/controlC0: stranche 3670 F pulseaudio DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=28d4f703-2b20-4dd3-ba8b-aa363ad5141d InstallationDate: Installed on 2017-07-14 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=4fde9883-6d7f-4954-90d6-779f37bbdc93 ro console=tty console=ttyUSB0,57600 noplymouth debug ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH Z77 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704479] Re: Change CONFIG_IBMVETH to module
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Artful) Importance: Medium Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: 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/1704479 Title: Change CONFIG_IBMVETH to module Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: == Comment: #0 - Breno Leitao - 2017-07-14 15:07:47 == Dear Canonical, Please change the CONFIG_IBMVETH=y to module on artful kernel. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704430] Re: Middle mouse button lost function after Upgrade to Mint 18.2
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 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.13-rc1/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704430 Title: Middle mouse button lost function after Upgrade to Mint 18.2 Status in linux package in Ubuntu: Incomplete Bug description: It looks an old bug report (#1581088) is back. I recently upgraded from 18.1 to 18.2 and lost my middle mouse button of a Bluetooth Mouse "Logitech M557" Searching for root cause I found this bug report #1581088. Following resolution attemps I could figure the same root cause and solution. After upgrade : >> xinput list-props 12 Device 'Bluetooth Mouse M557': Device Enabled (138): 1 Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (264): 0 Device Accel Constant Deceleration (265): 1.00 Device Accel Adaptive Deceleration (266): 1.00 Device Accel Velocity Scaling (267):10.00 Device Product ID (259):1133, 45072 Device Node (260): "/dev/input/event12" Evdev Axis Inversion (387): 0, 0 Evdev Axes Swap (389): 0 Axis Labels (390): "Rel X" (148), "Rel Y" (149), "Rel Horiz Wheel" (385), "Rel Vert Wheel" (386) Button Labels (391):"Button Left" (141), "Button Middle" (142), "Button Right" (143), "Button Wheel Up" (144), "Button Wheel Down" (145), "Button Horiz Wheel Left" (146), "Button Horiz Wheel Right" (147), "Button Side" (380), "Button Extra" (381), "Button Forward" (382), "Button Back" (383), "Button Task" (384), "Button Unknown" (379), "Button Unknown" (379), "Button Unknown" (379), "Button Unknown" (379) Evdev Scrolling Distance (392): 1, 1, 1 Evdev Middle Button Emulation (393):1 Evdev Middle Button Timeout (394): 50 Evdev Third Button Emulation (395): 0 Evdev Third Button Emulation Timeout (396): 1000 Evdev Third Button Emulation Button (397): 3 Evdev Third Button Emulation Threshold (398): 20 Evdev Wheel Emulation (399):1 Evdev Wheel Emulation Axes (400): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (401):10 Evdev Wheel Emulation Timeout (402):200 Evdev Wheel Emulation Button (403): 4 Evdev Drag Lock Buttons (404): 0 The porperty 399 (Evdev Wheel Emulation) was set to "0", even in in the gnome-tweak-tool is has been enabled. After setting this property to "1" with >> xinput --set-prop 12 399 1 my middle mouse button is working as expected. May be worth to mention: I'am running the following kernel: >> uname -r 4.10.0-26-generic Joerg --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuxm 2962 F pulseaudio /dev/snd/pcmC1D0p: tuxm 2962 F...m pulseaudio /dev/snd/controlC1: tuxm 2962 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.2 InstallationDate: Installed on 2017-01-31 (163 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 8087:07da Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W840SU Series Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=0da4509d-87d9-4ebd-ad23-484e8af643ec ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 Tags: sonya Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1704469] Re: r8169 0000:02:00.0: invalid large VPD tag 7f at offset 0
** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704469 Title: r8169 :02:00.0: invalid large VPD tag 7f at offset 0 Status in linux package in Ubuntu: Incomplete Bug description: dmesg: [ 1025.813826] r8169 :02:00.0: invalid large VPD tag 7f at offset 0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1801 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 15:30:03 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (9 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-07-05 (8 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701013] Re: linux: 4.10.0-28.32 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1701014 derivatives: 1701017 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Monday, 17. July 2017 12:33 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1701014 derivatives: 1701017 -- swm properties -- boot-testing-requested: true - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Monday, 17. July 2017 12:33 UTC - kernel-stable-phase: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/1701013 Title: linux: 4.10.0-28.32 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: 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: 1701014 derivatives: 1701017 -- swm properties -- boot-testing-requested: true phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704479] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2017-07-17 08:40 EDT--- Canonical, we also need this fix backported to Zesty. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704479 Title: Change CONFIG_IBMVETH to module Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: == Comment: #0 - Breno Leitao - 2017-07-14 15:07:47 == Dear Canonical, Please change the CONFIG_IBMVETH=y to module on artful kernel. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704363] Re: Add firmware for Redpine 9113 chipset
** Changed in: linux-firmware (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1704363 Title: Add firmware for Redpine 9113 chipset Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The redpine driver in xenial has been updated, and a corresponding firmware update is also required. Fix: Add new firmware files. Test case: Test with affected hw and with a kernel which has the driver update. Regression potential: These are new files used by a single driver, so no regressions are possible outside of that driver. --- Latest firmware images provided by Redpine in 1.2 production release are updated to ubuntu's linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1704363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702912] Re: linux: 4.4.0-84.107 -proposed tracker
** 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/1702912 Title: linux: 4.4.0-84.107 -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug is for tracking the 4.4.0-84.107 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687273] Re: Shared folder randomly not mounted
The patch posted in comment #19 was included in mainline as commit 62a6cfddcc0a5313e7da3e8311ba16226fe0ac10 and was cc'd to upstream stable. This commit is in the Ubuntu-4.4.0-79.100 kernel. Can you apply the latest updates and see if this bug is resolved? ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cifs-utils (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** 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 the bug report. https://bugs.launchpad.net/bugs/1687273 Title: Shared folder randomly not mounted Status in Linux: Unknown Status in cifs-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in cifs-utils source package in Xenial: New Status in linux source package in Xenial: In Progress Status in linux package in Debian: Fix Released Bug description: Hello Everybody, since last update from ubuntu 16.04.2, last night, my servers are randomly not able to read and write from shared folders. I got this message: lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. ... rsync: ERROR: cannot stat destination "/mnt/record/": Host is down (112) rsync error: errors selecting input/output files, dirs (code 3) at main.c(652) [Receiver=3.1.1] This comes from my cron script. When I type df -h it takes sometimes very long to get the list. And it also can be that the mounted share is disconnected and I have to mount -a (what also takes long) again. My fstab have this command: //address /mnt/storage cifs auto,nofail,iocharset=utf8,rw,credentials=/path/.smb,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0 0 My update list from last night was this: linux-image-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-image-extra-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75:amd64 (4.4.0-75.96, automatic) Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-headers-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-libc-dev:amd64 (4.4.0-72.93, 4.4.0-75.96) mysql-client-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libapt-inst2.0:amd64 (1.2.19, 1.2.20) mysql-server-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17) linux-image-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) apt:amd64 (1.2.19, 1.2.20) mysql-server:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) udev:amd64 (229-4ubuntu16, 229-4ubuntu17) libapt-pkg5.0:amd64 (1.2.19, 1.2.20) libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17) cifs-utils:amd64 (2:6.4-1ubuntu1, 2:6.4-1ubuntu1.1) dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-client-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17) distro-info-data:amd64 (0.28ubuntu0.2, 0.28ubuntu0.3) systemd:amd64 (229-4ubuntu16, 229-4ubuntu17) mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) apt-utils:amd64 (1.2.19, 1.2.20) libmysqlclient20:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) linux-headers-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-image-extra-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) thermald:amd64 (1.5-2ubuntu3, 1.5-2ubuntu4) qemu-guest-agent:amd64 (1:2.5+dfsg-5ubuntu10.10, 1:2.5+dfsg-5ubuntu10.11) libfreetype6:amd64 (2.6.1-0.1ubuntu2.1, 2.6.1-0.1ubuntu2.2) linux-image-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) libdpkg-perl:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-server-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1) dpkg-dev:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) I saw that somebody else has the same problem: https://askubuntu.com/questions/910058/updates-broke-cifs-smb-mounts- in-16-04 I had to remove the latest kernel update, after that it works. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1687273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@l
[Kernel-packages] [Bug 1704470] Re: playback fails using alsa in mpd
@jsalisbury - I will try - but it appears to be rather intermittent - so
not actually convinced of where the issue is.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704470
Title:
playback fails using alsa in mpd
Status in linux package in Ubuntu:
Incomplete
Bug description:
Using 4.11.0-10.15 kernel from playback fails using this mpd.conf
##Pulseaudio
#audio_output {
# type "pulse"
# name "Local MPD"
# server "127.0.0.1"
#}
##Alsa
audio_output {
type "alsa"
name "Cambridge Audio DAC100 USB 2 - USB Audio"
device "hw:1,0"
auto_resample "no"
auto_format "no"
auto_channels "no"
replay_gain_handler "none"
mixer_type "none"
}
If I reboot into 4.10.0-26 then playback with alsa works.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.11.0-10-generic 4.11.0-10.15
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wolf 1742 F pulseaudio
/dev/snd/pcmC1D0p: wolf 1742 F...m pulseaudio
/dev/snd/controlC1: wolf 1742 F pulseaudio
CurrentDesktop: XFCE
Date: Fri Jul 14 20:27:17 2017
HibernationDevice: RESUME=UUID=9f10a8f1-df29-4691-b2cc-7fbe68244587
MachineType: NOVATECH LTD MBB-44608
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic
root=UUID=c81d4267-4905-4511-9011-d51db8eb0c3a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.11.0-10-generic N/A
linux-backports-modules-4.11.0-10-generic N/A
linux-firmware 1.167
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: 7383241-001
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: V1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
dmi.product.name: MBB-44608
dmi.product.version: V1.0
dmi.sys.vendor: NOVATECH LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704470/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698844] Re: Fix /proc/cpuinfo revision for POWER9 DD2
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1698844 Title: Fix /proc/cpuinfo revision for POWER9 DD2 Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2017-06-19 09:44:36 == The P9 PVR bits 12-15 don't indicate a revision but instead different chip configurations. From BookIV we have: Bits Configuration 0 :Scale out 12 cores 1 :Scale out 24 cores 2 :Scale up 12 cores 3 :Scale up 24 cores DD1 doesn't use this but DD2 does. Linux will mostly use the "Scale out 24 core" configuration (ie. SMT4 not SMT8) which results in a PVR of 0x004e1200. The reported revision in /proc/cpuinfo is hence reported incorrectly as "18.0". This patch fixes this to mask off only the relevant bits for the major revision (ie. bits 8-11) for POWER9. Please cherry pick: https://patchwork.ozlabs.org/patch/776052/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1698844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700521] Re: powerpc: Invalidate ERAT on powersave wakeup for POWER9
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700521 Title: powerpc: Invalidate ERAT on powersave wakeup for POWER9 Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2017-06-23 13:13:02 == Hello, This is a patch that we need to have on Zesty, including on the 16.04.3 installer. On POWER9 the ERAT may be incorrect on wakeup from some stop states that lose state. This causes random segvs and illegal instructions when these stop states are enabled. This patch invalidates the ERAT on wakeup on POWER9 to prevent this from causing a problem. URL: https://patchwork.ozlabs.org/patch/780365/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1700521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689360] Re: TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly calculating base_command_size
** Changed in: linux (Ubuntu)
Status: New => Triaged
** 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/1689360
Title:
TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly
calculating base_command_size
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Triaged
Bug description:
---Problem Description---
If there has BIDI data, its first iov[] will overwrite the last
iov[] for se_cmd->t_data_sg.
---uname output---
Latest Yakkety master branch
Machine Type = P8
---Steps to Reproduce---
Just have a system do workload using tcmu.
Stack trace output:
I have seen this in my environment:
(gdb) print *((tcmulib_cmd->iovec)+0)
$7 = {iov_base = 0x3fff7c3d, iov_len = 8192}
(gdb) print *((tcmulib_cmd->iovec)+1)
$3 = {iov_base = 0x3fff7c3da000, iov_len = 4096}
(gdb) print *((tcmulib_cmd->iovec)+2)
$4 = {iov_base = 0x3fff7c3dc000, iov_len = 16384}
(gdb) print *((tcmulib_cmd->iovec)+3)
$5 = {iov_base = 0x3fff7c3f7000, iov_len = 12288}
(gdb) print *((tcmulib_cmd->iovec)+4)
$6 = {iov_base = 0x1306e853c0028, iov_len = 128} <--- bad pointer and length
cmu: Fix wrongly calculating of the base_command_size
https://patchwork.kernel.org/patch/9687657/
tcmu: Fix possible overwrite of t_data_sg's last iov[]
https://patchwork.kernel.org/patch/9687565/
tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI
case
https://patchwork.kernel.org/patch/9655423/
This patch should also be a part of these fixes. WITH BIDI op fixes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689360/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672782] Re: Graphics trouble after hibernation or Sleep
Added tag kernel-fixed-upstream ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672782 Title: Graphics trouble after hibernation or Sleep Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Edges around windows get pixelated ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abhilash 2353 F pulseaudio /dev/snd/controlC0: abhilash 2353 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 11:52:03 2017 HibernationDevice: RESUME=UUID=e086eed9-3076-4bc3-b94b-8674e530b351 InstallationDate: Installed on 2016-12-28 (75 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20378 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=2e21e919-a77e-41b5-889c-9339d654e040 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN30WW(V1.13) dmi.board.asset.tag: 31900058Std dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: 31900058Std dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN30WW(V1.13):bd07/16/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704479] Re: Change CONFIG_IBMVETH to module
** Changed in: ubuntu-power-systems Status: New => 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/1704479 Title: Change CONFIG_IBMVETH to module Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: == Comment: #0 - Breno Leitao - 2017-07-14 15:07:47 == Dear Canonical, Please change the CONFIG_IBMVETH=y to module on artful kernel. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1704479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
Do you have an update about this 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/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel. This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77 kdump-tools 1:1.5.9-5ubuntu0.4 makedumpfile1:1.5.9-5ubuntu0.4 linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1 # kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2b00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-46-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz The kernel trace [ 10.738064] BUG: unable to handle kernel NULL pointer dereference at 0088 [ 10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.743571] PGD 0 [ 10.744482] Oops: [#1] SMP [ 10.745615] Modules linked in: [ 10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic #49~16.04.1-Ubuntu [ 10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [ 10.752574] task: 8f16b2938ec0 task.stack: 8f16b294 [ 10.754892] RIP: 0010:[] [] hswep_uncore_cpu_init+0x52/0xa0 [ 10.758371] RSP: 0018:8f16b2943e40 EFLAGS: 00010206 [ 10.760337] RAX: 0050 RBX: RCX: 238a [ 10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: [ 10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 89231a97 [ 10.767968] R10: eac07000 R11: R12: 89c1a030 [ 10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 8f16b2c19300 [ 10.772894] FS: () GS:8f16b2c0() knlGS: [ 10.775945] CS: 0010 DS: ES: CR0: 80050033 [ 10.777935] CR2: 0088 CR3: 2d806000 CR4: 001406f0 [ 10.780398] Stack: [ 10.781154] 8f16b2943e50 df388e 8f16b2943e88 89d8b292 [ 10.884602] 0105 89d8b196 89c0daf8 [ 10.887394] 8f16b2c19300 8f16b2943f08 88e02190 88ea377f [ 10.890699] Call Trace: [ 10.891596] [] intel_uncore_init+0xfc/0x2d6 [ 10.893587] [] do_one_initcall+0x50/0x1a0 [ 11.397431] [] ? parse_args+0x2cf/0x490 [ 11.399313] [] kernel_init_freeable+0x178/0x217 [ 11.402112] [] kernel_init+0xe/0x100 [ 11.404013] [] ret_from_fork+0x1f/0x40 [ 11.405895] [] ? rest_init+0x80/0x80 [ 11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00 [ 11.422367] RIP [] hswep_uncore_cpu_init+0x52/0xa0 [ 11.425174] RSP [ 11.426588] CR2: 0088 [ 11.427978] ---[ end trace d8adbfe4355f5160 ]--- [ 11.430006] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.430006] [ 11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.433354] Please find the full kernel trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696445] Re: OpenPower: Some multipaths temporarily have only a single path
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696445 Title: OpenPower: Some multipaths temporarily have only a single path Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: [Impact] * The SES driver causes a long delay in disk discovery when a large number of disks is present in the disk enclosure, which increases with the number of disks attached. * This delays the addition and visibility of the disk devices to userspace, which among other things causes multipath not to have multiple paths, actually, until the disk discovery eventually/finally finishes. * The fix significantly shortens the time taken by the SES driver to handle disk discovery, causing no extra delays, by removing a superfluous SCSI command sent to enclosure. [Test Case] * Load the module to access the enclosure and its disks; e.g., $ sudo modprobe mpt3sas * Notice the interval between the discovery of each disk; e.g., dmesg $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk * The interval should be in the same second or so range with the fix. $ dmesg -T | grep 'Attached SCSI disk' | tail -n2 [Wed Jun 7 13:11:59 2017] sd 18:0:176:0: [sdly] Attached SCSI disk [Wed Jun 7 13:11:59 2017] sd 18:0:175:0: [sdlx] Attached SCSI disk [Regression Potential] * The power status of the disks in the enclosure is no longer checked during probe time. However, the patch demonstrates that initial value was never used in any way. So, little regression potential. * Nonetheless, users of SES enclosures which verify the power status of disks in the enclosure might _theoretically_ see a problem, iff the fix has a problem (which has not been found yet). [Other Info] * None at this time. Problem Description: This week, I went ahead and scaled up my test configuration to max configuration 2x5U84_Enclosures,_MaxCfg_168HDDs. This time, it hit a different issue. The issue is that some multipaths only have a single path and no redundancy. Others have multiple paths and redundancy. Checkpoint #1: == - system reboot around 2pm (14:00) Checkpoint # 2: === - It took several minutes for first disk to be detected. root@smb1p1:~# multipath -ll|grep dm |wc -l 103 root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' | grep 'Attached SCSI disk' | tail [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk [Thu Jun 1 14:18:40 2017] sd 17:0:102:0: [sdct] Attached SCSI disk [Thu Jun 1 14:18:44 2017] sd 17:0:103:0: [sdcu] Attached SCSI disk [Thu Jun 1 14:18:54 2017] sd 17:0:105:0: [sdcv] Attached SCSI disk [Thu Jun 1 14:18:59 2017] sd 17:0:106:0: [sdcw] Attached SCSI disk [Thu Jun 1 14:19:04 2017] sd 17:0:107:0: [sdcx] Attached SCSI disk [Thu Jun 1 14:19:09 2017] sd 17:0:108:0: [sdcy] Attached SCSI disk [Thu Jun 1 14:19:14 2017] sd 17:0:109:0: [sdcz] Attached SCSI disk [Thu Jun 1 14:19:19 2017] sd 17:0:110:0: [sdda] Attached SCSI disk root@smb1p1:~# ... root@smb1p1:~# multipath -ll|grep dm |wc -l 142 root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' | grep 'Attached SCSI disk' | tail [Thu Jun 1 14:21:54 2017] sd 17:0:141:0: [sdee] Attached SCSI disk [Thu Jun 1 14:21:58 2017] sd 17:0:142:0: [sdef] Attached SCSI disk [Thu Jun 1 14:22:04 2017] sd 17:0:143:0: [sdeg] Attached SCSI disk [Thu Jun 1 14:22:08 2017] sd 17:0:144:0: [sdeh] Attached SCSI disk [Thu Jun 1 14:22:14 2017] sd 17:0:145:0: [sdei] Attached SCSI disk [Thu Jun 1 14:22:18 2017] sd 17:0:146:0: [sdej] Attached SCSI disk [Thu Jun 1 14:22:24 2017] sd 17:0:147:0: [sdek] Attached SCSI disk [Thu Jun 1 14:22:29 2017] sd 17:0:148:0: [sdel] Attached SCSI disk [Thu Jun 1 14:22:34 2017] sd 17:0:149:0: [sdem] Attached SCSI disk [Thu Jun 1 14:22:39 2017] sd 17:0:150:0: [sden] Attached SCSI disk root@smb1p1:~# ... - After 43 minutes, multipath -ll command shows some paths with only single path and no redundancy and some path with multiple paths and redundancy. root@smb1p1:~# date Thu Jun 1 14:43:00 CDT 2017 root@smb1p1:~# multipath -ll | grep -c 'sd[a-z]\+' 252 root@smb1p1:~# ... - After 47 minutes, multipath -ll command still shows some paths with only single path and no redundancy. root@smb1p1:~# multipath -ll | grep -c
[Kernel-packages] [Bug 1701019] Re: linux: 4.8.0-59.64 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: 1701020 -- swm properties -- boot-testing-requested: true phase: Promoted to security proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Released + kernel-stable-phase-changed:Monday, 17. July 2017 13:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: 1701020 -- swm properties -- boot-testing-requested: true - phase: Promoted to security + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Released - kernel-stable-phase-changed:Monday, 17. July 2017 13:33 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701019 Title: linux: 4.8.0-59.64 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: 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: derivatives: 1701020 -- swm properties -- boot-testing-requested: true phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Unfortnately some of my machines with 4.4.0-83 are still freezing up when they do a hyper-v backup. I will attach the syslog. ** Attachment added: "Server1 freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679898/+attachment/4916176/+files/Server1.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/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 (20150
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
Second server log ** Attachment added: "Server2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679898/+attachment/4916177/+files/Server2.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/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
[Kernel-packages] [Bug 1704435] Re: [Xenial] nvme: Quirks for PM1725 controllers
** Changed in: linux (Ubuntu Artful) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704435 Title: [Xenial] nvme: Quirks for PM1725 controllers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Fix Committed Bug description: == SRU Xenial == Pick up the following device quirk to resolve a hardware/firmware bug affectung some NVMe drives that use the PM1725 controller. Under adverse circumstances the bug can result in data corruption and loss. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d554b5e1ca64d23e4f839e6531490fee8479fbaf nvme: Quirks for PM1725 controllers PM1725 controllers have a couple of quirks that need to be handled in the driver: - I/O queue depth must be limited to 64 entries on controllers that do not report MQES. - The host interface registers go offline briefly while resetting the chip. Thus a delay is needed before checking whether the controller is ready. Note that the admin queue depth is also limited to 64 on older versions of this board. Since our NVME_AQ_DEPTH is now 32 that is no longer an issue. Signed-off-by: Martin K. Petersen Signed-off-by: Sagi Grimberg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704102] Re: bonding: stack dump when unregistering a netdev
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704102
Title:
bonding: stack dump when unregistering a netdev
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
In Progress
Status in linux source package in Zesty:
In Progress
Status in linux source package in Artful:
Fix Committed
Bug description:
Here is the reproducer:
ip netns add foo
ip -n foo link add dummy1 type dummy
ip -n foo link add dummy2 type dummy
modprobe bonding
ip -n foo link add bond1 type bond
ip -n foo link set dev bond1 down
ip -n foo addr add 10.10.10.1/24 dev bond1
ip -n foo link set dev bond1 up
ip -n foo link set dummy1 master bond1
ip -n foo link set dummy2 master bond1
ip -n foo link set bond1 mtu 1540
# Move slaves to init_net
ip -n foo link set dummy1 netns 1
ip -n foo link set dummy2 netns 1
# idev are still in netns foo for dummy interfaces:
ip netns exec foo ls /proc/sys/net/ipv4/conf/
ip netns exec foo ls /proc/net/dev_snmp6/
ip netns del foo
dmesg
The bug has been fixed upstream by this patch:
f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when
unregistering slave")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/bonding?id=f51048c3e07b
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704102/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693673 Title: Ubuntu 16.04 IOB Error when the Mustang board rebooted Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 3.07.09, the following warning messages are displayed: [ 38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction error [ 38.199164] xgene-edac 7880.edac: IOB BA write response error [ 38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. (0x) [ 38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722 This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 26 12:21 seq crw-rw 1 root audio 116, 33 May 26 12:21 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.6 Architecture: arm64 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=UUID=f8faea1d-17bf-4c48-9b44-ca04875978b9 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AppliedMicro X-Gene Mustang Board Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-53-generic N/A linux-backports-modules-4.8.0-53-generic N/A linux-firmware1.157.10 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-53-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: Feb 28 2017 dmi.bios.vendor: AppliedMicro dmi.bios.version: 3.07.09 dmi.board.asset.tag: Not Specified dmi.board.name: X-Gene Mustang Board dmi.board.vendor: AppliedMicro dmi.board.version: 1.0 dmi.chassis.asset.tag: Not Specified dmi.chassis.type: 23 dmi.chassis.vendor: AppliedMicro dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0: dmi.product.name: X-Gene Mustang Board dmi.product.version: 1.0 dmi.sys.vendor: AppliedMicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260
Changing to affect linux since the fix is in the driver, not in the firmware. I note patches have been submitted but not applied yet (and there's a response about v2 patches that I haven't found). Have you tested the patches yourself to confirm they fix your problem? ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) ** 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/1682744 Title: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260 Status in Ubuntu: Unknown Status in linux package in Ubuntu: Triaged Bug description: Only happens when connecting to 5GHz network, 2.5 GHz work fine. Network controller: Intel Corporation Wireless 7260 (rev 6b) iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode iwlmvm апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4289] device (wlan0): Activation: starting connection 'NewHibernia5' (104460fe-9e5b-4a8c-8735-cfe48dec488e) апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4290] audit: op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" name="NewHibernia5" pid=7054 uid=1000 result="success" апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4291] device (wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4293] manager: NetworkManager state is now CONNECTING апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4339] device (wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent) апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4381] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4383] device (wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but secrets are required. апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4384] device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4433] device (wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4438] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4450] device (wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets exist. No new secrets needed. апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4451] Config: added 'ssid' value 'NewHibernia5' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4451] Config: added 'scan_ssid' value '1' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'key_mgmt' value 'WPA-PSK' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'auth_alg' value 'OPEN' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'psk' value '' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4654] sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1 апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz) апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values: апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_HW_IF_CONFIG_REG: 0X40489204 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT_COALESCING: 0X8000ff40 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT_MASK: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_FH_INT_STATUS: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GPIO_IN: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_RESET: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GP_CNTRL: 0X080403cd апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_HW_REV: 0X0144 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_EEPROM_REG: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_EEPROM_GP: 0X8000
[Kernel-packages] [Bug 1689360] Re: TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly calculating base_command_size
** Changed in: ubuntu-power-systems
Status: New => 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/1689360
Title:
TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly
calculating base_command_size
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
---Problem Description---
If there has BIDI data, its first iov[] will overwrite the last
iov[] for se_cmd->t_data_sg.
---uname output---
Latest Yakkety master branch
Machine Type = P8
---Steps to Reproduce---
Just have a system do workload using tcmu.
Stack trace output:
I have seen this in my environment:
(gdb) print *((tcmulib_cmd->iovec)+0)
$7 = {iov_base = 0x3fff7c3d, iov_len = 8192}
(gdb) print *((tcmulib_cmd->iovec)+1)
$3 = {iov_base = 0x3fff7c3da000, iov_len = 4096}
(gdb) print *((tcmulib_cmd->iovec)+2)
$4 = {iov_base = 0x3fff7c3dc000, iov_len = 16384}
(gdb) print *((tcmulib_cmd->iovec)+3)
$5 = {iov_base = 0x3fff7c3f7000, iov_len = 12288}
(gdb) print *((tcmulib_cmd->iovec)+4)
$6 = {iov_base = 0x1306e853c0028, iov_len = 128} <--- bad pointer and length
cmu: Fix wrongly calculating of the base_command_size
https://patchwork.kernel.org/patch/9687657/
tcmu: Fix possible overwrite of t_data_sg's last iov[]
https://patchwork.kernel.org/patch/9687565/
tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI
case
https://patchwork.kernel.org/patch/9655423/
This patch should also be a part of these fixes. WITH BIDI op fixes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689360/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704435] Re: [Xenial] nvme: Quirks for PM1725 controllers
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Zesty) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704435 Title: [Xenial] nvme: Quirks for PM1725 controllers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: == SRU Xenial == Pick up the following device quirk to resolve a hardware/firmware bug affectung some NVMe drives that use the PM1725 controller. Under adverse circumstances the bug can result in data corruption and loss. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d554b5e1ca64d23e4f839e6531490fee8479fbaf nvme: Quirks for PM1725 controllers PM1725 controllers have a couple of quirks that need to be handled in the driver: - I/O queue depth must be limited to 64 entries on controllers that do not report MQES. - The host interface registers go offline briefly while resetting the chip. Thus a delay is needed before checking whether the controller is ready. Note that the admin queue depth is also limited to 64 on older versions of this board. Since our NVME_AQ_DEPTH is now 32 that is no longer an issue. Signed-off-by: Martin K. Petersen Signed-off-by: Sagi Grimberg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1587714] Re: MacBookPro11, 4 fails to poweroff or suspend
FYI, it looks like a slightly different patch has been accepted into the mainline 4.13 kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/x86/pci/fixup.c?h=v4.13-rc1&id=13cfc732160f7bc7e596128ce34cda361c556966 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1587714 Title: MacBookPro11,4 fails to poweroff or suspend Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Since the release of the 2015 MacBookPro11,4 (15" retina), it has been unable to suspend or poweroff on linux. Recently, https://bugzilla.kernel.org/show_bug.cgi?id=103211 has received a patch that works to fix these issues. The patch is in comment #172, and is also attached to this bugreport, and reported to work very well by users of other distributions. In addition, I can confirm that building the latest xenial 4.4.0-22-generic kernel with this patch applied fixes the issue. Can this be added to the official xenial kernel? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1587714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
