[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
Thanks Mike for the check. Given the results even better that we decoupled this from last SRU. The ppa you tested had all patches that were identified by IBM backported. @lagarcia: - do you think there are more than the 5 you identified? - Given the report that the 2.6.1 from yakkety works there must be something between 2.5 to 2.6.1 that we miss not from 2.7 as the identified patches so far were. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Incomplete Bug description: [Impact] * Some newer Power8 derivates fail to work correctly e.g. Power S822LC (8335-GTB) * This is a toleration change (no exploitation) for those HW releases following the SRU policy of "For Long Term Support releases we regularly want to enable new hardware. Such changes are appropriate provided that we can ensure not to affect upgrades on existing hardware." * Without the Fix that hardware won't run Xenial guests under current Xenials Qemu version * The fix lets processors that support it run in PowerISA 2.07 compatibility mode (plus a few no-op changes as backport dependencies) [Test Case] * Run a Xenial Guest in KVM on one of the specific HW revisions being affected. [Regression Potential] * Changes are PPC only, so fallout should be contained to that * Patches were created by IBM and in Upstream qemu since 2.7 * The effective change is rather small, only allow different compat level on this other cpu class * There are a few refactoring changes needed to get the backport done, while they should be a no-op that is a regression potential (still limited to ppc64el) [Other Info] * Needed for certifying this Hardware for Ubuntu Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el 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: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
@Marciej here are the results for GA-X370-Gaming-5 board (with 1800X processor). Please note that it's the result on 4.10.1 with PINCTRL_AMD removed. ** Attachment added: "devices.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4837491/+files/devices.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/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3
And lspci ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+attachment/4837492/+files/lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
I tested on an KBL laptop and it did have the issue. Backport a patch can make the machine idle to C10. commit 3ce093d4de753d6c92cc09366e29d0618a62f542 Author: Len Brown Date: Wed Apr 6 17:00:59 2016 -0400 intel_idle: Add KBL support KBL is similar to SKL Signed-off-by: Len Brown Signed-off-by: Rafael J. Wysocki Please test the Xenial kernel: http://people.canonical.com/~khfeng/lp1672439/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: My processor does not appear to be utilizing and idling states deeper than C3. 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 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 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: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1647936] Raspberry Pi 3: a small rainbow square on the top right of screen
> Wiadomość napisana przez Ying-Chun Liu w dniu > 13.03.2017, o godz. 11:02: > > I think I'm making wrong assumption? It seems to me that refresh gadget snaps > won't upgrade the files in the system. That is correct. This is not yet supported by snapd. > Upgrading kernel snap does change the kernel/uboot.env stuff. But not for > gadgets right? Seems we need to regenerate an edge image for testing this? > > -- > You received this bug notification because you are a member of Snappy > Developers, which is subscribed to Snappy. > Matching subscriptions: xxx-bugs-on-snapd > https://bugs.launchpad.net/bugs/1647936 > > Title: > Raspberry Pi 3: a small rainbow square on the top right of screen > > To manage notifications about this bug go to: > https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670696] Re: Typo in error msg when no crashkernel memory reservation is set
** Changed in: makedumpfile (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1670696 Title: Typo in error msg when no crashkernel memory reservation is set Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Zesty: In Progress Status in makedumpfile package in Debian: New Bug description: [Impact] * There is a typo in ERRMSG of function show_mem_usage affecting Xenial/Zesty, Debian and makedumpfile upstream. This should be : "show_mem_usage: No memory is reserved for crashkernel!" instead of : "show_mem_usage: No memory is reserved for crashkenrel!" The typo is located here in src code : # filename : makedumpfile.c - int show_mem_usage(void) { uint64_t vmcoreinfo_addr, vmcoreinfo_len; struct cycle cycle = {0}; if (!is_crashkernel_mem_reserved()) { ==> ERRMSG("No memory is reserved for crashkenrel!\n"); return FALSE; } - [Test Case] * Take a system with no crashkernel memory reservation set * run command : makedumpfile --mem-usage /proc/kcore * Error message : show_mem_usage: No memory is reserved for crashkenrel! [Regression Potential] * No regression, it is a trivial change with no behavioural change. [Other Info] * Upstream: Patch has been submitted upstream (ML :ke...@lists.infradead.org) - AFAIK, there is no upstream bug database, so no URL available, ML only. - Patch will be merge in upstream version 1.6.2 # See comment #4 * Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1670696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
Hi, please download the attach file, then $ sudo cp 71-pointingstick-precision.hwdb /etc/udev/hwdb.d/ $ sudo systemd-hwdb update $ sudo udevadm trigger And check if this issue is solved or not. ** Attachment added: "71-pointingstick-precision.hwdb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+attachment/4837507/+files/71-pointingstick-precision.hwdb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670358] Re: Bcmwl-kernel-source not supporting wifi card
** Description changed: - No version of the driver would work with a Broadcom Limited BCM43142 - 802.11b/g/n [14e4:4365] (rev 01) netcard on Ubuntu 16.10 LTS. + No version of the driver would work with a Broadcom Limited BCM43142 802.11b/g/n [14e4:4365] (rev 01) netcard on Ubuntu 16.10 LTS. + Other information: actually the installation process won't disable Secure Boot so is the wrong working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 6 14:32:10 2017 InstallationDate: Installed on 2017-03-05 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1670358 Title: Bcmwl-kernel-source not supporting wifi card Status in bcmwl package in Ubuntu: New Bug description: No version of the driver would work with a Broadcom Limited BCM43142 802.11b/g/n [14e4:4365] (rev 01) netcard on Ubuntu 16.10 LTS. Other information: actually the installation process won't disable Secure Boot so is the wrong working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 6 14:32:10 2017 InstallationDate: Installed on 2017-03-05 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1670358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
I can confirm this issue and the workaround at comment 18. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop 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 Bug description: booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic: Grub works, entering full disk encryption passphrase works, but when the desktop comes up mouse and keyboard (via USB) are dead and the desktop also. booting the PC without the stick attached works fine, but as soon as it is attached (see syslog) mouse, keyboard and the desktop itself are dead (checked by opening terminal and "watch date" - freezes, with desktop still visible). problem is resolved by booting former kernel 4.4.0-59-generic. syslog upon attaching stick --- Feb 21 07:17:02 orin kernel: [ 188.998338] usb 8-2: new high-speed USB device number 2 using xhci_hcd Feb 21 07:17:02 orin kernel: [ 189.129674] usb 8-2: New USB device found, idVendor=0bda, idProduct=8178 Feb 21 07:17:02 orin kernel: [ 189.129682] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 21 07:17:02 orin kernel: [ 189.129687] usb 8-2: Product: USB WLAN Feb 21 07:17:02 orin kernel: [ 189.129691] usb 8-2: Manufacturer: Realtek Feb 21 07:17:02 orin kernel: [ 189.129694] usb 8-2: SerialNumber: 00e04c01 Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: "/sys/devices/pci:00/:00:10.1/usb8/8-2" Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager... Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 'org.freedesktop.UDisks2' Feb 21 07:17:02 orin systemd[1]: Started Disk Manager. Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 on the system message bus Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive Feb 21 07:17:03 orin kernel: [ 190.200286] cfg80211: World regulatory domain updated: Feb 21 07:17:03 orin kernel: [ 190.200294] cfg80211: DFS Master region: unset Feb 21 07:17:03 orin kernel: [ 190.200297] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 21 07:17:03 orin kernel: [ 190.200303] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200308] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200312] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200317] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200321] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 21 07:17:03 orin kernel: [ 190.200325] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Feb 21 07:17:03 orin kernel: [ 190.200329] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200333] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.223081] rtl8192cu: Chip version 0x11 Feb 21 07:17:03 orin kernel: [ 190.625235] rtl8192cu: MAC address: 14:cc:20:10:43:98 Feb 21 07:17:03 orin kernel: [ 190.625241] rtl8192cu: Board Type 0 Feb 21 07:17:03 orin kernel: [ 190.626355] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 Feb 21 07:17:03 orin kernel: [ 190.626408] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7698] (wlan0): using nl80211 for WiFi device control Feb 21 07:17:03 orin kernel: [ 190.636625] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' Feb 21 07:17:03 orin kernel: [ 190.637211] usbcore: registered new interface driver rtl8192cu Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status... Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7780] device (wlan0): driver supports Access Point (AP) mode Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7798] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4) Feb 21 07:17:03 orin kernel: [ 190.648972] usbcore: registered new interface driver rtl8xxxu Feb 21 07:
[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain
** Tags removed: solved-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/1664602 Title: Using an NVMe drive causes huge power drain Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Won't Fix Bug description: PCIe NVMe drives are very common in new laptops. The Zesty's kernels (including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous power state transitions). A patch does exist : http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html https://github.com/damige/linux-nvme It seems that we cannot expect this before kernel 4.11. Additionally my laptop CPU does never go under PC3 power saving state, powertop says. I don't know if it's related. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ft 1900 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10 InstallationDate: Installed on 2016-12-12 (63 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) Lsusb: 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: Dell Inc. Precision 7510 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 RelatedPackageVersions: linux-restricted-modules-4.10.0-8-generic N/A linux-backports-modules-4.10.0-8-generic N/A linux-firmware1.163 Tags: zesty Uname: Linux 4.10.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.5 dmi.board.name: 0YH43H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672518] [NEW] Suspend -> Freeze
You have been subscribed to a public bug: Thinkpad SL510 freezes after SUSPEND Halfmoon-shaped LED is flashing, screen is black as should be, but nothing wakes the System up. Freeze or is system waiting for imput I cant deliver eg missing button? Google: Display driver at fault?! Keep up the good work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 13 20:52:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] InstallationDate: Installed on 2017-03-06 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2847BTG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET83WW (1.41 ) dmi.board.name: 2847BTG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6JET83WW(1.41):bd09/21/2010:svnLENOVO:pn2847BTG:pvrThinkPadSL510:rvnLENOVO:rn2847BTG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2847BTG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Mar 13 20:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze suspend-resume ubuntu xenial -- Suspend -> Freeze https://bugs.launchpad.net/bugs/1672518 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672518] Re: Suspend -> Freeze
sounds like it's old hw, so could be a hardware failure ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672518 Title: Suspend -> Freeze Status in linux package in Ubuntu: Confirmed Bug description: Thinkpad SL510 freezes after SUSPEND Halfmoon-shaped LED is flashing, screen is black as should be, but nothing wakes the System up. Freeze or is system waiting for imput I cant deliver eg missing button? Google: Display driver at fault?! Keep up the good work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 13 20:52:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] InstallationDate: Installed on 2017-03-06 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2847BTG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET83WW (1.41 ) dmi.board.name: 2847BTG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6JET83WW(1.41):bd09/21/2010:svnLENOVO:pn2847BTG:pvrThinkPadSL510:rvnLENOVO:rn2847BTG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2847BTG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Mar 13 20:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672518] 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/1672518 Title: Suspend -> Freeze Status in linux package in Ubuntu: Confirmed Bug description: Thinkpad SL510 freezes after SUSPEND Halfmoon-shaped LED is flashing, screen is black as should be, but nothing wakes the System up. Freeze or is system waiting for imput I cant deliver eg missing button? Google: Display driver at fault?! Keep up the good work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 13 20:52:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] InstallationDate: Installed on 2017-03-06 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2847BTG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET83WW (1.41 ) dmi.board.name: 2847BTG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6JET83WW(1.41):bd09/21/2010:svnLENOVO:pn2847BTG:pvrThinkPadSL510:rvnLENOVO:rn2847BTG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2847BTG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Mar 13 20:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662003] Re: /sbin/crda failed with exit code 249
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1662003 Title: /sbin/crda failed with exit code 249 Status in crda package in Ubuntu: Confirmed Bug description: /var/log/syslog tells : --- kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) systemd-udevd: Process '/sbin/crda' failed with exit code 249. kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] --- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 5 20:18:42 2017 InstallationDate: Installed on 2017-02-01 (3 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: crda UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1669153] Re: Add Use-After-Free Patch for Ubuntu16.10 - EEH on BELL3 adapter fails to recover (serial/tty)
** Changed in: linux (Ubuntu Xenial) 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/1669153 Title: Add Use-After-Free Patch for Ubuntu16.10 - EEH on BELL3 adapter fails to recover (serial/tty) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: On LP1646857, patch [1] was applied (Zesty, Yakkety, Xenial). However, this patch [2] fixes a use-after-free problem on it, and it's not yet applied (Yakkety, Xenial), only applied on Zesty so far. Please apply patch [2] for Yakkety and Xenial HWE. Thank you. [1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f209fa03fc9d131b3108c2e4936181eabab87416 [2] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c130b666a9a711f985a0a44b58699ebe14bb7245 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668042] Re: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1668042 Title: [Xenial - 16.04 ]Bonding driver - stack corruption when trying to copy 20 bytes to a sockaddr Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Bug description: In Ubuntu Xenial with kernel 4.4.0-65, we get kernel Panic after scenario [1]. patch [2] should fix the issue When using an IPoIB bond currently only active-backup mode is a valid use case and this commit strengthens it. Since commit 2ab82852a270 ("net/bonding: Enable bonding to enslave netdevices not supporting set_mac_address()") was introduced till 4.7-rc1, IPoIB didn't support the set_mac_address ndo, and hence the fail over mac policy always applied to IPoIB bonds. With the introduction of commit 492a7e67ff83 ("IB/IPoIB: Allow setting the device address"), that doesn't hold and practically IPoIB bonds are broken as of that. To fix it, lets go to fail over mac if the device doesn't support the ndo OR this is IPoIB device. As a by-product, this commit also prevents a stack corruption which occurred when trying to copy 20 bytes (IPoIB) device address to a sockaddr struct that has only 16 bytes of storage. [1] Get panic after create bond with down/updelay and restart NIC driver Configure bond with down/updelay cat /etc/network/interfaces auto bond1 iface bond1 inet static address 31.136.42.17 netmask 255.255.0.0 bond-slaves ib0 ib1 bond-miimon 100 bond-updelay 5000 bond-mode active-backup bond-primary ib1 bond-downdelay 5000 auto ib0 iface ib0 inet manual bond-master bond1 auto ib1 iface ib1 inet manual bond-master bond1 modprobe -r [2] 1533e77315220dc1d5ec3bd6d9fe32e2aa0a74c0 net/bonding: Enforce active-backup policy for IPoIB bonds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1669015] Re: Xenial update to v4.4.51 stable release
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1669015 Title: Xenial update to v4.4.51 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.4.51 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.4.51 stable release shall be applied: vfs: fix uninitialized flags in splice_to_pipe() siano: make it work again with CONFIG_VMAP_STACK fuse: fix use after free issue in fuse_dev_do_read() scsi: don't BUG_ON() empty DMA transfers Fix missing sanity check in /dev/sg Input: elan_i2c - add ELAN0605 to the ACPI table drm/radeon: Use mode h/vdisplay fields to hide out of bounds HW cursor drm/dp/mst: fix kernel oops when turning off secondary monitor futex: Move futex_init() to core_initcall ARM: 8658/1: uaccess: fix zeroing of 64-bit get_user() printk: use rcuidle console tracepoint NTB: ntb_transport: fix debugfs_remove_recursive ntb_transport: Pick an unused queue bcache: Make gc wakeup sane, remove set_task_state() mmc: core: fix multi-bit bus width without high-speed mode Linux 4.4.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667571] Re: linux-tools-common should Depends: lsb-release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1667571 Title: linux-tools-common should Depends: lsb-release 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 Committed Status in linux source package in Zesty: Fix Released Bug description: default desc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1669016] Re: Xenial update to v4.4.52 stable release
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1669016 Title: Xenial update to v4.4.52 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.4.52 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.4.52 stable release shall be applied: net/llc: avoid BUG_ON() in skb_orphan() packet: fix races in fanout_add() packet: Do not call fanout_release from atomic contexts irda: Fix lockdep annotations in hashbin_delete(). ip: fix IP_CHECKSUM handling net: socket: fix recvmmsg not returning error from sock_error tty: serial: msm: Fix module autoload USB: serial: mos7840: fix another NULL-deref at open USB: serial: cp210x: add new IDs for GE Bx50v3 boards USB: serial: ftdi_sio: fix modem-status error handling USB: serial: ftdi_sio: fix extreme low-latency setting USB: serial: ftdi_sio: fix line-status over-reporting USB: serial: spcp8x5: fix modem-status handling USB: serial: opticon: fix CTS retrieval at open USB: serial: ark3116: fix register-accessor error handling x86/platform/goldfish: Prevent unconditional loading goldfish: Sanitize the broken interrupt handler block: fix double-free in the failure path of cgwb_bdi_init() rtlwifi: rtl_usb: Fix for URB leaking when doing ifconfig up/down Revert "usb: chipidea: imx: enable CI_HDRC_SET_NON_ZERO_TTHA" kvm: vmx: ensure VMCS is current while enabling PML Linux 4.4.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667239] Re: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs 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 Committed Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp# dpkg -l | grep afu ii afuimage3.0-1970-3042652 all no description given cat /opt/ibm/capikv/version.txt 1970-3042652 /opt/ibm/capikv/afu/cxl_afu_dump /dev/cxl/afu0.0m -v AFU Version = 160525N1 NVMe0 Version = BTV73011 NVMe0 NEXT= BTV
[Kernel-packages] [Bug 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1667527 Title: [Hyper-V] pci-hyperv: Use device serial number as PCI domain Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: This allows PCI domain numbers starts with 1, and also unique on the same VM. So names, such as VF NIC names, that include domain number as part of the name, can be shorter than that based on part of bus UUID previously. The new names will also stay same for VMs created with copied VHD and same number of devices. This is needed for SR-IOV in Azure. This is Bjorn's tree for 4.11 here: https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci /host-hv&id=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666324] Re: Xenial update to v4.4.50 stable release
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => 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/1666324 Title: Xenial update to v4.4.50 stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.4.50 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.4.50 stable release shall be applied: can: Fix kernel panic at security_sock_rcv_skb ipv6: fix ip6_tnl_parse_tlv_enc_lim() ipv6: pointer math error in ip6_tnl_parse_tlv_enc_lim() tcp: fix 0 divide in __tcp_select_window() net: use a work queue to defer net_disable_timestamp() work ipv4: keep skb->dst around in presence of IP options netlabel: out of bound access in cipso_v4_validate() ip6_gre: fix ip6gre_err() invalid reads ipv6: tcp: add a missing tcp_v6_restore_cb() tcp: avoid infinite loop in tcp_splice_read() tun: read vnet_hdr_sz once macvtap: read vnet_hdr_size once mlx4: Invoke softirqs after napi_reschedule sctp: avoid BUG_ON on sctp_wait_for_sndbuf sit: fix a double free on error path net: introduce device min_header_len packet: round up linear to header len ping: fix a null pointer dereference l2tp: do not use udp_ioctl() Linux 4.4.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662003] Re: /sbin/crda failed with exit code 249
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: crda (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1662003 Title: /sbin/crda failed with exit code 249 Status in crda package in Ubuntu: Confirmed Bug description: /var/log/syslog tells : --- kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) systemd-udevd: Process '/sbin/crda' failed with exit code 249. kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] --- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 5 20:18:42 2017 InstallationDate: Installed on 2017-02-01 (3 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: crda UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662003] Re: /sbin/crda failed with exit code 249
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1662003 Title: /sbin/crda failed with exit code 249 Status in crda package in Ubuntu: Confirmed Bug description: /var/log/syslog tells : --- kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) systemd-udevd: Process '/sbin/crda' failed with exit code 249. kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] --- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 5 20:18:42 2017 InstallationDate: Installed on 2017-02-01 (3 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: crda UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1623750] Re: Request to backport cxlflash patches to Xenial SRU stream
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1623750 Title: Request to backport cxlflash patches to Xenial SRU stream 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 Committed Bug description: Problem Description == There are a few patches in cxlflash that are in the process of getting upstream. We would like to have them pulled into Xenial SRU. Patches are, cxlflash: Scan host only after the port is ready for I/O cxlflash: Remove the device cleanly in the system shutdown path cxlflash: Fix to avoid EEH and host reset collisions cxlflash: Improve EEH recovery time These patches are applied to mkp's 4.9/scsi-queue. Commit ids from that queue, 05dab43230fdc0d14ca885b473a2740fe017ecb1 scsi: cxlflash: Improve EEH recovery time 1d3324c382b1a617eb567e3650dcb51f22dfec9a scsi: cxlflash: Fix to avoid EEH and host reset collisions babf985d1e1b0677cb264acd01319d2b9c8f4327 scsi: cxlflash: Remove the device cleanly in the system shutdown path bbbfae962b7c221237c0f92547ee0c83f7204747 scsi: cxlflash: Scan host only after the port is ready for I/O I tried applying them on local copy of xenial/master-next tree and it applied cleanly. Please let me know if you want me to attach the patches instead. Please include the above commits to Xenial SRU. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: In Progress 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 Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671176] Re: linux: 4.8.0-42.45 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671176 Title: linux: 4.8.0-42.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-42.45 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-sru-workflow/+bug/1671176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667571] Re: linux-tools-common should Depends: lsb-release
** Changed in: linux (Ubuntu Yakkety) 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/1667571 Title: linux-tools-common should Depends: lsb-release 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 Committed Status in linux source package in Zesty: Fix Released Bug description: default desc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667239] Re: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs
** Changed in: linux (Ubuntu Yakkety) 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/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs 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 Committed Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp# dpkg -l | grep afu ii afuimage3.0-1970-3042652 all no description given cat /opt/ibm/capikv/version.txt 1970-3042652 /opt/ibm/capikv/afu/cxl_afu_dump /dev/cxl/afu0.0m -v AFU Version = 160525N1 NVMe0 Version = BTV73011 NVMe0 NEXT= BT
[Kernel-packages] [Bug 1669153] Re: Add Use-After-Free Patch for Ubuntu16.10 - EEH on BELL3 adapter fails to recover (serial/tty)
** Changed in: linux (Ubuntu Yakkety) 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/1669153 Title: Add Use-After-Free Patch for Ubuntu16.10 - EEH on BELL3 adapter fails to recover (serial/tty) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: On LP1646857, patch [1] was applied (Zesty, Yakkety, Xenial). However, this patch [2] fixes a use-after-free problem on it, and it's not yet applied (Yakkety, Xenial), only applied on Zesty so far. Please apply patch [2] for Yakkety and Xenial HWE. Thank you. [1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f209fa03fc9d131b3108c2e4936181eabab87416 [2] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c130b666a9a711f985a0a44b58699ebe14bb7245 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1623750] Re: Request to backport cxlflash patches to Xenial SRU stream
** Changed in: linux (Ubuntu Yakkety) 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/1623750 Title: Request to backport cxlflash patches to Xenial SRU stream 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 Committed Bug description: Problem Description == There are a few patches in cxlflash that are in the process of getting upstream. We would like to have them pulled into Xenial SRU. Patches are, cxlflash: Scan host only after the port is ready for I/O cxlflash: Remove the device cleanly in the system shutdown path cxlflash: Fix to avoid EEH and host reset collisions cxlflash: Improve EEH recovery time These patches are applied to mkp's 4.9/scsi-queue. Commit ids from that queue, 05dab43230fdc0d14ca885b473a2740fe017ecb1 scsi: cxlflash: Improve EEH recovery time 1d3324c382b1a617eb567e3650dcb51f22dfec9a scsi: cxlflash: Fix to avoid EEH and host reset collisions babf985d1e1b0677cb264acd01319d2b9c8f4327 scsi: cxlflash: Remove the device cleanly in the system shutdown path bbbfae962b7c221237c0f92547ee0c83f7204747 scsi: cxlflash: Scan host only after the port is ready for I/O I tried applying them on local copy of xenial/master-next tree and it applied cleanly. Please let me know if you want me to attach the patches instead. Please include the above commits to Xenial SRU. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (Ubuntu Yakkety) 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/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: In Progress 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 Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667239] htxerr
Default Comment by Bridge ** Attachment added: "htxerr" https://bugs.launchpad.net/bugs/1667239/+attachment/4837570/+files/htxerr -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs 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 Committed Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp# dpkg -l | grep afu ii afuimage3.0-1970-3042652 all no description given cat /opt/ibm/capikv/version.txt 1970-3042652 /opt/ibm/capikv/afu/cxl_afu_dump /dev/cxl/afu0.0m -v AFU Version = 160525N
[Kernel-packages] [Bug 1667239] dmesg, backtrace - surelock02p03
Default Comment by Bridge ** Attachment added: "dmesg, backtrace - surelock02p03" https://bugs.launchpad.net/bugs/1667239/+attachment/4837573/+files/log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs 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 Committed Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp# dpkg -l | grep afu ii afuimage3.0-1970-3042652 all no description given cat /opt/ibm/capikv/version.txt 1970-3042652 /opt/ibm/capikv/afu/cxl_afu_dump /dev/cxl/afu0.0m -v AF
[Kernel-packages] [Bug 1667239] kern.log
Default Comment by Bridge ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1667239/+attachment/4837571/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs 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 Committed Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp# dpkg -l | grep afu ii afuimage3.0-1970-3042652 all no description given cat /opt/ibm/capikv/version.txt 1970-3042652 /opt/ibm/capikv/afu/cxl_afu_dump /dev/cxl/afu0.0m -v AFU Version = 160
[Kernel-packages] [Bug 1667239] dmesg, backtrace - capiredfsp
Default Comment by Bridge ** Attachment added: "dmesg, backtrace - capiredfsp" https://bugs.launchpad.net/bugs/1667239/+attachment/4837572/+files/dmesg_backtrace_capiredfsp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs 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 Committed Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp# dpkg -l | grep afu ii afuimage3.0-1970-3042652 all no description given cat /opt/ibm/capikv/version.txt 1970-3042652 /opt/ibm/capikv/afu/cxl_afu_dump /de
[Kernel-packages] [Bug 1667239] syslog
Default Comment by Bridge ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1667239/+attachment/4837569/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs 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 Committed Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp# dpkg -l | grep afu ii afuimage3.0-1970-3042652 all no description given cat /opt/ibm/capikv/version.txt 1970-3042652 /opt/ibm/capikv/afu/cxl_afu_dump /dev/cxl/afu0.0m -v AFU Version = 160525N
[Kernel-packages] [Bug 1672550] Re: i40e Intel X710 error during device probe prevents link set up and ip association
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672550 Title: i40e Intel X710 error during device probe prevents link set up and ip association Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: == Comment: #0 - Mauro Sergio Martins Rodrigues - 2017-02-22 06:48:42 == While investigating bug #145959 I got blocked in the reproduction process due to the follow issue during interface link bring up: [1.590591] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [1.590661] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [1.590669] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL which prevented me to bring the interface up and associate an ip to it. == Comment: #2 - Mauro Sergio Martins Rodrigues - 2017-02-22 07:26:36 == some missing Information kernel is Ubuntu's 4.4.0-62-generic. When testing with 4.8.0-36-generic (from xenial's proposed) device probe works fine, no similar message is seen. To obtain some more data on this I added some statements to see which TC MAP was applied in a healthy probe (note that the other functions, like function 1 works fine but those functions have no cable on them). root@yangtze-lp1:~/_maurosr/linux-4.4.0/drivers/net/ethernet/intel/i40e# dmesg [52448.914605] i40e 0045:01:00.3: i40e_ptp_stop: removed PHC on enP69p1s0f3 [52448.981801] i40e 0045:01:00.2: i40e_ptp_stop: removed PHC on enP69p1s0f2 [52449.069793] i40e 0045:01:00.1: i40e_ptp_stop: removed PHC on enP69p1s0f1 [52449.173834] i40e 0045:01:00.0: i40e_ptp_stop: removed PHC on enP69p1s0f0 [52449.264462] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.4.25-k [52449.264468] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [52449.264625] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [52449.286138] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.505657] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [52449.508977] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 [52449.531210] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [52449.531213] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [52449.531217] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL [52449.544642] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [52449.697424] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [52449.727043] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 0 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA [52449.727098] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass [52449.748667] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.976665] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 [52449.980685] i40e 0045:01:00.1: SAN MAC: 68:05:ca:2d:e9:0d [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 [52450.015610] i40e 0045:01:00.1 enP69p1s0f1: renamed from eth0 [52450.074479] i40e 0045:01:00.1: PCI-Express: Speed 8.0GT/s Width x8 [52450.080516] i40e 0045:01:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 128 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA Comparing function 0: [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 and function 1: [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 Then looking at 4.8: [ 123.425399] i40e: loading out-of-tree module taints kernel. [ 123.428958] i40e: module verification failed: signature and/or required key missing - tainting kernel [ 123.430690] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.6.11-k [ 123.430691] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [ 123.430918] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [ 123.450445] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [ 123.664088] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [ 123.667878] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [ 123.681915]
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
I can confirm that this version fixes the following issue : crash: invalid structure member offset: module_num_symtab FILE: kernel.c LINE: 3049 FUNCTION: module_init() using the latest linux-image-lts-xenial kernel ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1607894 Title: Unable to analyse vmcore/dump via crash due to bad kernel debug info build Status in crash package in Ubuntu: Fix Released Status in crash source package in Trusty: Fix Committed Bug description: [ Test case ] * trigger a kernel crash dump * use crash tool to analyse it * ... on ppc64el architecture == Comment: #0 - NAVEED A. UPPINANGADY SALIH - 2016-07-01 02:41:07 == ---Problem Description--- Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel with ddeb kernel debuginfo available in http://ddebs.ubuntu.com/pool/main/l/linux/ http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29 -generic-dbgsym_4.4.0-29.48_ppc64el.ddeb ---uname output--- 4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = model : 8247-22L machine : PowerNV 8247-22L ---Steps to Reproduce--- # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic /var/crash/201606300840/dump.201606300840 crash 7.0.3 ... This GDB was configured as "powerpc64le-unknown-linux-gnu"... crash: invalid kernel virtual address: 61c2555c09c17994 type: "possible" WARNING: cannot read cpu_possible_map crash: invalid kernel virtual address: 8a0f6ddee20c4116 type: "present" WARNING: cannot read cpu_present_map crash: invalid kernel virtual address: 5a09344e320a1886 type: "online" WARNING: cannot read cpu_online_map WARNING: cannot read linux_banner string crash: /usr/lib/debug/boot/vmlinux-4.4.0-29-generic and /var/crash/201606300840/dump.201606300840 do not match! Userspace rpm: linux-image-4.4.0-29-generic- dbgsym_4.4.0-29.48_ppc64el.ddeb == Comment: #5 - Naresh Bannoth - 2016-07-27 04:12:09 == The Latest kernel I am having is as follows root@ltcalpine-lp6:~# uname -a Linux ltcalpine-lp6 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:03:56 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ltcalpine-lp6:~# >>> the issue same as posted originally. ... This GDB was configured as "powerpc64le-unknown-linux-gnu"... crash: invalid kernel virtual address: 61c2555c09c17994 type: "possible" WARNING: cannot read cpu_possible_map crash: invalid kernel virtual address: 8a0f6ddee20c4116 type: "present" WARNING: cannot read cpu_present_map crash: invalid kernel virtual address: 5a09344e320a1886 type: "online" WARNING: cannot read cpu_online_map WARNING: cannot read linux_banner string crash: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic and /var/crash/201607270248/dump.201607270248 do not match! == Comment: #6 - Hari Krishna Bathini - 2016-07-28 11:49:31 == The kernel is compiled with gcc version 4.8.4 while the vmlinux pulled from http://ddebs.ubuntu.com/pool/main/l/linux/ is compiled with gcc version 5.3.1 which is the source of the issue. Resolved this by pulling the kernel debug symbols package from: deb http://ddebs.ubuntu.com/ -updates main which indeed has the vmlinux compiled with gcc version 4.8.4. But I got this error: crash: invalid structure member offset: module_num_symtab FILE: kernel.c LINE: 3049 FUNCTION: module_init() after the update owning to couple of missing patches listed below: commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61 Author: Dave Anderson Date: Wed Jan 20 09:56:36 2016 -0500 Fix for the changes made to the kernel module structure introduced by this kernel commit for Linux 4.5 and later kernels: commit 7523e4dc5057e157212b4741abd6256e03404cf1 module: use a structure to encapsulate layout. Without the patch, the crash session fails during initialization with the error message: "crash: invalid structure member offset: module_init_text_size". (seb...@linux.vnet.ibm.com) commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66 Author: Dave Anderson Date: Fri Feb 12 14:32:53 2016 -0500 Fix for the changes made to the kernel module structure introduced by this kernel commit for Linux 4.5 and later kernels: commit 8244062ef1e54502ef55f54cced659913f244c3e modules: fix longstanding /proc/kallsyms vs module insertion race. Without the patch, the crash session fails during initialization with the error message: "crash: invalid structure member offset: module_num_symtab". (ander...@redhat.com) Applying the above patches on top of crash tool version 7.0.3-3ubuntu4.4, was able
[Kernel-packages] [Bug 1672550] Re: i40e Intel X710 error during device probe prevents link set up and ip association
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672550 Title: i40e Intel X710 error during device probe prevents link set up and ip association Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: == Comment: #0 - Mauro Sergio Martins Rodrigues - 2017-02-22 06:48:42 == While investigating bug #145959 I got blocked in the reproduction process due to the follow issue during interface link bring up: [1.590591] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [1.590661] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [1.590669] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL which prevented me to bring the interface up and associate an ip to it. == Comment: #2 - Mauro Sergio Martins Rodrigues - 2017-02-22 07:26:36 == some missing Information kernel is Ubuntu's 4.4.0-62-generic. When testing with 4.8.0-36-generic (from xenial's proposed) device probe works fine, no similar message is seen. To obtain some more data on this I added some statements to see which TC MAP was applied in a healthy probe (note that the other functions, like function 1 works fine but those functions have no cable on them). root@yangtze-lp1:~/_maurosr/linux-4.4.0/drivers/net/ethernet/intel/i40e# dmesg [52448.914605] i40e 0045:01:00.3: i40e_ptp_stop: removed PHC on enP69p1s0f3 [52448.981801] i40e 0045:01:00.2: i40e_ptp_stop: removed PHC on enP69p1s0f2 [52449.069793] i40e 0045:01:00.1: i40e_ptp_stop: removed PHC on enP69p1s0f1 [52449.173834] i40e 0045:01:00.0: i40e_ptp_stop: removed PHC on enP69p1s0f0 [52449.264462] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.4.25-k [52449.264468] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [52449.264625] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [52449.286138] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.505657] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [52449.508977] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 [52449.531210] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [52449.531213] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [52449.531217] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL [52449.544642] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [52449.697424] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [52449.727043] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 0 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA [52449.727098] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass [52449.748667] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.976665] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 [52449.980685] i40e 0045:01:00.1: SAN MAC: 68:05:ca:2d:e9:0d [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 [52450.015610] i40e 0045:01:00.1 enP69p1s0f1: renamed from eth0 [52450.074479] i40e 0045:01:00.1: PCI-Express: Speed 8.0GT/s Width x8 [52450.080516] i40e 0045:01:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 128 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA Comparing function 0: [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 and function 1: [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 Then looking at 4.8: [ 123.425399] i40e: loading out-of-tree module taints kernel. [ 123.428958] i40e: module verification failed: signature and/or required key missing - tainting kernel [ 123.430690] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.6.11-k [ 123.430691] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [ 123.430918] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [ 123.450445] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [ 123.664088] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [ 123.667878] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [ 123.681915] Non-contiguous TC - Disabling DCB [ 123.690177] i40e 0045:01:00.0: DEBUG DATA vsi > 399, enabled_tc 1 [ 123.713262] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [ 123.864601] i40e 0045:01:00.0: Added LAN device PF0 bus=0x00 func=0x00 [ 123.864611] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Wid
[Kernel-packages] [Bug 1672550] Re: i40e Intel X710 error during device probe prevents link set up and ip association
https://lists.ubuntu.com/archives/kernel-team/2017-March/082977.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672550 Title: i40e Intel X710 error during device probe prevents link set up and ip association Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: == Comment: #0 - Mauro Sergio Martins Rodrigues - 2017-02-22 06:48:42 == While investigating bug #145959 I got blocked in the reproduction process due to the follow issue during interface link bring up: [1.590591] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [1.590661] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [1.590669] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL which prevented me to bring the interface up and associate an ip to it. == Comment: #2 - Mauro Sergio Martins Rodrigues - 2017-02-22 07:26:36 == some missing Information kernel is Ubuntu's 4.4.0-62-generic. When testing with 4.8.0-36-generic (from xenial's proposed) device probe works fine, no similar message is seen. To obtain some more data on this I added some statements to see which TC MAP was applied in a healthy probe (note that the other functions, like function 1 works fine but those functions have no cable on them). root@yangtze-lp1:~/_maurosr/linux-4.4.0/drivers/net/ethernet/intel/i40e# dmesg [52448.914605] i40e 0045:01:00.3: i40e_ptp_stop: removed PHC on enP69p1s0f3 [52448.981801] i40e 0045:01:00.2: i40e_ptp_stop: removed PHC on enP69p1s0f2 [52449.069793] i40e 0045:01:00.1: i40e_ptp_stop: removed PHC on enP69p1s0f1 [52449.173834] i40e 0045:01:00.0: i40e_ptp_stop: removed PHC on enP69p1s0f0 [52449.264462] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.4.25-k [52449.264468] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [52449.264625] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [52449.286138] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.505657] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [52449.508977] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 [52449.531210] i40e 0045:01:00.0: AQ command Config VSI BW allocation per TC failed = 14 [52449.531213] i40e 0045:01:00.0: Failed configuring TC map 255 for VSI 399 [52449.531217] i40e 0045:01:00.0: failed to configure TCs for main VSI tc_map 0x00ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL [52449.544642] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [52449.697424] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [52449.727043] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 0 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA [52449.727098] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass [52449.748667] i40e 0045:01:00.1: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [52449.976665] i40e 0045:01:00.1: MAC address: 68:05:ca:2d:e9:09 [52449.980685] i40e 0045:01:00.1: SAN MAC: 68:05:ca:2d:e9:0d [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 [52450.015610] i40e 0045:01:00.1 enP69p1s0f1: renamed from eth0 [52450.074479] i40e 0045:01:00.1: PCI-Express: Speed 8.0GT/s Width x8 [52450.080516] i40e 0045:01:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 128 RX: 1BUF RSS FD_ATR DCB VxLAN Geneve PTP VEPA Comparing function 0: [52449.529200] i40e 0045:01:00.0: DEBUG DATA vsi > 399;enabled_tc > 255 and function 1: [52449.994982] i40e 0045:01:00.1: DEBUG DATA vsi > 398;enabled_tc > 1 Then looking at 4.8: [ 123.425399] i40e: loading out-of-tree module taints kernel. [ 123.428958] i40e: module verification failed: signature and/or required key missing - tainting kernel [ 123.430690] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.6.11-k [ 123.430691] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [ 123.430918] i40e 0045:01:00.0: Using 64-bit DMA iommu bypass [ 123.450445] i40e 0045:01:00.0: fw 5.0.40043 api 1.5 nvm 5.02 0x80002284 0.0.0 [ 123.664088] i40e 0045:01:00.0: MAC address: 68:05:ca:2d:e9:08 [ 123.667878] i40e 0045:01:00.0: SAN MAC: 68:05:ca:2d:e9:0c [ 123.681915] Non-contiguous TC - Disabling DCB [ 123.690177] i40e 0045:01:00.0: DEBUG DATA vsi > 399, enabled_tc 1 [ 123.713262] i40e 0045:01:00.0 enP69p1s0f0: renamed from eth0 [ 123.864601] i40e 0045:01:00.0: Added LAN device PF0 bus=0x00 func=0x00 [ 123.864611] i40e 0045:01:00.0: PCI-Express: Speed 8.0GT/s Width x8 [ 123.893254] i40e 0045:01:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 128 RSS FD_ATR DCB VxLAN Geneve PTP VEPA [ 123.893321] i40e 0045:01:00.1: Using 64-bit DMA iommu bypass [ 123.9148
[Kernel-packages] [Bug 1624540] Re: please have lxd recommend zfs
As a note here, previous version of zfs-linux in Ubuntu loads the zfs kernel modules for everyone who has the package installed unconditionally, and since zfs-linux/0.6.5.9-4 (synced from Debian) they are only loaded when the system has at least one zpool configured (ConditionPathExists=/etc/zfs/zpool.cache), as expected by rlaager in comment #14. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1624540 Title: please have lxd recommend zfs Status in lxd package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: Confirmed Bug description: Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS userspace package, such that 'sudo lxd init' just works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1624540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10
The Xenial task was 'Fix Released' by mistake. Please revert back to '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/1572801 Title: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Bug description: Ubuntu 16.04 64bit ISO number 20160420.1 unity version 7.4.0+16.04.20160415-0ubuntu1 Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10 Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 21 01:44:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1920x1080+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 'unityshell']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PLUS 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.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 21 01:37:17 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671176] Re: linux: 4.8.0-42.45 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671176 Title: linux: 4.8.0-42.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-42.45 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-sru-workflow/+bug/1671176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
Hi kaihengfeng, yes that has effect, it works. But 0.1 is too slow, I've tried 0.25 and find it's usable. Thanks a lot. :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] [NEW] Graphics trouble after hibernation or Sleep
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672782 Title: Graphics trouble after hibernation or Sleep Status in linux package in Ubuntu: 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 1672785] [NEW] [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown
Public bug reported: Mellanox has submitted the following patch upstream that's important for SR-IOV in Azure. Please integrate it into the Mellanox mlx4 drivers for lts-xenial, HWE, Zesty, and Azure custom. https://patchwork.ozlabs.org/patch/738305/ From: Jack Morgenstein Some Hypervisors detach VFs from VMs by instantly causing an FLR event to be generated for a VF. In the mlx4 case, this will cause that VF's comm channel to be disabled before the VM has an opportunity to invoke the VF device's "shutdown" method. For such Hypervisors, there is a race condition between the VF's shutdown method and its internal-error detection/reset thread. The internal-error detection/reset thread (which runs every 5 seconds) also detects a disabled comm channel. If the internal-error detection/reset flow wins the race, we still get delays (while that flow tries repeatedly to detect comm-channel recovery). The cited commit fixed the command timeout problem when the internal-error detection/reset flow loses the race. This commit avoids the unneeded delays when the internal-error detection/reset flow wins. Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver device shutdown") Signed-off-by: Jack Morgenstein Reported-by: Simon Xiao Signed-off-by: Tariq Toukan --- drivers/net/ethernet/mellanox/mlx4/cmd.c | 11 +++ drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++ include/linux/mlx4/device.h | 1 + 3 files changed, 23 insertions(+) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1672785 Title: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown Status in linux package in Ubuntu: Confirmed Bug description: Mellanox has submitted the following patch upstream that's important for SR-IOV in Azure. Please integrate it into the Mellanox mlx4 drivers for lts-xenial, HWE, Zesty, and Azure custom. https://patchwork.ozlabs.org/patch/738305/ From: Jack Morgenstein Some Hypervisors detach VFs from VMs by instantly causing an FLR event to be generated for a VF. In the mlx4 case, this will cause that VF's comm channel to be disabled before the VM has an opportunity to invoke the VF device's "shutdown" method. For such Hypervisors, there is a race condition between the VF's shutdown method and its internal-error detection/reset thread. The internal-error detection/reset thread (which runs every 5 seconds) also detects a disabled comm channel. If the internal-error detection/reset flow wins the race, we still get delays (while that flow tries repeatedly to detect comm-channel recovery). The cited commit fixed the command timeout problem when the internal-error detection/reset flow loses the race. This commit avoids the unneeded delays when the internal-error detection/reset flow wins. Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver device shutdown") Signed-off-by: Jack Morgenstein Reported-by: Simon Xiao Signed-off-by: Tariq Toukan --- drivers/net/ethernet/mellanox/mlx4/cmd.c | 11 +++ drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++ include/linux/mlx4/device.h | 1 + 3 files changed, 23 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] 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/1672782 Title: Graphics trouble after hibernation or Sleep Status in linux package in Ubuntu: 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 1672785] Re: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown
I will add the upstream commit when this patch goes into linux-next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672785 Title: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown Status in linux package in Ubuntu: Confirmed Bug description: Mellanox has submitted the following patch upstream that's important for SR-IOV in Azure. Please integrate it into the Mellanox mlx4 drivers for lts-xenial, HWE, Zesty, and Azure custom. https://patchwork.ozlabs.org/patch/738305/ From: Jack Morgenstein Some Hypervisors detach VFs from VMs by instantly causing an FLR event to be generated for a VF. In the mlx4 case, this will cause that VF's comm channel to be disabled before the VM has an opportunity to invoke the VF device's "shutdown" method. For such Hypervisors, there is a race condition between the VF's shutdown method and its internal-error detection/reset thread. The internal-error detection/reset thread (which runs every 5 seconds) also detects a disabled comm channel. If the internal-error detection/reset flow wins the race, we still get delays (while that flow tries repeatedly to detect comm-channel recovery). The cited commit fixed the command timeout problem when the internal-error detection/reset flow loses the race. This commit avoids the unneeded delays when the internal-error detection/reset flow wins. Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver device shutdown") Signed-off-by: Jack Morgenstein Reported-by: Simon Xiao Signed-off-by: Tariq Toukan --- drivers/net/ethernet/mellanox/mlx4/cmd.c | 11 +++ drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++ include/linux/mlx4/device.h | 1 + 3 files changed, 23 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
I also put an xinput command into ~/.xsession xinput set-prop 'AlpsPS/2 ALPS DualPoint Stick' 'libinput Accel Speed' 0.1 to have some difference in pushing the stick hard or soft -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670634] Comment bridged from LTC Bugzilla
--- Comment From jac...@de.ibm.com 2017-03-14 12:07 EDT--- I was able to run into the hand now also without openafs, /var/log/syslog: Mar 14 15:10:46 mclint multipathd[887]: mpatha: sda - tur checker timed out Mar 14 15:10:46 mclint multipathd[887]: 8:0: reinstated Mar 14 15:10:46 mclint multipathd[887]: mpatha: sdb - tur checker timed out Mar 14 15:10:46 mclint multipathd[887]: 8:16: reinstated Mar 14 15:10:46 mclint multipathd[887]: mpatha: sdc - tur checker timed out Mar 14 15:10:46 mclint multipathd[887]: 8:32: reinstated Mar 14 15:10:46 mclint multipathd[887]: mpatha: sdd - tur checker timed out Mar 14 15:10:46 mclint multipathd[887]: 8:48: reinstated On the sclp_line console: ? 9841.149452! INFO: task btrfs-transacti:634 blocked for more than 120 seconds. ? 9841.149459! Not tainted 4.4.0-67-generic #88 ? 9841.149461! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9841.149627! INFO: task cpuplugd:2409 blocked for more than 120 seconds. ? 9841.149628! Not tainted 4.4.0-67-generic #88 ? 9841.149629! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9841.149674! INFO: task irqbalance:2515 blocked for more than 120 seconds. ? 9841.149675! Not tainted 4.4.0-67-generic #88 ? 9841.149676! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9841.149715! INFO: task kworker/0:2:3661 blocked for more than 120 seconds. ? 9841.149716! Not tainted 4.4.0-67-generic #88 ? 9841.149717! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9841.149752! INFO: task tar:16648 blocked for more than 120 seconds. ? 9841.149753! Not tainted 4.4.0-67-generic #88 ? 9841.149754! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9961.149482! INFO: task btrfs-transacti:634 blocked for more than 120 seconds. ? 9961.149489! Not tainted 4.4.0-67-generic #88 ? 9961.149490! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9961.149640! INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. ? 9961.149642! Not tainted 4.4.0-67-generic #88 ? 9961.149642! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9961.149727! INFO: task cpuplugd:2409 blocked for more than 120 seconds. ? 9961.149729! Not tainted 4.4.0-67-generic #88 ? 9961.149729! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9961.149772! INFO: task irqbalance:2515 blocked for more than 120 seconds. ? 9961.149773! Not tainted 4.4.0-67-generic #88 ? 9961.149773! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ? 9961.149811! INFO: task kworker/0:2:3661 blocked for more than 120 seconds. ? 9961.149812! Not tainted 4.4.0-67-generic #88 ? 9961.149812! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. I just made a new dump -> General dump info: Dump format: s390mv Version: 5 Dump created...: Tue, 14 Mar 2017 15:45:29 +0100 Dump ended.: Tue, 14 Mar 2017 15:46:07 +0100 Dump CPU ID: 9efc729648000 UTS node name..: mclint UTS kernel release.: 4.4.0-67-generic UTS kernel version.: #88 SMP Wed Mar 8 14:48:51 UTC 2017 Build arch.: s390x (64 bit) System arch: s390x (64 bit) CPU count (online).: 3 CPU count (real)...: 4 Dump memory range..: 8192 MB Real memory range..: 8192 MB The dump is currently uploaded to the Box-Folder -> mclint_20170314_kernel_4_4_0-67_without_openafs.dump.bz2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b83
[Kernel-packages] [Bug 1661430] Re: [Hyper-V] Fix ring buffer handling to avoid host throttling
HWE verified as well. ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661430 Title: [Hyper-V] Fix ring buffer handling to avoid host throttling 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: An unfortunate side effect of some of the recent work done to improve ring buffer performance made a situation where the host would interpret guest requests as a denial of service attack, pausing guest communications for five seconds. This series of fixes corrects this problem. Needed for each kernel that has included a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=74198eb4a42c4a3c4fbef08fa01a291a282f7c2e Drivers: hv: vmbus: Base host signaling strictly on the ring state One of the factors that can result in the host concluding that a given guest in mounting a DOS attack is if the guest generates interrupts to the host when the host is not expecting it. If these "spurious" interrupts reach a certain rate, the host can throttle the guest to minimize the impact. The host computation of the "expected number of interrupts" is strictly based on the ring transitions. Until the host logic is fixed, base the guest logic to interrupt solely on the ring state. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f6ee4e7d83586c8b10bd4f2f4346353d04ce884 Drivers: hv: vmbus: On write cleanup the logic to interrupt the host Signal the host when we determine the host is to be signaled. The currrent code determines the need to signal in the ringbuffer code and actually issues the signal elsewhere. This can result in the host viewing this interrupt as spurious since the host may also poll the channel. Make the necessary adjustments. https://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=3372592a140db69fd63837e81f048ab4abf8111e Drivers: hv: vmbus: On the read path cleanup the logic to interrupt the host Signal the host when we determine the host is to be signaled - on th read path. The currrent code determines the need to signal in the ringbuffer code and actually issues the signal elsewhere. This can result in the host viewing this interrupt as spurious since the host may also poll the channel. Make the necessary adjustments. https://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=433e19cf33d34bb6751c874a9c00980552fe508c Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read() Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()") added the proper mb(), but removed the test "prev_write_sz < pending_sz" when making the signal decision. As a result, the guest can signal the host unnecessarily, and then the host can throttle the guest because the host thinks the guest is buggy or malicious; finally the user running stress test can perceive intermittent freeze of the guest. This patch brings back the test, and properly handles the in-place consumption APIs used by NetVSC (see get_next_pkt_raw(), put_pkt_raw() and commit_rd_index()). Fixes: a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
This issue, or similar symptoms doesn't seem to be fixed. This is with stock kernel, stock stress-ng but with the suggested changes to the memory_stress_ng test script. The machine locks up completely maybe 1 out of 5-10 runs. See attached dmesg for errors. Kernel: 4.4.0-64-generic-85-Ubuntu stress-ng Version: 0.07.21-1~ppa ** Attachment added: "FAIL-2017-03-09-15-21-47.dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4837690/+files/FAIL-2017-03-09-15-21-47.dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 Status in Provider for Plainbox - Checkbox: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: memory_stress_ng, as part of server certification is failing for IBM Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is defined by the test locking up the server in an unrecoverable state which only a reboot will fix. I will be attaching screen and kern logs for the failures and a successful run on 14.04 on the same server. To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1573062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1663687] Re: [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
Looks good. ** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1663687 Title: [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Patchset: 1/6 Enable tracking of queue depth. 2/6 Remove the artificially imposed restriction on max segment size. 3/6 Enable multi-q support. We will allocate the outgoing channel using the following policy: 1. We will make every effort to pick a channel that is in the same NUMA node that is initiating the I/O 2. The mapping between the guest CPU and the outgoing channel is persistent. 4/6 Properly set SRB flags when hosting device supports tagged queuing. This patch improves the performance on Fiber Channel disks. 5/6 When sense message is present on error, we should pass along to the upper layer to decide how to deal with the error. This patch fixes connectivity issues with Fiber Channel devices. 6/6 On I/O errors, the Windows driver doesn't set data_transfer_length on error conditions other than SRB_STATUS_DATA_OVERRUN. In these cases we need to set data_transfer_length to 0, indicating there is no data transferred. On SRB_STATUS_DATA_OVERRUN, data_transfer_length is set by the Windows driver to the actual data transferred. The new feature (multi-q) in this patchset require boot line parameters to enable so they are safe to integrate. K. Y. Srinivasan (3): storvsc: Enable tracking of queue depth storvsc: Remove the restriction on max segment size storvsc: Enable multi-queue support Long Li (3): storvsc: use tagged SRB requests if supported by the device storvsc: properly handle SRB_ERROR when sense message is present storvsc: properly set residual data length on errors https://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=40630f462824ee24bc00d692865c86c3828094e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
We need to Breaks: snapd (<< 2.23.1~) to ensure this is upgraded before the new breaking kernels can hit. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-meta (Ubuntu) ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed ** Changed in: linux-meta (Ubuntu) Importance: Undecided => High ** Changed in: linux-meta (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux-meta package in Ubuntu: Confirmed Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
@Kai-Heng Feng, What are the odds of this backport patch being included with the next update from Canonical for 16.04. Since your recommended kernel is 4.4.0-68 do you think it will arrive as part of the regular release schedule? I can report if the patch worked when it arrives. As much as I love to support the work on these bugs, jumping kernels has left sour taste in my mouth. Switching between two kernels has sometimes created issues (bluetooth drivers not loading etc,.) that carry over into the previously stable kernel. Mostly this is my production/work machine and I am resistant to messing with it too much. :( Sorry to sound like a poor sport. C -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: My processor does not appear to be utilizing and idling states deeper than C3. 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 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 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: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666897] Re: snaps with classic + jailmode confinement started to fail on zesty
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666897 Title: snaps with classic + jailmode confinement started to fail on zesty Status in snapd: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: We just noticed that zesty stated to fail when a snap using classic confinement is installed in jailmode. $ snap install --jailmode --classic python0 $ python0 (doesn't work) /snap/python0/2/usr/bin/python0: error while loading shared libraries: libm.so.6: failed to map segment from shared object And in the system log you can see: [ 2929.841318] audit: type=1400 audit(1487770576.927:40): apparmor="DENIED" operation="file_mmap" profile="snap.python0.python0" name="/snap/core/1264/lib/x86_64-linux-gnu/libm-2.23.so" pid=5235 comm="python0" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1666897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672785] Re: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Zesty) Importance: Medium Status: Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Tags added: kernel-da-key kernel-hyper-v -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672785 Title: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Mellanox has submitted the following patch upstream that's important for SR-IOV in Azure. Please integrate it into the Mellanox mlx4 drivers for lts-xenial, HWE, Zesty, and Azure custom. https://patchwork.ozlabs.org/patch/738305/ From: Jack Morgenstein Some Hypervisors detach VFs from VMs by instantly causing an FLR event to be generated for a VF. In the mlx4 case, this will cause that VF's comm channel to be disabled before the VM has an opportunity to invoke the VF device's "shutdown" method. For such Hypervisors, there is a race condition between the VF's shutdown method and its internal-error detection/reset thread. The internal-error detection/reset thread (which runs every 5 seconds) also detects a disabled comm channel. If the internal-error detection/reset flow wins the race, we still get delays (while that flow tries repeatedly to detect comm-channel recovery). The cited commit fixed the command timeout problem when the internal-error detection/reset flow loses the race. This commit avoids the unneeded delays when the internal-error detection/reset flow wins. Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver device shutdown") Signed-off-by: Jack Morgenstein Reported-by: Simon Xiao Signed-off-by: Tariq Toukan --- drivers/net/ethernet/mellanox/mlx4/cmd.c | 11 +++ drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++ include/linux/mlx4/device.h | 1 + 3 files changed, 23 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] amaura (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/amaura__4.10.0-13.15__2017-03-14_16-58-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672563] Re: ubuntu 16.04 doesnt boot normally on my asus k550vx
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.11 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.11-rc2 ** 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/1672563 Title: ubuntu 16.04 doesnt boot normally on my asus k550vx Status in linux package in Ubuntu: Incomplete Bug description: i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even in this case when i try to install my nividia graphic cards driver, it never boots again after installation. my graphic card: nvidia 950m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] secchi (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/secchi__4.10.0-13.15__2017-03-14_17-00-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] naumann (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/naumann__4.10.0-13.15__2017-03-14_17-01-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
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.11 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.11-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672782 Title: Graphics trouble after hibernation or Sleep Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete 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 1672518] Re: Suspend -> Freeze
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Incomplete ** Changed in: linux (Ubuntu Yakkety) 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/1672518 Title: Suspend -> Freeze Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: Thinkpad SL510 freezes after SUSPEND Halfmoon-shaped LED is flashing, screen is black as should be, but nothing wakes the System up. Freeze or is system waiting for imput I cant deliver eg missing button? Google: Display driver at fault?! Keep up the good work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 13 20:52:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:213a] InstallationDate: Installed on 2017-03-06 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 2847BTG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET83WW (1.41 ) dmi.board.name: 2847BTG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6JET83WW(1.41):bd09/21/2010:svnLENOVO:pn2847BTG:pvrThinkPadSL510:rvnLENOVO:rn2847BTG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2847BTG dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Mar 13 20:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] fozzie (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/fozzie__4.10.0-13.15__2017-03-14_17-02-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] gonzo (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/gonzo__4.10.0-13.15__2017-03-14_17-05-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] archytas (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/archytas__4.10.0-13.15__2017-03-14_17-06-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] onibi (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/onibi__4.10.0-13.15__2017-03-14_17-06-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
Would it be possible for you to test this latest kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop 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 Bug description: booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic: Grub works, entering full disk encryption passphrase works, but when the desktop comes up mouse and keyboard (via USB) are dead and the desktop also. booting the PC without the stick attached works fine, but as soon as it is attached (see syslog) mouse, keyboard and the desktop itself are dead (checked by opening terminal and "watch date" - freezes, with desktop still visible). problem is resolved by booting former kernel 4.4.0-59-generic. syslog upon attaching stick --- Feb 21 07:17:02 orin kernel: [ 188.998338] usb 8-2: new high-speed USB device number 2 using xhci_hcd Feb 21 07:17:02 orin kernel: [ 189.129674] usb 8-2: New USB device found, idVendor=0bda, idProduct=8178 Feb 21 07:17:02 orin kernel: [ 189.129682] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 21 07:17:02 orin kernel: [ 189.129687] usb 8-2: Product: USB WLAN Feb 21 07:17:02 orin kernel: [ 189.129691] usb 8-2: Manufacturer: Realtek Feb 21 07:17:02 orin kernel: [ 189.129694] usb 8-2: SerialNumber: 00e04c01 Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: "/sys/devices/pci:00/:00:10.1/usb8/8-2" Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager... Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 'org.freedesktop.UDisks2' Feb 21 07:17:02 orin systemd[1]: Started Disk Manager. Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 on the system message bus Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive Feb 21 07:17:03 orin kernel: [ 190.200286] cfg80211: World regulatory domain updated: Feb 21 07:17:03 orin kernel: [ 190.200294] cfg80211: DFS Master region: unset Feb 21 07:17:03 orin kernel: [ 190.200297] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 21 07:17:03 orin kernel: [ 190.200303] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200308] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200312] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200317] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200321] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 21 07:17:03 orin kernel: [ 190.200325] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Feb 21 07:17:03 orin kernel: [ 190.200329] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200333] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.223081] rtl8192cu: Chip version 0x11 Feb 21 07:17:03 orin kernel: [ 190.625235] rtl8192cu: MAC address: 14:cc:20:10:43:98 Feb 21 07:17:03 orin kernel: [ 190.625241] rtl8192cu: Board Type 0 Feb 21 07:17:03 orin kernel: [ 190.626355] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 Feb 21 07:17:03 orin kernel: [ 190.626408] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7698] (wlan0): using nl80211 for WiFi device control Feb 21 07:17:03 orin kernel: [ 190.636625] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' Feb 21 07:17:03 orin kernel: [ 190.637211] usbcore: registered new interface driver rtl8192cu Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status... Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7780] device (wlan0): driver supports Access Point (AP) mode Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7798] manager: (wlan0): new 802.11 W
[Kernel-packages] [Bug 1671614] hainzel (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/hainzel__4.10.0-13.15__2017-03-14_17-04-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/ms10-34-mcdivittB0-kernel__4.10.0-13.15__2017-03-14_17-12-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/ms10-35-mcdivittB0-kernel__4.10.0-13.15__2017-03-14_17-12-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] rumford (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/rumford__4.10.0-13.15__2017-03-14_17-18-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/modoc__4.10.0-13.15__2017-03-14_17-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] alkaid (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/alkaid__4.10.0-13.15__2017-03-14_17-13-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
No, that's why I built a slightly newer kernel, 4.4.0-68, so it won't mess with the current release kernel, 4.4.0-66. It's okay if don't want to test it, I already tested it on Precision 5520 at my hand. The problem lies here is, 5520 has several different configs, I want to make sure the patch works on your machine. Otherwise what's the point? I assume the bluetooth symptom you saw mainly relates to the non- matching firmware is still in the chip, a cold boot instead of warm reboot should circumvent it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: My processor does not appear to be utilizing and idling states deeper than C3. 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 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 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: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] gonzo (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/gonzo__4.10.0-13.15__2017-03-14_17-31-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] fozzie (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/fozzie__4.10.0-13.15__2017-03-14_17-28-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672819] [NEW] exec'ing a setuid binary from a threaded program sometimes fails to setuid
Public bug reported: This can be reproduced with https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 With that, and go 1.8, if you run “make” and then for i in `seq 99`; do ./a_go; done you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there. That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue. But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated. If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: john 2354 F...m pulseaudio /dev/snd/controlC0: john 2354 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 17:17:23 2017 HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf InstallationDate: Installed on 2014-04-27 (1051 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: High Status: Triaged ** Affects: linux (Ubuntu Xenial) Importance: High Status: Triaged ** Tags: amd64 apport-bug kernel-key xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672819 Title: exec'ing a setuid binary from a threaded program sometimes fails to setuid Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This can be reproduced with https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 With that, and go 1.8, if you run “make” and then for i in `seq 99`; do ./a_go; done you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there. That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue. But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated. If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: john 2354 F...m pulseaudio /dev/snd/controlC0: john 2354 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 17:17:23 2017 HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae7
[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid
I also tried this in 4.10.0-11-generic, same results. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672819 Title: exec'ing a setuid binary from a threaded program sometimes fails to setuid Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This can be reproduced with https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 With that, and go 1.8, if you run “make” and then for i in `seq 99`; do ./a_go; done you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there. That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue. But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated. If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: john 2354 F...m pulseaudio /dev/snd/controlC0: john 2354 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 17:17:23 2017 HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf InstallationDate: Installed on 2014-04-27 (1051 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] onibi (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/onibi__4.10.0-13.15__2017-03-14_17-37-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Tags added: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672819 Title: exec'ing a setuid binary from a threaded program sometimes fails to setuid Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This can be reproduced with https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 With that, and go 1.8, if you run “make” and then for i in `seq 99`; do ./a_go; done you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there. That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue. But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated. If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: john 2354 F...m pulseaudio /dev/snd/controlC0: john 2354 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 17:17:23 2017 HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf InstallationDate: Installed on 2014-04-27 (1051 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] alkaid (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/alkaid__4.10.0-13.15__2017-03-14_17-48-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid
I can reproduce this with the simple pthreads-only reproducer (loop of ./a_p running setuid binary ./b) running 4.4.0-57-generic on bare metal. $ for i in `seq 10`; do ./a_p; done GOT 1000 GOT 1000 $ for i in `seq 1000`; do ./a_p; done | wc -l 117 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672819 Title: exec'ing a setuid binary from a threaded program sometimes fails to setuid Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This can be reproduced with https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 With that, and go 1.8, if you run “make” and then for i in `seq 99`; do ./a_go; done you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there. That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue. But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated. If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: john 2354 F...m pulseaudio /dev/snd/controlC0: john 2354 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 17:17:23 2017 HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf InstallationDate: Installed on 2014-04-27 (1051 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid
An AWS instance (t2.xlarge with 4 vCPU's) running 4.4.0-1001-aws reproduces the problem: $ for i in `seq 1`; do ./a_p; done | wc -l 124 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672819 Title: exec'ing a setuid binary from a threaded program sometimes fails to setuid Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This can be reproduced with https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 With that, and go 1.8, if you run “make” and then for i in `seq 99`; do ./a_go; done you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there. That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue. But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated. If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: john 2354 F...m pulseaudio /dev/snd/controlC0: john 2354 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 17:17:23 2017 HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf InstallationDate: Installed on 2014-04-27 (1051 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672521] Re: ThunderX: soft lockup on 4.8+ kernels
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 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.11-rc2 ** 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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Status in linux source package in Zesty: Triaged Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr0100:rvnGIGABYTE:rnMT30-GS0:rvr01234567:cvnGIGABYTE:ct17:cvr01234567:
[Kernel-packages] [Bug 1672455] Re: Mainline Kernel repo does not use https
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1672455 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. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-development-workflow ** 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/1672455 Title: Mainline Kernel repo does not use https Status in linux package in Ubuntu: Incomplete Bug description: Mainline kernels are provided at http://kernel.ubuntu.com/~kernel-ppa This is very convenient, especially if one has the latest hardware for which older kernels often do not have hardware support. However https://kernel.ubuntu.com/~kernel-ppa does not work. I do not have a great feeling installing something as crucial as a kernel without trusting the source. Of course one could in theory try to reproduce the build by compiling from source, but in practice this is hardly a viable solutions. Proposed solution: Enable https with a trusted certificate for https://kernel.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672536] Re: task btrfs:841 blocked for more than 120 seconds.
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.11 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.11-rc2 ** 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/1672536 Title: task btrfs:841 blocked for more than 120 seconds. Status in linux package in Ubuntu: Incomplete Bug description: After starting `btrfs scrub start /` `dmesg` contains ``` [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,02] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,03] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,02] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,02] [] ? do_nanosleep+0x96/0xf0 [ +0,03] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,02] [] ? do_nanosleep+0x5a/0xf0 [ +0,03] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,10] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,34] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,02] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,32] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_
[Kernel-packages] [Bug 1672521] Re: ThunderX: soft lockup on 4.8+ kernels
If the mainline kernel still exhibits the bug, we can perform a kernel bisect to identify what commit introduced the regression. If the mainline kernel fixes the bug, we can perform a "Reverse" bisect to identify the fix. ** Also affects: linux (Ubuntu Zesty) Importance: High Status: Confirmed ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** Changed in: linux (Ubuntu Zesty) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => High ** Tags added: kernel-da-key needs-bisect 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/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Status in linux source package in Zesty: Triaged Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:pnR120-T30:pvr
[Kernel-packages] [Bug 1672563] Re: ubuntu 16.04 doesnt boot normally on my asus k550vx
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672563 Title: ubuntu 16.04 doesnt boot normally on my asus k550vx Status in linux package in Ubuntu: Incomplete Bug description: i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even in this case when i try to install my nividia graphic cards driver, it never boots again after installation. my graphic card: nvidia 950m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] secchi (amd64) - tests ran: 21, failed: 1
tests ran: 21, failed: 1; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/secchi__4.10.0-13.15__2017-03-14_17-22-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] naumann (amd64) - tests ran: 21, failed: 1
tests ran: 21, failed: 1; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/naumann__4.10.0-13.15__2017-03-14_17-24-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] pepe (amd64) - tests ran: 10, failed: 0
tests ran: 10, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/pepe__4.10.0-13.15__2017-03-14_17-09-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672785] Re: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown
I built a Zesty test kernel with the patch. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1672785/zesty/ The patch does not apply cleanly to Xenial. I'll investigate and see if prereq commits are needed and backport. I'll post that kernel shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672785 Title: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Mellanox has submitted the following patch upstream that's important for SR-IOV in Azure. Please integrate it into the Mellanox mlx4 drivers for lts-xenial, HWE, Zesty, and Azure custom. https://patchwork.ozlabs.org/patch/738305/ From: Jack Morgenstein Some Hypervisors detach VFs from VMs by instantly causing an FLR event to be generated for a VF. In the mlx4 case, this will cause that VF's comm channel to be disabled before the VM has an opportunity to invoke the VF device's "shutdown" method. For such Hypervisors, there is a race condition between the VF's shutdown method and its internal-error detection/reset thread. The internal-error detection/reset thread (which runs every 5 seconds) also detects a disabled comm channel. If the internal-error detection/reset flow wins the race, we still get delays (while that flow tries repeatedly to detect comm-channel recovery). The cited commit fixed the command timeout problem when the internal-error detection/reset flow loses the race. This commit avoids the unneeded delays when the internal-error detection/reset flow wins. Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver device shutdown") Signed-off-by: Jack Morgenstein Reported-by: Simon Xiao Signed-off-by: Tariq Toukan --- drivers/net/ethernet/mellanox/mlx4/cmd.c | 11 +++ drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++ include/linux/mlx4/device.h | 1 + 3 files changed, 23 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
Should I install all four .deb packages in the link you provided? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: My processor does not appear to be utilizing and idling states deeper than C3. 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 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 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: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] archytas (amd64) - tests ran: 21, failed: 1
tests ran: 21, failed: 1; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/archytas__4.10.0-13.15__2017-03-14_17-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671614] hainzel (amd64) - tests ran: 21, failed: 1
tests ran: 21, failed: 1; http://kernel.ubuntu.com/testing/4.10.0-13.15-generic/hainzel__4.10.0-13.15__2017-03-14_17-31-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671614 Title: linux: 4.10.0-13.15 -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: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-13.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: 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/1671614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
Okay. I'll try it out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: My processor does not appear to be utilizing and idling states deeper than C3. 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 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 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: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672521] Re: ThunderX: soft lockup on 4.8+ kernels
Hi, I tried out 4.11-rc1 a few days ago. Unfortunately, I did not get the board to boot properly from the start, since ThunderX networking drivers failed to allocate MSI-X/MSI interrupts, and polling on some registers also failed ... So, with 4.11-rc1, at least one networking interfaces was never coming online due to unmapped interrupts/failed polling, but unloading `nicpf` and reloading it seemed to work (networking worked after this). After this, the soft lockup happened, but I can't be sure I did not mess something else. Let me try this again and get back to you with some proper logs, but off the top of my head, things got worse with 4.11-rc1 ... Thanks, Alex -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672521 Title: ThunderX: soft lockup on 4.8+ kernels Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Status in linux source package in Zesty: Triaged Bug description: I have been trying to easily reproduce this for days. We initially observed it in OPNFV Armband, when we tried to upgrade our Ubuntu Xenial installation kernel to linux-image-generic-hwe-16.04 (4.8). In our environment, this was easily triggered on compute nodes, when launching multiple VMs (we suspected OVS, QEMU etc.). However, in order to rule out our specifics, we looked for a simple way to reproduce it on all ThunderX nodes we have access to, and we finally found it: $ apt-get install stress-ng $ stress-ng --hdd 1024 We tested different FW versions, provided by both chip/board manufacturers, and with all of them the result is 100% reproductible, leading to a kernel Oops [1]: [ 726.070531] INFO: task kworker/0:1:312 blocked for more than 120 seconds. [ 726.077908] Tainted: GW I 4.8.0-41-generic #44~16.04.1-Ubuntu [ 726.085850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.094383] kworker/0:1 D 080861bc 0 312 2 0x [ 726.094401] Workqueue: events vmstat_shepherd [ 726.094404] Call trace: [ 726.094411] [] __switch_to+0x94/0xa8 [ 726.094418] [] __schedule+0x224/0x718 [ 726.094421] [] schedule+0x38/0x98 [ 726.094425] [] schedule_preempt_disabled+0x14/0x20 [ 726.094428] [] __mutex_lock_slowpath+0xd4/0x168 [ 726.094431] [] mutex_lock+0x58/0x70 [ 726.094437] [] get_online_cpus+0x44/0x70 [ 726.094440] [] vmstat_shepherd+0x3c/0xe8 [ 726.094446] [] process_one_work+0x150/0x478 [ 726.094449] [] worker_thread+0x50/0x4b8 [ 726.094453] [] kthread+0xec/0x100 [ 726.094456] [] ret_from_fork+0x10/0x40 Over the last few days, I tested all 4.8-* and 4.10 (zesty backport), the soft lockup happens with each and every one of them. On the other hand, 4.4.0-45-generic seems to work perfectly fine (probably newer 4.4.0-* too, but due to a regression in the ethernet drivers after 4.4.0-45, we can't test those with ease) under normal conditions, yet running stress-ng leads to the same oops. [1] http://paste.ubuntu.com/24172516/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 13 19:27 seq crw-rw 1 root audio 116, 33 Mar 13 19:27 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 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 IwConfig: Error: [Errno 2] No such file or directory MachineType: GIGABYTE R120-T30 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic root=/dev/mapper/os-root ro console=tty0 console=ttyS0,115200 console=ttyAMA0,115200 net.ifnames=1 biosdevname=0 rootdelay=90 nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-41-generic N/A linux-backports-modules-4.8.0-41-generic N/A linux-firmware1.157.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-41-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/22/2016 dmi.bios.vendor: GIGABYTE dmi.bios.version: T22 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MT30-GS0 dmi.board.vendor: GIGABYTE dmi.board.version: 01234567 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 17 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrT22:bd11/22/2016:svnGIGABYTE:p
[Kernel-packages] [Bug 1672455] Re: Mainline Kernel repo does not use https
Running apport-collect 1672455 doesn't make any sense, since the ppa- webserver is of concern here. It is easy to verify this bug: Just point a browser to https://kernel.ubuntu.com/~kernel-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/1672455 Title: Mainline Kernel repo does not use https Status in linux package in Ubuntu: Confirmed Bug description: Mainline kernels are provided at http://kernel.ubuntu.com/~kernel-ppa This is very convenient, especially if one has the latest hardware for which older kernels often do not have hardware support. However https://kernel.ubuntu.com/~kernel-ppa does not work. I do not have a great feeling installing something as crucial as a kernel without trusting the source. Of course one could in theory try to reproduce the build by compiling from source, but in practice this is hardly a viable solutions. Proposed solution: Enable https with a trusted certificate for https://kernel.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp