[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d
Here you go, cpuid -1 -r output. ** Attachment added: "cpuid -1 -r output c3.large instances" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657733/+files/cpuid_raw.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/1573231 Title: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do- release-upgrade -d Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xefff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at [880fbba0] [0.00] Scanning 1 areas for low memory corruption [0.00] RAMDISK: [mem 0x3407e000-0x36036fff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM HVML ) [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM INTL 20090123) [0.00] No NUMA configuration found [0.00] Faking a node at [mem 0x-0x0001efff] [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x] [0.00] Normal [mem 0x0001-0x0001efff] [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009dfff] [
[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards
freeze/hang forever, the pc gets stuck and it does not recover, i have to hard reboot it. I could not see the freeze synced with the 5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579190 Title: Key 5 automatically pressed on some Logitech wireless keyboards Status in linux package in Ubuntu: Incomplete Bug description: I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5. It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage. It seems that this is a Linux specific issue as no one is complaining about this issue under Windows, but a couple of people are complaining for different versions of Ubuntu. It is always 5 and WladyXX3740 claims on the Logitech forum that: "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related." Here is where most of the people are complaining: https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639 I discovered that this is related to my Logitech keyboard by running this command: xinput test-xi2 --root Here is the device list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ Logitech M310/M310t id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ DELL Wireless hotkeys id=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] And some extract from the output when this happens: EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 12 (PropertyEvent) property: 308 'Synaptics Off' changed: modified EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.21.22 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
In the mainline kernel install instructions i too had noticed that it mentioned out-of-tree modules could interfere with the kernel installations, and so i wondered if they could be causing problems in other ways as well. Specifically Virtualbox. I did not see the specific error message that the instructions had listed but i had planned to uninstall virtualbox just in case. It seems i forgot to do that. I have uninstalled virtualbox and am testing 4.6.0-040600rc5-generic kernel again. Currently i have watched several youtube videos without incident, but i will keep testing. Is it possible that virtualbox is part of the root problem? Strange that it didn't cause issues in 14.04, but it would later. But not an impossible scenario. I still have yet to do the kernel bisecting as i'm still a little confused at the basic process. I think it involves compiling kernels manually. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] onza (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/onza__4.4.0-22.39__2016-05-07_03-53-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550300] Re: hp C7000 and bl460c gen 8 - Virtual Fan issue
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550300 Title: hp C7000 and bl460c gen 8 - Virtual Fan issue Status in linux package in Ubuntu: Expired Bug description: Hi, i installed system ubuntu 12.04.5 on a c7000 of type bl460c gen 8. After machine is started up it stroke Virtual Fan of chassis to 100% of cpu. Installing sensors i detect only temperature, not any type of fun : root@lastline-engine:~/apport# sensors acpitz-virtual-0 Adapter: Virtual device temp1: +8.3�C (crit = +31.3�C) coretemp-isa- Adapter: ISA adapter Physical id 0: +33.0�C (high = +85.0�C, crit = +95.0�C) Core 0: +31.0�C (high = +85.0�C, crit = +95.0�C) Core 1: +31.0�C (high = +85.0�C, crit = +95.0�C) Core 2: +31.0�C (high = +85.0�C, crit = +95.0�C) Core 3: +32.0�C (high = +85.0�C, crit = +95.0�C) Core 4: +33.0�C (high = +85.0�C, crit = +95.0�C) Core 8: +32.0�C (high = +85.0�C, crit = +95.0�C) Core 9: +30.0�C (high = +85.0�C, crit = +95.0�C) Core 10:+30.0�C (high = +85.0�C, crit = +95.0�C) Core 11:+32.0�C (high = +85.0�C, crit = +95.0�C) Core 12:+31.0�C (high = +85.0�C, crit = +95.0�C) coretemp-isa-0001 Adapter: ISA adapter Physical id 1: +34.0�C (high = +85.0�C, crit = +95.0�C) Core 0: +31.0�C (high = +85.0�C, crit = +95.0�C) Core 1: +31.0�C (high = +85.0�C, crit = +95.0�C) Core 2: +28.0�C (high = +85.0�C, crit = +95.0�C) Core 3: +27.0�C (high = +85.0�C, crit = +95.0�C) Core 4: +30.0�C (high = +85.0�C, crit = +95.0�C) Core 8: +32.0�C (high = +85.0�C, crit = +95.0�C) Core 9: +34.0�C (high = +85.0�C, crit = +95.0�C) Core 10:+32.0�C (high = +85.0�C, crit = +95.0�C) Core 11:+31.0�C (high = +85.0�C, crit = +95.0�C) Core 12:+31.0�C (high = +85.0�C, crit = +95.0�C) cooling device seems attached but cannot view them : root@lastline-engine:~/apport# more /sys/class/thermal/cooling_device*/cur_state :: /sys/class/thermal/cooling_device0/cur_state :: 0 :: /sys/class/thermal/cooling_device10/cur_state :: 0 :: /sys/class/thermal/cooling_device11/cur_state :: 0 :: /sys/class/thermal/cooling_device12/cur_state :: 0 :: /sys/class/thermal/cooling_device13/cur_state :: 0 :: /sys/class/thermal/cooling_device14/cur_state :: 0 :: /sys/class/thermal/cooling_device15/cur_state :: 0 :: /sys/class/thermal/cooling_device16/cur_state :: 0 :: /sys/class/thermal/cooling_device17/cur_state :: 0 :: /sys/class/thermal/cooling_device18/cur_state :: 0 :: /sys/class/thermal/cooling_device19/cur_state :: 0 :: /sys/class/thermal/cooling_device1/cur_state :: 0 :: /sys/class/thermal/cooling_device20/cur_state :: 0 :: /sys/class/thermal/cooling_device21/cur_state :: 0 :: /sys/class/thermal/cooling_device22/cur_state :: 0 :: /sys/class/thermal/cooling_device23/cur_state :: 0 :: /sys/class/thermal/cooling_device24/cur_state :: 0 :: /sys/class/thermal/cooling_device25/cur_state :: 0 :: /sys/class/thermal/cooling_device26/cur_state :: 0 :: /sys/class/thermal/cooling_device27/cur_state :: 0 :: /sys/class/thermal/cooling_device28/cur_state :: 0 :: /sys/class/thermal/cooling_device29/cur_state :: 0 :: /sys/class/thermal/cooling_device2/cur_state :: 0 :: /sys/class/thermal/cooling_device30/cur_state :: 0 :: /sys/class/thermal/cooling_device31/cur_state :: 0 :: /sys/class/thermal/cooling_device32/cur_state :: 0 :: /sys/class/thermal/cooling_device33/cur_state :: 0 :: /sys/class/thermal/cooling_device34/cur_state :: 0 :: /sys/class/thermal/cooling_device35/cur_state :: 0 :: /sys/class/thermal/cooling_device36/cur_state :: 0 :: /sys/class/thermal/cooling_device37/cur_state ::
[Kernel-packages] [Bug 1550873] Re: suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550873 Title: suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: Using my Thinkpad X250 Core i5 5200U and Lubuntu 14.04 64bit. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-51-generic 3.19.0-51.58~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Sun Feb 28 06:34:49 2016 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1447090102 Failure: suspend/resume InstallationDate: Installed on 2016-02-06 (21 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) InterpreterPath: /usr/bin/python3.4 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: linux-lts-vivid Title: suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francis1991 F pulseaudio /dev/snd/controlC1: francis1991 F pulseaudio CRDA: Error: [Errno 2] No existe el archivo o el directorio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e23ab1fe-1941-45a2-a0cc-829a7527cd3d InstallationDate: Installed on 2016-02-06 (29 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO 20CLS6 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-51-generic root=UUID=41c8a9f0-1196-4f53-b5d8-5735a14d045a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 RelatedPackageVersions: linux-restricted-modules-3.19.0-51-generic N/A linux-backports-modules-3.19.0-51-generic N/A linux-firmware 1.127.20 Tags: trusty Uname: Linux 3.19.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET33W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS6 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CLS6:pvrThinkPadX250:rvnLENOVO:rn20CLS6:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CLS6 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1553400] Re: BUG: unable to handle kernel NULL pointer dereference at (null)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1553400 Title: BUG: unable to handle kernel NULL pointer dereference at (null) Status in linux package in Ubuntu: Expired Bug description: Filesystem IO has started hanging when trying to access certain directories. Relevant kernel oops below: [12779.747913] BUG: unable to handle kernel NULL pointer dereference at (null) [12779.747961] IP: [] locked_inode_to_wb_and_lock_list+0x22/0xd0 [12779.748004] PGD 743c6067 PUD 1490067 PMD 0 [12779.748028] Oops: [#1] SMP [12779.748047] Modules linked in: sunrpc veth ctr ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables cmac hid_multitouch btusb btrtl btbcm btintel hid_logitech_hidpp pn544_mei mei_phy pn544 hci nfc uvcvideo vi deobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media rfcomm bnep dell_wmi sparse_keymap bluetooth arc4 dell_laptop dcdbas dell_smm_hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel snd_hda_intel kvm binfmt_misc snd_hda_codec snd_hda_core snd_soc_rt5640 snd_soc_rl6231 snd_soc_core snd_hwdep snd_compress ac97_bus snd_ pcm_dmaengine iwlmvm snd_pcm mac80211 snd_seq_midi snd_seq_midi_event snd_rawmidi joydev input_leds iwlwifi serio_raw snd_seq cfg80211 snd_seq_device lpc_ich snd_timer 8250_fintek i2c_hid snd i2c_designware_platform dw_dmac dell_smo8800 i2c_designware_core dw_dmac_core snd_soc_sst_acpi 8250_dw shpchp dell_rbtn soundcore mei_me spi_pxa2xx_platform mei mac_hid nls_iso8859_1 parport_pc ppdev lp parport drbg ansi_cprng hid_log itech_dj hid_generic dm_crypt usbhid hid crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i915 cryptd psmouse ahci libahci e1000e sdhci_pci ptp i2c_algo_bit pps_core drm_kms_helper drm wmi video sdhci_acpi sdhci [12779.748879] CPU: 0 PID: 25793 Comm: node Tainted: GW OE 4.2.0-30-generic #36~14.04.1-Ubuntu [12779.748931] Hardware name: Dell Inc. Latitude E7440/085VV3, BIOS A15 05/19/2015 [12779.748973] task: 880228d85280 ti: 88040b7a4000 task.ti: 88040b7a4000 [12779.749013] RIP: 0010:[] [] locked_inode_to_wb_and_lock_list+0x22/0xd0 [12779.749068] RSP: 0018:88040b7a7838 EFLAGS: 00010246 [12779.749095] RAX: RBX: RCX: 8802f51a1a00 [12779.749131] RDX: 0001 RSI: 8802f51a2230 RDI: 8802f51a1cf8 [12779.749170] RBP: 88040b7a7858 R08: R09: 0246 [12779.749206] R10: 0eb61400 R11: ea000ce357c0 R12: 8802f51a1cf8 [12779.749241] R13: 8802f51a1d80 R14: R15: 0125 [12779.749275] FS: 7f5bc8a24740() GS:88041ea0() knlGS: [12779.749316] CS: 0010 DS: ES: CR0: 80050033 [12779.749345] CR2: CR3: d4d3a000 CR4: 001406f0 [12779.749380] Stack: [12779.749391] 8802f51a1cf8 009d 81832e80 [12779.749430] 88040b7a7878 81217c43 8802f51a1cf8 009d [12779.749469] 88040b7a78a8 812051f3 88040b7a78c8 88040b7a78d8 [12779.749514] Call Trace: [12779.749533] [] inode_wb_list_del+0x23/0x50 [12779.749566] [] evict+0x53/0x180 [12779.749592] [] dispose_list+0x3a/0x50 [12779.749619] [] prune_icache_sb+0x4b/0x60 [12779.749645] [] super_cache_scan+0x141/0x190 [12779.749676] [] shrink_slab+0x207/0x380 [12779.749703] [] shrink_zone+0x291/0x2b0 [12779.749729] [] do_try_to_free_pages+0x15c/0x420 [12779.749759] [] ? pfmemalloc_watermark_ok+0xc0/0xe0 [12779.749788] [] try_to_free_pages+0xb4/0x140 [12779.749818] [] __alloc_pages_nodemask+0x5af/0x990 [12779.749855] [] ? free_pgtables+0xc6/0x110 [12779.749890] [] alloc_pages_vma+0x1de/0x200 [12779.749925] [] do_huge_pmd_anonymous_page+0x116/0x410 [12779.749964] [] handle_mm_fault+0x18c/0x1810 [12779.749998] [] ? security_mmap_file+0xca/0xe0 [12779.750033] [] ? vm_mmap_pgoff+0x98/0xc0 [12779.750066] [] __do_page_fault+0x19a/0x430 [12779.750100] [] do_page_fault+0x22/0x30 [12779.750133] [] page_fault+0x28/0x30 [12779.750163] Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 56 41 55 4c 8d af 88 00 00 00 41 54 49 89 fc 53 49 8b 9c 24 00 01 00 00 <48> 8b 03 48 83 c0 50 48 39 c3 74 13 48 8b 83 10 02 00 00 a8 03 [12779.750307] RIP []
[Kernel-packages] [Bug 1552493] Re: no samba share after suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1552493 Title: no samba share after suspend Status in linux package in Ubuntu: Expired Bug description: After resuming from standby, the samba shares go missing and only restored after a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.2.0-30-generic 4.2.0-30.36~14.04.1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 3 06:45:06 2016 InstallationDate: Installed on 2016-03-02 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160216) SourcePackage: linux-lts-wily UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arup 2078 F pulseaudio /dev/snd/controlC2: arup 2078 F pulseaudio /dev/snd/controlC1: arup 2078 F pulseaudio /dev/snd/controlC3: arup 2078 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=8cd2dc30-7c52-4f01-b1e5-00440a260ddd InstallationDate: Installed on 2016-03-04 (2 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160216) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7850 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=af47955f-3067-49dd-9267-d9488727642d ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 RelatedPackageVersions: linux-restricted-modules-4.2.0-30-generic N/A linux-backports-modules-4.2.0-30-generic N/A linux-firmware1.127.20 RfKill: Tags: trusty Uname: Linux 4.2.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.11:bd02/16/2016:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1536552] Re: TouchPad not working on Acer Aspire R5-471T (called also R14)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1536552 Title: TouchPad not working on Acer Aspire R5-471T (called also R14) Status in linux package in Ubuntu: Expired Bug description: The touchpad is not working at all. Works good on pre-installed Windows 10. I don't know the brand/model of the touchpad. Regards, Tom ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-47-generic 3.19.0-47.53~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 21 10:38:55 2016 InstallationDate: Installed on 2016-01-20 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1573 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=b5897211-5dc4-45a0-9d13-3b1f4a256288 InstallationDate: Installed on 2016-03-04 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire R5-471T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=afe2d21d-63b1-42e3-9f61-514a47068a7b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 RelatedPackageVersions: linux-restricted-modules-4.2.0-30-generic N/A linux-backports-modules-4.2.0-30-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/11/2015 dmi.bios.vendor: Acer dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Luffy dmi.board.vendor: Acer dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV1.03:bd09/11/2015:svnAcer:pnAspireR5-471T:pvrV1.03:rvnAcer:rnLuffy:rvrV1.03:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire R5-471T dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] bantam (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/bantam__4.4.0-22.39__2016-05-07_02-40-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579296] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579296 Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: This happens while upgrading from Ubuntu 14.04.4 to Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 03:33 seq crw-rw 1 root audio 116, 33 May 7 03:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat May 7 03:34:30 2016 Ec2AMI: ami-009c Ec2AMIManifest: FIXME Ec2AvailabilityZone: az2 Ec2InstanceType: SSD.30 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ErrorMessage: subprocess installed post-installation script returned error exit status 2 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=cf46d380-0e4b-4826-88dc-d612eb447071 ro quiet RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.4 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579296] [NEW] package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: This happens while upgrading from Ubuntu 14.04.4 to Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 03:33 seq crw-rw 1 root audio 116, 33 May 7 03:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat May 7 03:34:30 2016 Ec2AMI: ami-009c Ec2AMIManifest: FIXME Ec2AvailabilityZone: az2 Ec2InstanceType: SSD.30 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ErrorMessage: subprocess installed post-installation script returned error exit status 2 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=cf46d380-0e4b-4826-88dc-d612eb447071 ro quiet RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.4 dmi.sys.vendor: OpenStack Foundation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images 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/1579296 Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: New Bug description: This happens while upgrading from Ubuntu 14.04.4 to Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 03:33 seq crw-rw 1 root audio 116, 33 May 7 03:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat May 7 03:34:30 2016 Ec2AMI: ami-009c Ec2AMIManifest: FIXME Ec2AvailabilityZone: az2 Ec2InstanceType: SSD.30 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ErrorMessage: subprocess installed post-installation script returned error exit status 2 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=cf46d380-0e4b-4826-88dc-d612eb447071 ro quiet RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.4:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.4 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1578721] onza (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/onza__4.4.0-22.39__2016-05-07_02-46-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 1
tests ran: 1, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-22.39/ms10-35-mcdivittB0-kernel__4.4.0-22.39__2016-05-06_23-14-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server)
** Summary changed: - Consider changing default CPU frequency scaling governor back to "performance" + Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" (Ubuntu Server) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00% __tick_nohz_idle_enter | 0.00% irq_entries_start | 0.00%
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00% __tick_nohz_idle_enter | 0.00% irq_entries_start | 0.00% sched_clock_idle_wakeup_event | 0.00% reschedule_interrupt
[Kernel-packages] [Bug 1578721] onza (amd64) - tests ran: 26, failed: 0
tests ran: 26, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/onza__4.4.0-22.39__2016-05-06_21-56-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] Re: Remote Desktop error when connect to the Ubuntu LTS 16.04
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+attachment/4657653/+files/Lspci.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+attachment/4657659/+files/WifiSyslog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+attachment/4657658/+files/UdevDb.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+attachment/4657657/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] bantam (amd64) - tests ran: 23, failed: 0
tests ran: 23, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/bantam__4.4.0-22.39__2016-05-07_01-21-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled
Same problem continues with 4.4.0-22. -- 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/1572659 Title: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled Status in bcmwl package in Ubuntu: Confirmed Bug description: After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver (package bcmwl-kernel-source) does not load and wifi not work. sudo modprobe wl modprobe: ERROR: could not insert 'wl': Required key not available If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works. If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21 and wifi works. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-12-02 (140 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NonfreeKernelModules: wl Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] onibi (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/onibi__4.4.0-22.39__2016-05-07_00-30-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] Re: Remote Desktop error when connect to the Ubuntu LTS 16.04
apport information ** Tags added: apport-collected xenial ** Description changed: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial + --- + ApportVersion: 2.20.1-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a + InstallationDate: Installed on 2015-09-08 (241 days ago) + InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) + MachineType: HP ProLiant DL360 Gen9 + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_US + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro + ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.4.0-21-generic N/A + linux-backports-modules-4.4.0-21-generic N/A + linux-firmware1.157 + RfKill: + + Tags: xenial + Uname: Linux 4.4.0-21-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 11/03/2014 + dmi.bios.vendor: HP + dmi.bios.version: P89 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL360 Gen9 + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657648/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic
[Kernel-packages] [Bug 1579282] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657658/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657651/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657653/+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/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657655/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657656/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657654/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657659/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657657/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657649/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657650/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1579282/+attachment/4657652/+files/JournalErrors.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/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a InstallationDate: Installed on 2015-09-08 (241 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/03/2014 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] bantam (i386) - tests ran: 13, failed: 1
tests ran: 13, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-22.39/bantam__4.4.0-22.39__2016-05-06_21-07-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] Re: Remote Desktop error when connect to the Ubuntu LTS 16.04
** Description changed: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) - Major opcode of failed request: 109 (X_ChangeHosts) - Value in failed request: 0x5 - Serial number of failed request: 6 - Current serial number in output stream: 8 + Major opcode of failed request: 109 (X_ChangeHosts) + Value in failed request: 0x5 + Serial number of failed request: 6 + Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) - Major opcode of failed request: 109 (X_ChangeHosts) - Value in failed request: 0x5 - Serial number of failed request: 6 - Current serial number in output stream: 8 + Major opcode of failed request: 109 (X_ChangeHosts) + Value in failed request: 0x5 + Serial number of failed request: 6 + Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 + + ##lsb_release -a + No LSB modules are available. + Distributor ID: Ubuntu + Description:Ubuntu 16.04 LTS + Release:16.04 + Codename: 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/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1579282 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579282] [NEW] Remote Desktop error when connect to the Ubuntu LTS 16.04
Public bug reported: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1579282 Title: Remote Desktop error when connect to the Ubuntu LTS 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed. The .xsession-errors log as followings, #cat .xsession-errors Xsession: X session started for at Fri May 6 17:52:57 PDT 2016 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:ubuntu being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 /etc/xrdp/startwm.sh: 3: [: x: unexpected operator #cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 ##lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579281] [NEW] Please update iwlwifi firmwares to include versions 17-19
Public bug reported: Linux firmware git has these new firware revisions that are supported by the drivers shipped in Ubuntu (and it actually tries to load them): May 2 20:57:35 t460s kernel: [2.873419] Intel(R) Wireless WiFi driver for Linux May 2 20:57:35 t460s kernel: [2.873422] Copyright(c) 2003- 2015 Intel Corporation May 2 20:57:35 t460s kernel: [2.873794] iwlwifi :04:00.0: enabling device ( -> 0002) May 2 20:57:35 t460s kernel: [2.877881] iwlwifi :04:00.0: Unsupported splx structure May 2 20:57:35 t460s kernel: [2.878491] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 May 2 20:57:35 t460s kernel: [2.878504] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 May 2 20:57:35 t460s kernel: [2.878515] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 May 2 20:57:35 t460s kernel: [2.884163] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm Adding iwlwifi-8000C-19.ucode works as expected: [21431.655352] iwlwifi :04:00.0: loaded firmware version 19.313137.0 op_mode iwlmvm So, please include these new revisions in the Ubuntu package (for xenial too). ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1579281 Title: Please update iwlwifi firmwares to include versions 17-19 Status in linux-firmware package in Ubuntu: New Bug description: Linux firmware git has these new firware revisions that are supported by the drivers shipped in Ubuntu (and it actually tries to load them): May 2 20:57:35 t460s kernel: [2.873419] Intel(R) Wireless WiFi driver for Linux May 2 20:57:35 t460s kernel: [2.873422] Copyright(c) 2003- 2015 Intel Corporation May 2 20:57:35 t460s kernel: [2.873794] iwlwifi :04:00.0: enabling device ( -> 0002) May 2 20:57:35 t460s kernel: [2.877881] iwlwifi :04:00.0: Unsupported splx structure May 2 20:57:35 t460s kernel: [2.878491] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 May 2 20:57:35 t460s kernel: [2.878504] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 May 2 20:57:35 t460s kernel: [2.878515] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 May 2 20:57:35 t460s kernel: [2.884163] iwlwifi :04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm Adding iwlwifi-8000C-19.ucode works as expected: [21431.655352] iwlwifi :04:00.0: loaded firmware version 19.313137.0 op_mode iwlmvm So, please include these new revisions in the Ubuntu package (for xenial too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1579281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
Looking at the kernel CPUFreq Governors documentation[1], It looks like powersave is actually a pretty poor default value for many applications, but especially servers. I'm not sure about low-power applications like laptops, and how power usage is affected by frequency on other architectures. Perhaps defaulting to the performance governor unless one of the more intelligent governors is available? [1]https://www.kernel.org/doc/Documentation/cpu-freq/governors.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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01%
[Kernel-packages] [Bug 1579278] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1579278 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) 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/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available |
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
| - 26.02% 0.08% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 25.94% cpu_startup_entry | - 23.65% call_cpuidle | - 23.63% cpuidle_enter | - 17.31% cpuidle_enter_state | 17.04% intel_idle | 0.04% poll_idle |+ 0.03% ktime_get | 0.02% leave_mm |+ 0.02% ret_from_intr |+ 0.00% apic_timer_interrupt | 0.00% sched_idle_set_state | 0.00% read_tsc | + 4.41% ret_from_intr | + 1.79% apic_timer_interrupt | 0.04% native_irq_return_iret | 0.02% ktime_get | 0.01% irq_entries_start | + 0.01% reschedule_interrupt | 0.01% common_interrupt | 0.01% intel_idle | 0.00% sched_idle_set_state | 0.00% do_IRQ | 0.00% restore_regs_and_iret | 0.00% native_iret | 0.00% restore_c_regs_and_iret | + 0.00% call_function_single_interrupt | + 0.00% call_function_interrupt | + 0.00% ret_from_intr |0.00% cpuidle_enter_state -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | +
[Kernel-packages] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
As Theodore Ts'o has pointed out[1]: """ ... with modern Intel processors, the ondemand CPU governor is actually counterproductive because waking up to decide whether the CPU is idle keeps it from entering the deepest sleep states, and so (somewhat counterintuitively) the performance governor will actually result in the best battery life. """ [1]https://plus.google.com/+TheodoreTso/posts/2vEekAsG2QT ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit
[Kernel-packages] [Bug 1579278] [NEW] Consider changing default CPU frequency scaling governor back to "performance"
Public bug reported: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.00% schedule | + 0.00% arch_cpu_idle_exit | 0.00% __tick_nohz_idle_enter | 0.00% irq_entries_start | 0.00% sched_clock_idle_wakeup_event | 0.00% reschedule_interrupt | + 0.00% apic_timer_interrupt |+ 0.20% start_secondary |+ 0.00% x86_64_start_kernel | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | - 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter |- 52.92% cpuidle_enter | + 31.81% cpuidle_enter_state | + 20.01% ret_from_intr | + 0.51% apic_timer_interrupt | 0.28% native_irq_return_iret | + 0.09% reschedule_interrupt | 0.05% irq_entries_start | 0.05% do_IRQ | 0.05%
[Kernel-packages] [Bug 1578721] onibi (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/onibi__4.4.0-22.39__2016-05-06_23-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579140] Re: CVE-2016-4558
** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1579140 Title: CVE-2016-4558 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: Invalid Status in linux-goldfish source package in Wily: Invalid Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Invalid Status in linux-manta source package in Wily:
[Kernel-packages] [Bug 1578721] fozzie (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/fozzie__4.4.0-22.39__2016-05-06_23-10-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578705] Re: CVE-2016-4557: use-after-free flaw via double-fdput in bpf
** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1578705 Title: CVE-2016-4557: use-after-free flaw via double-fdput in bpf Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: New Status in linux-goldfish source package in Xenial: New Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Invalid Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: New Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Released Status in linux-snapdragon source package in Xenial: Fix Released Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: New Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: New Status in linux-goldfish source package in Yakkety: New Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Invalid Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in
[Kernel-packages] [Bug 1578721] dagmar (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/dagmar__4.4.0-22.39__2016-05-06_22-57-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571020] Re: CVE-2016-3961
** 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-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1571020 Title: CVE-2016-3961 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily:
[Kernel-packages] [Bug 1566581] Re: CVE-2016-3689
** Changed in: linux-lts-trusty (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-lts-trusty (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-lts-trusty (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-lts-trusty (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-lts-wily (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-lts-wily (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-lts-wily (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-lts-wily (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-lts-wily (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-lts-quantal (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-lts-quantal (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-lts-quantal (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-lts-quantal (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-ti-omap4 (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-ti-omap4 (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-lts-raring (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-lts-raring (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-lts-raring (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-lts-raring (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-lts-raring (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-armadaxp (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-armadaxp (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-armadaxp (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-armadaxp (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-armadaxp (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-lts-xenial (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-lts-xenial (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-lts-xenial (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-lts-saucy (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-lts-saucy (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-lts-saucy (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-lts-saucy (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-manta (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-manta (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-manta (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-manta (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-manta (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-lts-vivid (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-lts-vivid (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-lts-vivid (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-lts-vivid (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-raspi2 (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-raspi2 (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Importance: Medium => Low ** Changed in: linux-raspi2 (Ubuntu Yakkety) Importance: Medium => Low ** Changed in: linux-raspi2 (Ubuntu Trusty) Importance: Medium => Low ** Changed in: linux-snapdragon (Ubuntu Precise) Importance: Medium => Low ** Changed in: linux-snapdragon (Ubuntu Wily) Importance: Medium => Low ** Changed in: linux-snapdragon
[Kernel-packages] [Bug 1561388] Re: CVE-2016-3157
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561388 Title: CVE-2016-3157 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1575260] Re: Failed to start Daemon for power management.
In addition to Max's libusbmuxd symlink in comment #3, I also had to create the following symlink: sudo ln -s /usr/lib/x86_64-linux-gnu/libplist.so.3 /usr/lib/x86_64 -linux-gnu/libplist.so.2 After this, the upower service was able to start and I regained my battery indicator and brightness controls. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575260 Title: Failed to start Daemon for power management. Status in linux package in Ubuntu: Confirmed Bug description: One of the many issue since upgrading to 16.10, I get this in my syslog : 454 Apr 26 07:57:40 mwaterm1-x250 upowerd[13918]: /usr/lib/upower/upowerd: error while loading shared libraries: libusbmuxd.so.2: cannot open shared object file: No such file or directory 455 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a 456 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: Failed to start Daemon for power management. 457 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Unit entered failed state. 458 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Failed with result 'exit-code'. 459 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: upower.service: Service hold-off time over, scheduling restart. 460 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: Stopped Daemon for power management. 461 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: upower.service: Start request repeated too quickly. 462 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: Failed to start Daemon for power management. 463 Apr 26 07:58:04 mwaterm1-x250 gnome-session[2230]: gnome-session-binary[2230]: GnomeDesktop-WARNING: Failed to acquire idle monitor object manager: Timeout was reached 464 Apr 26 07:58:04 mwaterm1-x250 gnome-session-binary[2230]: GnomeDesktop-WARNING: Failed to acquire idle monitor object manager: Timeout was reached 465 Apr 26 07:58:04 mwaterm1-x250 kernel: [27931.343128] unity-settings-[13900]: segfault at 0 ip 7f21751ade69 sp 7ffc7ad90ea0 error 4 in libupower-glib.so.3.0.1[7f217519e000+24000] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: davidmaxwaterman 2348 F pulseaudio /dev/snd/controlC0: davidmaxwaterman 2348 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 17:19:05 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f6a6d0a5-8059-4f25-9b03-f560ceb68f6d InstallationDate: Installed on 2015-05-20 (342 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20CM001QUK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) dmi.bios.date: 04/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET33W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CM001QUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CM001QUK dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1558847] Re: CVE-2016-3156
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1558847 Title: CVE-2016-3156 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1575260] Re: Failed to start Daemon for power management.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575260 Title: Failed to start Daemon for power management. Status in linux package in Ubuntu: Confirmed Bug description: One of the many issue since upgrading to 16.10, I get this in my syslog : 454 Apr 26 07:57:40 mwaterm1-x250 upowerd[13918]: /usr/lib/upower/upowerd: error while loading shared libraries: libusbmuxd.so.2: cannot open shared object file: No such file or directory 455 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a 456 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: Failed to start Daemon for power management. 457 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Unit entered failed state. 458 Apr 26 07:57:40 mwaterm1-x250 systemd[1]: upower.service: Failed with result 'exit-code'. 459 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: upower.service: Service hold-off time over, scheduling restart. 460 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: Stopped Daemon for power management. 461 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: upower.service: Start request repeated too quickly. 462 Apr 26 07:57:41 mwaterm1-x250 systemd[1]: Failed to start Daemon for power management. 463 Apr 26 07:58:04 mwaterm1-x250 gnome-session[2230]: gnome-session-binary[2230]: GnomeDesktop-WARNING: Failed to acquire idle monitor object manager: Timeout was reached 464 Apr 26 07:58:04 mwaterm1-x250 gnome-session-binary[2230]: GnomeDesktop-WARNING: Failed to acquire idle monitor object manager: Timeout was reached 465 Apr 26 07:58:04 mwaterm1-x250 kernel: [27931.343128] unity-settings-[13900]: segfault at 0 ip 7f21751ade69 sp 7ffc7ad90ea0 error 4 in libupower-glib.so.3.0.1[7f217519e000+24000] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: davidmaxwaterman 2348 F pulseaudio /dev/snd/controlC0: davidmaxwaterman 2348 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 17:19:05 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f6a6d0a5-8059-4f25-9b03-f560ceb68f6d InstallationDate: Installed on 2015-05-20 (342 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20CM001QUK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) dmi.bios.date: 04/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET33W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CM001QUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CM001QUK dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556888] Re: CVE-2016-3140
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1556888 Title: CVE-2016-3140 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source
[Kernel-packages] [Bug 1578721] fozzie (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/fozzie__4.4.0-22.39__2016-05-06_22-17-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556880] Re: CVE-2016-3138
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1556880 Title: CVE-2016-3138 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1578721] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/ms10-35-mcdivittB0-kernel__4.4.0-22.39__2016-05-06_22-46-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561414] Re: CVE-2016-2188
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561414 Title: CVE-2016-2188 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1556878] Re: CVE-2016-3137
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1556878 Title: CVE-2016-3137 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source
[Kernel-packages] [Bug 1561411] Re: CVE-2016-2186
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561411 Title: CVE-2016-2186 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1578721] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/ms10-35-mcdivittB0-kernel__4.4.0-22.39__2016-05-06_21-45-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561410] Re: CVE-2016-2185
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561410 Title: CVE-2016-2185 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1578721] onibi (amd64) - tests ran: 23, failed: 0
tests ran: 23, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/onibi__4.4.0-22.39__2016-05-06_22-26-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561409] Re: CVE-2016-2184
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561409 Title: CVE-2016-2184 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1566580] Re: CVE-2015-8839
** 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-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1566580 Title: CVE-2015-8839 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New Status
[Kernel-packages] [Bug 1578721] dagmar (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/dagmar__4.4.0-22.39__2016-05-06_22-07-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556877] Re: CVE-2016-3136
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1556877 Title: CVE-2016-3136 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source
[Kernel-packages] [Bug 1571859] Re: Thunderbolt 3 USB-C Port not "hotpluggable"
*** This bug is a duplicate of bug 1577898 *** https://bugs.launchpad.net/bugs/1577898 ** This bug has been marked a duplicate of bug 1577898 thunderbolt hotplug is broken -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571859 Title: Thunderbolt 3 USB-C Port not "hotpluggable" Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell Precision 5510 with 16.04 Beta 2. The Thunderbolt3 port will provide power to devices, but will not recognize them when plugged in after boot. If a Thunderbolt USB-C to Ethernet adapter is plugged in on boot, the device is recognized and usable as an ethernet connection. However if it is removed and plugged back in, it is not recognized when reconnected. I also have a Nexus 6P Android phone with USB-C. The laptop will provide power to the phone but will not recognize it as a connected device, even when attached at boot. This may be a related issue or something else entirely, but wanted to pass along none the less. I do not have any other USB-C/Thunderbolt adapters to test with at this time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kgochenour 3218 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 18 17:28:29 2016 HibernationDevice: RESUME=UUID=dbb01b4f-200c-47f8-aba9-c12e41ee127d InstallationDate: Installed on 2016-04-10 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] onibi (i386) - tests ran: 13, failed: 0
tests ran: 13, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/onibi__4.4.0-22.39__2016-05-06_20-45-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] fozzie (amd64) - tests ran: 23, failed: 0
tests ran: 23, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/fozzie__4.4.0-22.39__2016-05-06_21-43-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] dagmar (amd64) - tests ran: 23, failed: 0
tests ran: 23, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/dagmar__4.4.0-22.39__2016-05-06_21-34-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] onza (i386) - tests ran: 13, failed: 1
tests ran: 13, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-22.39/onza__4.4.0-22.39__2016-05-06_20-41-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] fozzie (i386) - tests ran: 13, failed: 0
tests ran: 13, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/fozzie__4.4.0-22.39__2016-05-06_20-17-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] rukbah (amd64) - tests ran: 83, failed: 0
tests ran: 83, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/rukbah__4.4.0-22.39__2016-05-06_19-07-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 23, failed: 1
tests ran: 23, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-22.39/ms10-35-mcdivittB0-kernel__4.4.0-22.39__2016-05-06_21-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1578721] dagmar (i386) - tests ran: 13, failed: 0
tests ran: 13, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.39/dagmar__4.4.0-22.39__2016-05-06_20-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1397880] Re: [v4.6-rc1 Regression] x86/topology: Create logical package id
On 05/06/2016 04:51 PM, Joseph Salisbury wrote: > Thomas' patch does resolve the bug. The cpuid info can be seen here: > https://launchpadlibrarian.net/258234267/cpuid_full.txt Any chance you could post it raw (cpuid -1 -r)? Thanks. -boris -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1397880 Title: [Feature] Memory Bandwidth Monitoring Status in intel: New Status in linux package in Ubuntu: Fix Released Status in xen package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in xen source package in Xenial: Fix Released Bug description: Memory Bandwidth Monitoring (MBM) is a CPU feature included in the family of Platform QoS features. It is used to track memory bandwidth usage for a specific task, or group of tasks. Memory Bandwidth Monitoring is an extension of the existing Cache QoS Monitoring (CQM) feature found in Haswell server. The mechanism used is the same, where tasks are associated with an Resource Monitoring ID (RMID), which the CPU uses to track the bandwidth usage. Upstream status: Kernel - 4.6 Xen - target 4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1397880/+subscriptions -- Mailing list: https://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 1578929] Re: UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1
I downloaded and installed most of the Xenial Distros on the 22nd 2 days after GA. I just downloaded Ubuntu Desktop 64 from the URL you provided and it does not have the problem. On Fri, May 6, 2016 at 8:00 AM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Is this only happening with the 16.10 daily images? Can you see if it > also happens with the Xenial image on the same setup? It can be > downloaded from: > > http://releases.ubuntu.com/xenial/ > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Tags added: kernel-da-key > > ** Also affects: linux (Ubuntu Yakkety) >Importance: Medium >Status: Confirmed > > ** Changed in: linux (Ubuntu Yakkety) >Importance: Medium => High > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1578929 > > Title: > UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1 > > Status in linux package in Ubuntu: > Confirmed > Status in linux source package in Yakkety: > Confirmed > > Bug description: > Hard Failure with this message during Choosing Keyboard "Continue". > > Must cancel installation. > > Received additional error > The Install encountered an error copying files to hard disk. > > [Errno 2] No such file or directory: '/target/usr/lib/x86_64-linux- > gnu/dri/vdpau_drv_video.so' > > Rest of message directs you to possible faulty hard disk. > > I am running under Virtualbox on solid hardware base so I strongly > doubt hardware is a problem. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37 > ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 > Uname: Linux 4.4.0-21-lowlatency x86_64 > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: ubuntu-studio 1887 F pulseaudio > CasperVersion: 1.376 > CurrentDesktop: XFCE > Date: Fri May 6 01:05:34 2016 > IwConfig: >enp0s3no wireless extensions. > >lono wireless extensions. > LiveMediaBuild: Ubuntu-Studio 16.10 "Yakkety Yak" - Alpha amd64 > (20160505) > Lsusb: >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > MachineType: innotek GmbH VirtualBox > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: > > ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed boot=casper > only-ubiquity initrd=/casper/initrd.lz quiet splash --- > RelatedPackageVersions: >linux-restricted-modules-4.4.0-21-lowlatency N/A >linux-backports-modules-4.4.0-21-lowlatency N/A >linux-firmware 1.157 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/01/2006 > dmi.bios.vendor: innotek GmbH > dmi.bios.version: VirtualBox > dmi.board.name: VirtualBox > dmi.board.vendor: Oracle Corporation > dmi.board.version: 1.2 > dmi.chassis.type: 1 > dmi.chassis.vendor: Oracle Corporation > dmi.modalias: > dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: > dmi.product.name: VirtualBox > dmi.product.version: 1.2 > dmi.sys.vendor: innotek GmbH > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578929/+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/1578929 Title: UStudio 16.10 Daily Installation Fails ubi-console-setup exit code 1 Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: Hard Failure with this message during Choosing Keyboard "Continue". Must cancel installation. Received additional error The Install encountered an error copying files to hard disk. [Errno 2] No such file or directory: '/target/usr/lib/x86_64-linux- gnu/dri/vdpau_drv_video.so' Rest of message directs you to possible faulty hard disk. I am running under Virtualbox on solid hardware base so I strongly doubt hardware is a problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.4.0-21-lowlatency 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-studio 1887 F pulseaudio CasperVersion: 1.376 CurrentDesktop: XFCE Date: Fri May 6 01:05:34 2016 IwConfig: enp0s3no wireless extensions. lono
[Kernel-packages] [Bug 1568523] Re: CVE-2016-3672
This bug was fixed in the package linux-snapdragon - 4.4.0-1013.14 --- linux-snapdragon (4.4.0-1013.14) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1578759 * Rebase to Ubuntu-4.4.0-22.39 -- Kamal MostafaThu, 05 May 2016 11:17:11 -0700 ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1568523 Title: CVE-2016-3672 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1567191] Re: CVE-2016-3951
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1567191] Re: CVE-2016-3951
This bug was fixed in the package linux-snapdragon - 4.4.0-1013.14 --- linux-snapdragon (4.4.0-1013.14) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1578759 * Rebase to Ubuntu-4.4.0-22.39 -- Kamal MostafaThu, 05 May 2016 11:17:11 -0700 ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1567191 Title: CVE-2016-3951 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1567191] Re: CVE-2016-3951
This bug was fixed in the package linux-raspi2 - 4.4.0-1010.12 --- linux-raspi2 (4.4.0-1010.12) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1578741 * Rebase against Ubuntu-4.4.0-22.39 -- Kamal MostafaThu, 05 May 2016 10:19:22 -0700 ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1567191 Title: CVE-2016-3951 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic
[Kernel-packages] [Bug 1568523] Re: CVE-2016-3672
This bug was fixed in the package linux-raspi2 - 4.4.0-1010.12 --- linux-raspi2 (4.4.0-1010.12) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1578741 * Rebase against Ubuntu-4.4.0-22.39 -- Kamal MostafaThu, 05 May 2016 10:19:22 -0700 ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1568523 Title: CVE-2016-3672 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1572666] Re: CVE-2016-3955
This bug was fixed in the package linux-raspi2 - 4.4.0-1010.12 --- linux-raspi2 (4.4.0-1010.12) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1578741 * Rebase against Ubuntu-4.4.0-22.39 -- Kamal MostafaThu, 05 May 2016 10:19:22 -0700 ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1572666 Title: CVE-2016-3955 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1578721] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 13, failed: 3
tests ran: 13, failed: 3; http://kernel.ubuntu.com/testing/4.4.0-22.39/ms10-35-mcdivittB0-kernel__4.4.0-22.39__2016-05-06_18-56-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/1578721 Title: linux: 4.4.0-22.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-22.39 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1578721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572666] Re: CVE-2016-3955
This bug was fixed in the package linux-snapdragon - 4.4.0-1013.14 --- linux-snapdragon (4.4.0-1013.14) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1578759 * Rebase to Ubuntu-4.4.0-22.39 -- Kamal MostafaThu, 05 May 2016 11:17:11 -0700 ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1572666 Title: CVE-2016-3955 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in
[Kernel-packages] [Bug 1542564] Re: Atheros AR9462 Bluetooth cannot detect other devices
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1569924] Re: linux: Add UEFI keyring for externally signed modules
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1546694] Re: Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565)
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1552925] Re: 13d3:3472 bluetooth not working, 4.2 low latency kernel 14.04.1 on asus ROG gl552jx
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1572291] Re: s390/pci: add extra padding to function measurement block
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1572722] Re: Xenial update to v4.4.7 stable release
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1542944] Re: QCA9565 / AR9565 bluetooth not work
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1573034] Re: Xenial update to v4.4.8 stable release
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards
Yes I WladyX I get freezes, but IIRC this is always how it was on Linux since I use it. :) Are the freezes happening to you at the same same time the 5 key is repeated? Joseph Salisbury, yes I can try the latest upstream kernel. Will let you know the 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/1579190 Title: Key 5 automatically pressed on some Logitech wireless keyboards Status in linux package in Ubuntu: Incomplete Bug description: I have a K520 Logitech keyboard and sometimes something starts to keep pressing key 5. It mostly happens when I leave the computer alone for some time, but sometimes also just during regular usage. It seems that this is a Linux specific issue as no one is complaining about this issue under Windows, but a couple of people are complaining for different versions of Ubuntu. It is always 5 and WladyXX3740 claims on the Logitech forum that: "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably kernel related." Here is where most of the people are complaining: https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639 I discovered that this is related to my Logitech keyboard by running this command: xinput test-xi2 --root Here is the device list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ Logitech M310/M310t id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ DELL Wireless hotkeys id=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] And some extract from the output when this happens: EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 12 (PropertyEvent) property: 308 'Synaptics Off' changed: modified EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 EVENT type 2 (KeyPress) device: 10 (10) detail: 14 flags: repeat root: 449.00/427.00 event: 449.00/427.00 buttons: modifiers: locked 0x10 latched 0 base 0 effective: 0x10 group: locked 0 latched 0 base 0 effective: 0 valuators: windows: root 0xf6 event 0xf6 child 0x36000f8 ...
[Kernel-packages] [Bug 1572666] Re: CVE-2016-3955
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1568523] Re: CVE-2016-3672
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -
[Kernel-packages] [Bug 1573231] Re: [v4.6-rc1 Regression] x86/topology: Create logical package id
On 05/06/2016 04:46 PM, Boris Ostrovsky wrote: > On 05/06/2016 03:38 PM, Joseph Salisbury wrote: >> On 05/06/2016 03:13 PM, Boris Ostrovsky wrote: >>> On 05/06/2016 02:48 PM, Thomas Gleixner wrote: Yuck. That dies with a divide error. And that looks like XEN is supplying crap data in the CPUID. >>> Joe, do you have >>> >>> ed6069b xen/apic: Provide Xen-specific version of cpu_present_to_apicid >>> APIC op >>> >>> -boris >> Yes the commit is in the 4.4 based Ubuntu kernel. This bug also happens >> with the vanilla 4.6-rc5 kernel, which also has that commit. > > Can you post guest's cpuid -1 -r ? (I guess after you verify Thomas' patch) > > Thanks. > -boris > > > Thomas' patch does resolve the bug. The cpuid info can be seen here: https://launchpadlibrarian.net/258234267/cpuid_full.txt Thanks, Joe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1573231 Title: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do- release-upgrade -d Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xefff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at [880fbba0] [0.00] Scanning 1 areas for low memory corruption [0.00] RAMDISK: [mem 0x3407e000-0x36036fff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: FACS 0xFC0035A0 40 [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM HVML ) [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM INTL 20090123) [0.00]
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
This bug was fixed in the package linux - 4.4.0-22.38 --- linux (4.4.0-22.38) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1573817 * autoreconstruct: need to also generate extend-diff-ignore options for links (LP: #1574362) - [Packaging] autoreconstruct -- generate extend-diff-ignore for links * tipc: missing linearization of sk_buff (LP: #1567064) - tipc: move linearization of buffers to generic code * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124) - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse vmbus_mmio_allocate() - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in private resource tree - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO range * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156) - ubuntu: vbox -- update to 5.0.18-dfsg-2build1 * CONFIG_AUFS_XATTR is not set (LP: #1557776) - [Config] CONFIG_AUFS_XATTR=y * CVE-2016-3672 (LP: #1568523) - x86/mm/32: Enable full randomization on i386 and X86_32 * CVE-2016-3955 (LP: #1572666) - USB: usbip: fix potential out-of-bounds write * Xenial update to v4.4.8 stable release (LP: #1573034) - hwmon: (max) Return -ENODEV from max_read_channel if not instantiated - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument - parisc: Avoid function pointers for kernel exception routines - parisc: Fix kernel crash with reversed copy_from_user() - parisc: Unbreak handling exceptions from kernel modules - ALSA: timer: Use mod_timer() for rearming the system timer - ALSA: hda - Asus N750JV external subwoofer fixup - ALSA: hda - Fix white noise on Asus N750JV headphone - ALSA: hda - Apply fix for white noise on Asus N550JV, too - mm: fix invalid node in alloc_migrate_target() - powerpc/mm: Fixup preempt underflow with huge pages - libnvdimm: fix smart data retrieval - libnvdimm, pfn: fix uuid validation - compiler-gcc: disable -ftracer for __noclone functions - arm64: opcodes.h: Add arm big-endian config options before including arm header - drm/dp: move hw_mutex up the call stack - drm/udl: Use unlocked gem unreferencing - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 - drm/radeon: add another R7 370 quirk - drm/radeon: add a dpm quirk for all R7 370 parts - drm/amdgpu/gmc: move vram type fetching into sw_init - drm/amdgpu/gmc: use proper register for vram type on Fiji - xen/events: Mask a moving irq - tcp: convert cached rtt from usec to jiffies when feeding initial rto - tunnel: Clear IPCB(skb)->opt before dst_link_failure called - net: jme: fix suspend/resume on JMC260 - net: vrf: Remove direct access to skb->data - net: qca_spi: Don't clear IFF_BROADCAST - net: qca_spi: clear IFF_TX_SKB_SHARING - net: fix bridge multicast packet checksum validation - sctp: lack the check for ports in sctp_v6_cmp_addr - mld, igmp: Fix reserved tailroom calculation - tipc: Revert "tipc: use existing sk_write_queue for outgoing packet chain" - qmi_wwan: add Sierra Wireless EM74xx device ID - ipv6: re-enable fragment header matching in ipv6_find_hdr - vxlan: fix missing options_len update on RX with collect metadata - cdc_ncm: toggle altsetting to force reset before setup - udp6: fix UDP/IPv6 encap resubmit path - tcp: fix tcpi_segs_in after connection establishment - ppp: release rtnl mutex when interface creation fails - net: validate variable length ll headers - ax25: add link layer header validation function - packet: validate variable length ll headers - bpf: avoid copying junk bytes in bpf_get_current_comm() - sh_eth: fix NULL pointer dereference in sh_eth_ring_format() - sh_eth: advance 'rxdesc' later in sh_eth_ring_format() - qlcnic: Remove unnecessary usage of atomic_t - qlcnic: Fix mailbox completion handling during spurious interrupt - macvtap: always pass ethernet header in linear - mlxsw: spectrum: Check requested ageing time is valid - rocker: set FDB cleanup timer according to lowest ageing time - bridge: allow zero ageing time - ipv4: Don't do expensive useless work during inetdev destroy. - net: Fix use after free in the recvmmsg exit path - mlx4: add missing braces in verify_qp_parameters - farsync: fix off-by-one bug in fst_add_one - ath9k: fix buffer overrun for ar9287 - ppp: ensure file->private_data can't be overridden - tcp/dccp: remove obsolete WARN_ON() in icmp handlers - qlge: Fix receive packets drop. - net: bcmgenet: fix dma api length mismatch -