[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads
patch for trusty and utopic has been submitted to kernel-team@. vivid has that commit already. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456881 Title: Some touchpads' right button doesn't work under I2C mode, need support of clickpads Status in HWE Next Project: New Status in linux package in Ubuntu: In Progress Bug description: We need to add this support, otherwise some touchpads' right button doesn't work under I2C mode. commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch) HID: multitouch: add support of clickpads Touchpads that have only one button are called clickpads and should be advertised as such by the kernel. Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com Tested-by: Jason Ekstrand ja...@jlekstrand.net Signed-off-by: Jiri Kosina jkos...@suse.cz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452830] [NEW] Keyboard and mouse not working after update to 15.04
You have been subscribed to a public bug: After turning on the system, mouse pointer is not visible and first key press on keyboard is ignored. When I press mouse button (left or right), mouse pointer appears and I can control it, but when I leave it for few seconds, it disappears again. As for the keyboard, the first key press is ignored (e.g. when I try to type zone, only one is visible on the screen because the first key is ignored) - this behavior repeats itself after few seconds of not pressing any keys. My keyboard has backlight option and when I turn it on, the light flickers and disappears when the keyboard gets disconnected. Disconnecting and connecting again mouse and keyboard makes the issue disappear - from that moment on, both mouse and keyboard work like a charm (until reboot). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: keyboard mouse -- Keyboard and mouse not working after update to 15.04 https://bugs.launchpad.net/bugs/1452830 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452830] Re: Keyboard and mouse not working after update to 15.04
** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452830 Title: Keyboard and mouse not working after update to 15.04 Status in linux package in Ubuntu: New Bug description: After turning on the system, mouse pointer is not visible and first key press on keyboard is ignored. When I press mouse button (left or right), mouse pointer appears and I can control it, but when I leave it for few seconds, it disappears again. As for the keyboard, the first key press is ignored (e.g. when I try to type zone, only one is visible on the screen because the first key is ignored) - this behavior repeats itself after few seconds of not pressing any keys. My keyboard has backlight option and when I turn it on, the light flickers and disappears when the keyboard gets disconnected. Disconnecting and connecting again mouse and keyboard makes the issue disappear - from that moment on, both mouse and keyboard work like a charm (until reboot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads
** Changed in: hwe-next Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456881 Title: Some touchpads' right button doesn't work under I2C mode, need support of clickpads Status in HWE Next Project: In Progress Status in linux package in Ubuntu: In Progress Bug description: We need to add this support, otherwise some touchpads' right button doesn't work under I2C mode. commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch) HID: multitouch: add support of clickpads Touchpads that have only one button are called clickpads and should be advertised as such by the kernel. Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com Tested-by: Jason Ekstrand ja...@jlekstrand.net Signed-off-by: Jiri Kosina jkos...@suse.cz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456285] Re: Intel 7260 problems on Thinkpad T440s
I'm not sure if this makes any sense but when I booted with the v4.1-rc3-unstable kernel it was as if the wireless card just wasn't detected at all. No sign of it in the network manager and no option to enable wi-fi. There were some messages about iwlwifi firmware that appeared very briefly during booting, but too quickly for me to read. I could try again if that would be useful. ** Tags removed: kernel-unable-to-test-upstream ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456285 Title: Intel 7260 problems on Thinkpad T440s Status in linux package in Ubuntu: Confirmed Bug description: Very intermittent and inconsistent wireless connections. Occasionally the indicator will show that the connection has been lost, but more often it seems that the indicator just shows low signal strength -- as it generally does even when the connection is working well. I'm pretty sure this is not an access-point problem because we have other devices using the same network without any problem. Here's some of the additional information that has been requested in other discussions of similar problems, although I don't fully understand what all these results mean. I have these three firmware files in /lib/firmware: [code] -rw-r--r-- 1 root root 683236 Nov 24 09:42 iwlwifi-7260-7.ucode -rw-r--r-- 1 root root 679780 Dec 1 09:16 iwlwifi-7260-8.ucode -rw-r--r-- 1 root root 680508 Dec 1 14:45 iwlwifi-7260-9.ucode [/code] dmesg | grep iwlwifi | grep firmware [code] [ 11.974201] iwlwifi :03:00.0: loaded firmware version 22.24.8.0 op_mode iwlmvm [/code] lspci -nn | grep 0280 [code] 03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b2] (rev 83) [/code] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-52-generic 3.13.0-52.86 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: timh 2011 F pulseaudio timh 2801 F pulseaudio /dev/snd/controlC0: timh 2011 F pulseaudio timh 2801 F pulseaudio CurrentDesktop: XFCE Date: Mon May 18 12:05:48 2015 HibernationDevice: RESUME=UUID=799c429f-edb4-438c-bbc7-386342199d23 InstallationDate: Installed on 2014-03-12 (432 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MachineType: LENOVO 20ARCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-52-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-52-generic N/A linux-backports-modules-3.13.0-52-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2015-03-16 (63 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20ARCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20ARCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455852] Re: 15.04 will not boot on MacBook 2, 1
Agree'd. With this patch, screen turns off (not only black). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1455852 Title: 15.04 will not boot on MacBook 2,1 Status in linux package in Ubuntu: Incomplete Bug description: see: http://ubuntuforums.org/showthread.php?t=2274999p=13286624#post13286624 Lubuntu 15.04 on refit grub dual boot macbook 2,1 linux-image-3.16 will boot, though sometimes hangs but, reboot will work eventually. With linux-image-3.19 never, ? is the GPU hang reported in kern.log relevant here? i915 problem? see kern.log snippet attached see error attached from GPU crash dump saved to /sys/class/drm/card0/error This seems to be a BUG as suggested by the log: ... Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel from: /sys/class/drm/card0/error: GPU HANG: ecode -1:0x, reason: Command parser error, iir 0x8000, action: continue Time: 1431810790 s 799079 us Kernel: 3.16.0-25-generic Reset count: 0 Suspend count: 0 PCI ID: 0x27a2 EIR: 0x0010 IER: 0x00028053 PGTBL_ER: 0x0102 FORCEWAKE: 0x DERRMR: 0x CCID: 0x Missed interrupts: 0x fence[0] = fence[1] = fence[2] = fence[3] = fence[4] = fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = INSTDONE_0: 0x7fc0 INSTDONE_1: 0x INSTDONE_2: 0x INSTDONE_3: 0x render command stream: bsd command stream: blt command stream: vebox command stream: bsd2 command stream: Active [0]: Pinned [0]: Num Pipes: 2 Pipe [0]: Power: on SRC: 027f01df STAT: 9a03 Plane [0]: CNTR: STRIDE: SIZE: POS: ADDR: Cursor [0]: CNTR: POS: BASE: Pipe [1]: Power: on SRC: 03ff02ff STAT: 1202 Plane [1]: CNTR: 9900 STRIDE: 1000 SIZE: 02ff03ff POS: ADDR: Cursor [1]: CNTR: POS: BASE: CPU transcoder: A Power: on CONF: HTOTAL: 031f027f HBLANK: 03170287 HSYNC: 02ef028f VTOTAL: 020c01df VBLANK: 020401e7 VSYNC: 01eb01e9 CPU transcoder: B Power: on CONF: 8000 HTOTAL: 059f04ff HBLANK: 059f04ff HSYNC: 054f052f VTOTAL: 0336031f VBLANK: 0336031f VSYNC: 03280322 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 1188 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=921b491d-af65-4a9e-a51d-47d3c6dcbac2 InstallationDate: Installed on 2012-10-27 (932 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121017.1) MachineType: Apple Inc. MacBook2,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=37fab4ad-d609-4d2a-ab4b-5c1a41d2f9fc ro init=/bin/systemd ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.143 Tags: vivid UdevLog: Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-26 (20 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452830] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1452830 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/1452830 Title: Keyboard and mouse not working after update to 15.04 Status in linux package in Ubuntu: Incomplete Bug description: After turning on the system, mouse pointer is not visible and first key press on keyboard is ignored. When I press mouse button (left or right), mouse pointer appears and I can control it, but when I leave it for few seconds, it disappears again. As for the keyboard, the first key press is ignored (e.g. when I try to type zone, only one is visible on the screen because the first key is ignored) - this behavior repeats itself after few seconds of not pressing any keys. My keyboard has backlight option and when I turn it on, the light flickers and disappears when the keyboard gets disconnected. Disconnecting and connecting again mouse and keyboard makes the issue disappear - from that moment on, both mouse and keyboard work like a charm (until reboot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1453593] Re: [gm45] 3.19.0-17 freeze
kernel 3.19.0-18: works for me with dell e6500 under 15.04-lubuntu (i386 architecture) (while kernel 3.19.0-17 was not working). Startup time is 4.9s (kernel), similar to other recent kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453593 Title: [gm45] 3.19.0-17 freeze Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Bug description: boot with 3.19.0-17 freezes at very early stage, way before the appearance of login screen. no such problems with kernel 3.19.0-16. Tested upstream kernels 4.0.0-1, 4.01, 4.0.2 and 4.1-rc2: all of them boot normally. No problems to boot with 3.19.0-17 in a lubuntu15.04 virtual machine under virtualbox (running on the same hardware platform). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: volker 2576 F pulseaudio CurrentDesktop: LXDE Date: Sun May 10 21:09:41 2015 HibernationDevice: RESUME=UUID=56d8d5bd-f32d-4192-a0d4-2395d9df1637 InstallationDate: Installed on 2014-02-12 (451 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Dell Inc. Latitude E6500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=6ff58f38-956b-49de-99d4-01dfc84b96ad ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NY667 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/18/2008:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1384597] Re: [drm/i915] stuck on render ring
Someone marked this as a duplicate of #1274779 but I do not agree. This one is about a kernel fix (which only needs to be backported), whereas the other issue affects the xorg driver. The problem described here is still valid for me on Ubuntu 14.04. Can anyone please backport the fix from above? ** This bug is no longer a duplicate of bug 1274779 [ivb] hang on pageflip (IPEHR: 0x0a01 or 0x0a080001 depending on pipe) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384597 Title: [drm/i915] stuck on render ring Status in linux package in Ubuntu: Incomplete Bug description: Chrome hangs with a stuck on render ring message on Ubuntu 14.04, 3.13.0-37-generic This bug has been fixed upstream: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=77104 dmesg: [21103.988448] [drm] Module unloaded [21103.992678] bbswitch: disabling discrete graphics [21103.992710] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) [21104.005522] pci :01:00.0: Refused to change power state, currently in D0 [21164.507889] bbswitch: enabling discrete graphics [21165.039148] [drm] Initialized nvidia-drm 0.0.0 20130102 for :01:00.0 on minor 1 [21165.039158] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 [21165.162607] vgaarb: this pci device is not a vga device [21165.163252] nvidia :01:00.0: irq 50 for MSI/MSI-X [21165.169122] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) [21166.762394] vgaarb: this pci device is not a vga device [21167.525348] [drm] Module unloaded [21167.530952] bbswitch: disabling discrete graphics [21167.530968] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) [21167.545277] pci :01:00.0: Refused to change power state, currently in D0 [21172.553983] bbswitch: enabling discrete graphics [21173.008283] [drm] Initialized nvidia-drm 0.0.0 20130102 for :01:00.0 on minor 1 [21173.008289] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 [21173.027763] vgaarb: this pci device is not a vga device [21173.028502] nvidia :01:00.0: irq 50 for MSI/MSI-X [21173.034301] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) [21173.975886] vgaarb: this pci device is not a vga device [26686.550084] [drm] stuck on render ring [26686.550091] [drm] GPU crash dump saved to /sys/class/drm/card0/error [26686.550092] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [26686.550094] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel [26686.550095] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [26686.550096] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Details of my system: $ uname -a Linux fraptop 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -c video *-display description: 3D controller product: GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:50 memory:d000-d0ff memory:a000-afff memory:b000-b1ff ioport:3000(size=128) memory:b200-b207 *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:48 memory:d100-d13f memory:c000-cfff ioport:4000(size=64) $ modinfo i915 filename: /lib/modules/3.13.0-37-generic/kernel/drivers/gpu/drm/i915/i915.ko license:GPL and additional rights description:Intel Graphics author: Tungsten Graphics, Inc. license:GPL and additional rights srcversion: 594AF6054E9069A37423B0F intree: Y vermagic: 3.13.0-37-generic SMP mod_unload modversions $ lsmod | grep nvidia nvidia 10675249 27 drm 303102 7
[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads
It seems the following commit in vivid is also needed for the better support for trusty and utopic. Author: Seth Forshee seth.fors...@canonical.com AuthorDate: Fri Mar 20 11:06:52 2015 -0500 Commit: Andy Whitcroft a...@canonical.com CommitDate: Fri Mar 27 10:44:38 2015 + HID: multitouch: Add support for button type usage According to [1], Windows Precision Touchpad devices must supply a button type usage in the device capabilities feature report. A value of 0 indicates that the device contains a depressible button (i.e. it's a click-pad) whereas a value of 1 indicates a non-depressible button. Add support for this usage and set INPUT_PROP_BUTTONPAD on the touchpad input device whenever a depressible button is present. [1] https://msdn.microsoft.com/en- us/library/windows/hardware/dn467314(v=vs.85).aspx Signed-off-by: Seth Forshee seth.fors...@canonical.com Reviewed-by: Benjamin Tissoires benjamin.tissoi...@redhat.com Signed-off-by: Jiri Kosina jkos...@suse.cz (cherry picked from commit 2c6e0277e1eab3df5db81c59e408b7b1c14b1b72 git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git) Acked-by: Stefan Bader stefan.ba...@canonical.com Acked-by: Chris J Arges chris.j.ar...@canonical.com Signed-off-by: Andy Whitcroft a...@canonical.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456881 Title: Some touchpads' right button doesn't work under I2C mode, need support of clickpads Status in HWE Next Project: In Progress Status in linux package in Ubuntu: In Progress Bug description: We need to add this support, otherwise some touchpads' right button doesn't work under I2C mode. commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch) HID: multitouch: add support of clickpads Touchpads that have only one button are called clickpads and should be advertised as such by the kernel. Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com Tested-by: Jason Ekstrand ja...@jlekstrand.net Signed-off-by: Jiri Kosina jkos...@suse.cz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
** Changed in: hwe-next Assignee: Adam Lee (adam8157) = (unassigned) ** Changed in: hwe-next Assignee: (unassigned) = Keng-Yu Lin (lexical) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1454450 Title: Bluetooth mouse laggy and erratic Status in HWE Next Project: Triaged Status in bluez package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth] [ 5579.876261] [c0e09561] hci_dev_do_open+0xe1/0xa90 [bluetooth] [ 5579.876266] [c0e0a6f0]
[Kernel-packages] [Bug 1453543] Re: totem player crashes kernel
I used to use the official supported LTS Ubuntu Trusty 3.13 kernel line. With current updates. I didn't noticed which subversion started to affect kernel panic after Totem player. May be several months. I tried to stress several times some kernels by Totem Player (play, seek, switch playlist...): 4.1.0-040100rc4-generic OK, never crashed. 3.16.0-pf4 my own customized with some patches. OK, never crashed. 3.16.0-37-generic Utopic actual supported by Trusty. KERNEL PANIC. 3.13.0-52-generic Trusty actual. KERNEL PANIC. 3.16.0-rc3-vanilla KERNEL PANIC. A week of testing my own custom build 3.16. Kernel panic never occurred yet. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453543 Title: totem player crashes kernel Status in linux package in Ubuntu: Confirmed Bug description: Very often Totem player crashes and results a black screen kernel panic. Other players work fine with any media data. ProblemType: Crash Architecture: x86_64 Description: Ubuntu 14.04.2 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455852] Re: 15.04 will not boot on MacBook 2, 1
** Bug watch added: Linux Kernel Bug Tracker #60770 http://bugzilla.kernel.org/show_bug.cgi?id=60770 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1455852 Title: 15.04 will not boot on MacBook 2,1 Status in linux package in Ubuntu: Incomplete Bug description: see: http://ubuntuforums.org/showthread.php?t=2274999p=13286624#post13286624 Lubuntu 15.04 on refit grub dual boot macbook 2,1 linux-image-3.16 will boot, though sometimes hangs but, reboot will work eventually. With linux-image-3.19 never, ? is the GPU hang reported in kern.log relevant here? i915 problem? see kern.log snippet attached see error attached from GPU crash dump saved to /sys/class/drm/card0/error This seems to be a BUG as suggested by the log: ... Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel from: /sys/class/drm/card0/error: GPU HANG: ecode -1:0x, reason: Command parser error, iir 0x8000, action: continue Time: 1431810790 s 799079 us Kernel: 3.16.0-25-generic Reset count: 0 Suspend count: 0 PCI ID: 0x27a2 EIR: 0x0010 IER: 0x00028053 PGTBL_ER: 0x0102 FORCEWAKE: 0x DERRMR: 0x CCID: 0x Missed interrupts: 0x fence[0] = fence[1] = fence[2] = fence[3] = fence[4] = fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = INSTDONE_0: 0x7fc0 INSTDONE_1: 0x INSTDONE_2: 0x INSTDONE_3: 0x render command stream: bsd command stream: blt command stream: vebox command stream: bsd2 command stream: Active [0]: Pinned [0]: Num Pipes: 2 Pipe [0]: Power: on SRC: 027f01df STAT: 9a03 Plane [0]: CNTR: STRIDE: SIZE: POS: ADDR: Cursor [0]: CNTR: POS: BASE: Pipe [1]: Power: on SRC: 03ff02ff STAT: 1202 Plane [1]: CNTR: 9900 STRIDE: 1000 SIZE: 02ff03ff POS: ADDR: Cursor [1]: CNTR: POS: BASE: CPU transcoder: A Power: on CONF: HTOTAL: 031f027f HBLANK: 03170287 HSYNC: 02ef028f VTOTAL: 020c01df VBLANK: 020401e7 VSYNC: 01eb01e9 CPU transcoder: B Power: on CONF: 8000 HTOTAL: 059f04ff HBLANK: 059f04ff HSYNC: 054f052f VTOTAL: 0336031f VBLANK: 0336031f VSYNC: 03280322 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 1188 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=921b491d-af65-4a9e-a51d-47d3c6dcbac2 InstallationDate: Installed on 2012-10-27 (932 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121017.1) MachineType: Apple Inc. MacBook2,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=37fab4ad-d609-4d2a-ab4b-5c1a41d2f9fc ro init=/bin/systemd ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.143 Tags: vivid UdevLog: Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-26 (20 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456952] [NEW] support the slub_debug boot option on specific object size
Public bug reported: The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s-name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s-flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: sts 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/1456952 Title: support the slub_debug boot option on specific object size Status in linux package in Ubuntu: New Bug description: The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s-name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s-flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456952] Re: support the slub_debug boot option on specific object size
** Description changed: + [Impact] + + slub_debug cannot work for specific kmem_cache size. + + e. g. slub_debug=PU,kmalloc-1024 + + The slub_debug is used to enable the debugging of use-after-free, poison + overwritten, double free. And it also increases the up time of the server + when the above mentioned errors happen instead of crashing immediately. + + However, currently, there exists bug that the slub_debug cannot be applied + for the specific object size. This is not helpful to enable the whole + system slub_debug because the performance loss will be up to 20%~30% + according to the customer's measurement. The patch here to limit the + slub_debug only on the specific object size to alleviate the performance + loss. + + [Fix] + The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s-name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s-flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. + + [Test case] ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Gavin Guo (mimi0213kimo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456952 Title: support the slub_debug boot option on specific object size Status in linux package in Ubuntu: Incomplete Bug description: [Impact] slub_debug cannot work for specific kmem_cache size. e. g. slub_debug=PU,kmalloc-1024 The slub_debug is used to enable the debugging of use-after-free, poison overwritten, double free. And it also increases the up time of the server when the above mentioned errors happen instead of crashing immediately. However, currently, there exists bug that the slub_debug cannot be applied for the specific object size. This is not helpful to enable the whole system slub_debug because the performance loss will be up to 20%~30% according to the customer's measurement. The patch here to limit the slub_debug only on the specific object size to alleviate the performance loss. [Fix] The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s-name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s-flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. [Test case] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456837] Re: USB drive errors with kernel version 3.13.0-35 and above
Gary Dalmadge, thank you for reporting this and helping make Ubuntu better. Just to advise, there is a de-emphasis of support for 32-bit operating systems upstream. Hence, is this reproducible in an x64 environment via http://cdimage.ubuntu.com/daily-live/current/vivid- desktop-amd64.iso ? ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.0-rc3 needs-bisect regression-release ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456837 Title: USB drive errors with kernel version 3.13.0-35 and above Status in linux package in Ubuntu: Incomplete Bug description: I am seeing various USB drive errors while trying to use the drives. For instance, I am unable to successfully create a new file system on the drives. One example is parted which returns the following error: Error fsyncing/closing /dev/sdc: Remote I/O error dmesg shows the following error in this case: end_request: critical target error, dev sdc, sector 0 The errors appear with different brands and types of USB drives. I have tested the drives on other systems and they are okay. Earlier versions of Ubuntu (prior to 14.04) do not show these errors. I am running the i386 version. I have tried different versions of the kernel. It seems to have appeared in the 3.13.0-35 kernel. I do not see it while using the 3.13.0-34 kernel, but see it in newer kernels. It is present in both the generic and low latency versions of the kernel. I have tried the Utopic kernels 3.16.0.37.29 with the same results. I have also tried the upstream kernels 4.0.3-040003, and 4.1.0-040100rc3 and still see the problem. I have multiple systems, and am only seeing this on systems with AMD processors and certain nVidia chipsets, for instance GeForce 6100 Northbridge/nForce 410 Southbridge. Here is the output of lsb_release -rd : Description: Ubuntu 14.04.2 LTS Release: 14.04 Please let me know if you need additional information. I will be happy to provide any information that you would find helpful. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-52-lowlatency 3.13.0-52.86 ProcVersionSignature: Ubuntu 3.13.0-52.86-lowlatency 3.13.11-ckt18 Uname: Linux 3.13.0-52-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gary 1804 F qasmixer gary 1952 F pulseaudio CurrentDesktop: XFCE Date: Tue May 19 18:06:54 2015 HibernationDevice: RESUME=UUID=c5872602-e17b-4383-8845-4b83d5332f13 InstallationDate: Installed on 2013-08-12 (645 days ago) InstallationMedia: Ubuntu-Studio 12.04.2 Precise Pangolin - Release i386 (20130213) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 003: ID 04cc:1521 ST-Ericsson USB 2.0 Hub Bus 001 Device 002: ID 04cf:8818 Myson Century, Inc. USB2.0 to ATAPI Bridge Controller 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 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-lowlatency root=UUID=e0b2c957-2687-46ae-ad75-68dd964b02b2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-52-lowlatency N/A linux-backports-modules-3.13.0-52-lowlatency N/A linux-firmware1.127.11 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-30 (384 days ago) dmi.bios.date: 08/11/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: C51MCP51 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/11/2006:svn:pn:pvr:rvn:rnC51MCP51:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456732] Re: linux: 3.19.0-18.18 -proposed tracker
No CVEs ** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed = In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) = John Johansen (jjohansen) ** Changed in: kernel-sru-workflow/security-signoff Status: In Progress = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456732 Title: linux: 3.19.0-18.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447371] Re: CVE-2015-3332
** Description changed: [TCP Fast Open local DoS] - Break-Fix: - local-2015-3332 + Break-Fix: 355a901e6cf1b2b763ec85caa2a9f04fbcc4ab4a local-2015-3332 -- 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/1447371 Title: CVE-2015-3332 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty 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-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New 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-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New 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-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: Invalid Status in linux-manta source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid:
[Kernel-packages] [Bug 1456987] [NEW] beaglebone: warning cpu cpu0: cpu0 regulator not ready, retry during boot
Public bug reported: From dmesg: ... [2.583310] cpu cpu0: cpu0 regulator not ready, retry [2.588716] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.612048] bL_switcher_halve_cpus: no CPU pairing possible [2.786225] cpu cpu0: cpu0 regulator not ready, retry [2.791644] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.820171] cpu cpu0: cpu0 regulator not ready, retry [2.825579] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.880831] cpu cpu0: cpu0 regulator not ready, retry [2.891547] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.909836] cpu cpu0: cpu0 regulator not ready, retry [2.915227] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [7.437203] cpu cpu0: cpu0 regulator not ready, retry [7.470228] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.117120] cpu cpu0: cpu0 regulator not ready, retry [8.136001] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.368726] cpu cpu0: cpu0 regulator not ready, retry [8.383608] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.497935] cpu cpu0: cpu0 regulator not ready, retry [8.514540] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.604475] cpu cpu0: cpu0 regulator not ready, retry [8.619969] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.249407] cpu cpu0: cpu0 regulator not ready, retry [9.265457] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.393519] cpu cpu0: cpu0 regulator not ready, retry [9.411153] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.411513] cpu cpu0: cpu0 regulator not ready, retry [9.445954] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.664395] cpu cpu0: cpu0 regulator not ready, retry [9.684708] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral ... that's because the cpufreq-cpu0 driver (that's built-in) requires the tsp65217 regulator driver that is compiled as a module (and not available during boot). While it's only a warning and it goes away when the rootfs is mounted (and the tps65217_regulator module is loaded), it's annoying and it spams the syslog. ** 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/1456987 Title: beaglebone: warning cpu cpu0: cpu0 regulator not ready, retry during boot Status in linux package in Ubuntu: Incomplete Bug description: From dmesg: ... [2.583310] cpu cpu0: cpu0 regulator not ready, retry [2.588716] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.612048] bL_switcher_halve_cpus: no CPU pairing possible [2.786225] cpu cpu0: cpu0 regulator not ready, retry [2.791644] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.820171] cpu cpu0: cpu0 regulator not ready, retry [2.825579] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.880831] cpu cpu0: cpu0 regulator not ready, retry [2.891547] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.909836] cpu cpu0: cpu0 regulator not ready, retry [2.915227] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [7.437203] cpu cpu0: cpu0 regulator not ready, retry [7.470228] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.117120] cpu cpu0: cpu0 regulator not ready, retry [8.136001] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.368726] cpu cpu0: cpu0 regulator not ready, retry [8.383608] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.497935] cpu cpu0: cpu0 regulator not ready, retry [8.514540] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.604475] cpu cpu0: cpu0 regulator not ready, retry [8.619969] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.249407] cpu cpu0: cpu0 regulator not ready, retry [9.265457] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.393519] cpu cpu0: cpu0 regulator not ready, retry [9.411153] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.411513] cpu cpu0: cpu0 regulator not ready, retry [9.445954] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.664395] cpu cpu0: cpu0 regulator not ready, retry [9.684708] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral ... that's because the cpufreq-cpu0 driver (that's
[Kernel-packages] [Bug 1456596] Re: DELL XPS 13 (9343) Strange, seemingly perpetual repeat of drm activity
I was able to install kernel 4.1.0-040100rc4-generic and this reported activity was NOT present ** Tags removed: kernel-unable-to-test-upstream ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456596 Title: DELL XPS 13 (9343) Strange, seemingly perpetual repeat of drm activity Status in linux package in Ubuntu: Confirmed Bug description: This laptop came factory preinstalled with Ubuntu, but due to problems had been modified. Most recent apport info from a few minutes ago is here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456585 dmesg output is added. There is about once every second this activity: [ 217.650626] [drm:intel_display_power_put] disabling display [ 217.650632] [drm:hsw_set_power_well] Requesting to disable the power well [ 217.682626] [drm:intel_display_power_get] enabling display [ 217.682631] [drm:hsw_set_power_well] Enabling power well dmesg output after cold boot, login to the desktop, starting the terminal, and leaving it for a few minutes is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456985] [NEW] Filesystem goes read-only while creating backups on HyperV
Public bug reported: Because ubuntu-bug linux not works because I am on kernel 3.19.0-17, I create this report manually. Summary of problem: we create backups with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 machines (EXT4). Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read-only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that the CentOS machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV, including snapshots and exports. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en- us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal System details: - Version signature: Ubuntu 3.19.0-17.17~14.04.1-generic 3.19.6 - lspci.log: http://paste.ubuntu.com/11242312/ - boot.log: http://paste.ubuntu.com/11242303/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: Filesystem goes read-only while creating VSS snapshot on HyperV Because ubuntu-bug linux not works because I am on kernel 3.19.0-17, I create this report manually. Summary of problem: we create VSS snapshots with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 machines (EXT4). Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read-only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that the CentOS machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en-us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only - While it was as follows on the 3.13.0-52 kernel: + While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal System details: - Version signature: Ubuntu 3.19.0-17.17~14.04.1-generic 3.19.6 - lspci.log: http://paste.ubuntu.com/11242312/ - boot.log: http://paste.ubuntu.com/11242303/ ** Summary changed: - Filesystem goes read-only while creating VSS snapshot on HyperV + Filesystem goes read-only while creating backups on HyperV ** Description changed: - Filesystem goes read-only while creating VSS snapshot on HyperV - Because ubuntu-bug linux not works because I am on kernel 3.19.0-17, I create this report manually. - Summary of problem: we create VSS snapshots with HyperV of 4 linux - virtual
[Kernel-packages] [Bug 1456985] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1456985 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/1456985 Title: Filesystem goes read-only while creating backups on HyperV Status in linux package in Ubuntu: Incomplete Bug description: Because ubuntu-bug linux not works because I am on kernel 3.19.0-17, I create this report manually. Summary of problem: we create backups with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 machines (EXT4). Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read- only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that the CentOS machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV, including snapshots and exports. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en- us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal System details: - Version signature: Ubuntu 3.19.0-17.17~14.04.1-generic 3.19.6 - lspci.log: http://paste.ubuntu.com/11242312/ - boot.log: http://paste.ubuntu.com/11242303/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1412097] Re: package linux-image-extra-3.16.0-29-generic 3.16.0-29.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Ubuntu has automatically removed all but 2 kernels for a long time. The bug is that it's not happening on your system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1412097 Title: package linux-image-extra-3.16.0-29-generic 3.16.0-29.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in One Hundred Papercuts: Triaged Status in linux package in Ubuntu: Triaged Bug description: This seems to happen from time to time. It's usually caused by images that weren't removed after an update. It's usually fixed by removing images that were not automatically removed and so are cluttering the device. I will probably have the issue fixed on my machine before anyone reads this. The only reason I report it is because I'm betting the average user can't fix the problem. A good permanent fix would be to have Ubuntu automatically remove old images on update to keep the space clean. I'd love to help make this happen but it's above my skill level. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-extra-3.16.0-29-generic 3.16.0-29.39 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: wes2940 F...m pulseaudio /dev/snd/controlC0: wes2940 F pulseaudio Date: Sat Jan 17 13:50:58 2015 DpkgTerminalLog: Log started: 2015-01-17 13:48:32 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-07 (133 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire 5735 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 SourcePackage: linux Title: package linux-image-extra-3.16.0-29-generic 3.16.0-29.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.08 dmi.board.name: CathedralPeak dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.08:bd09/10/2008:svnAcer:pnAspire5735:pvr0100:rvnAcer:rnCathedralPeak:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5735 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1412097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454160] Re: External monitor is disabled after resume
crs, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where XY and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: needs-bisect ** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1454160 Title: External monitor is disabled after resume Status in linux package in Ubuntu: Incomplete Bug description: I have an external screen connected to my machine (T450s, via docking station) and after resuming from suspend, my external monitor is disabled. After some trial and error I made an interesting observation: The external monitor only stops working if suspend via systemctl suspend, sudo pm-suspend, or via the hotkey on my keyboard (K750). However, this problem does not occur if I suspend via the menu entry in the upper right corner. How is this even possible? Mapping the suspend command from the upper right corner to a hotkey would be a sufficient workaround. But which command is used by that button? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 12 11:10:31 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2015-05-03 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20BWS03F00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET47WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS03F00 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:bvrJBET47WW(1.12):bd03/10/2015:svnLENOVO:pn20BWS03F00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS03F00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 12 11:08:05 2015 xserver.configfile: default xserver.errors:
[Kernel-packages] [Bug 1456952] Re: support the slub_debug boot option on specific object size
** Description changed: [Impact] slub_debug cannot work for specific kmem_cache size. e. g. slub_debug=PU,kmalloc-1024 The slub_debug is used to enable the debugging of use-after-free, poison overwritten, double free. And it also increases the up time of the server when the above mentioned errors happen instead of crashing immediately. However, currently, there exists bug that the slub_debug cannot be applied for the specific object size. This is not helpful to enable the whole system slub_debug because the performance loss will be up to 20%~30% according to the customer's measurement. The patch here to limit the slub_debug only on the specific object size to alleviate the performance loss. [Fix] The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s-name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s-flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. [Test case] + + Install the patched kernel. + sudo reboot + + sudo vim /etc/default/grub + append slub_debug=FPZU,kmalloc-1024 to GRUB_CMDLINE_LINUX_DEFAULT + sudo update-grub + sudo reboot + + # Check if the kmalloc-1024 debug options are enabled + sudo cat /sys/kernel/slab/kmalloc-1024/sanity_checks + # shoulb be 1 + sudo cat /sys/kernel/slab/kmalloc-1024/red_zone + # shoulb be 1 + sudo cat /sys/kernel/slab/kmalloc-1024/poison + # shoulb be 1 + + # Check other object size + sudo cat /sys/kernel/slab/kmalloc-8/sanity_checks + # shoulb be 0 + sudo cat /sys/kernel/slab/kmalloc-8/red_zone + # shoulb be 0 + sudo cat /sys/kernel/slab/kmalloc-8/poison + # shoulb be 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456952 Title: support the slub_debug boot option on specific object size Status in linux package in Ubuntu: Incomplete Bug description: [Impact] slub_debug cannot work for specific kmem_cache size. e. g. slub_debug=PU,kmalloc-1024 The slub_debug is used to enable the debugging of use-after-free, poison overwritten, double free. And it also increases the up time of the server when the above mentioned errors happen instead of crashing immediately. However, currently, there exists bug that the slub_debug cannot be applied for the specific object size. This is not helpful to enable the whole system slub_debug because the performance loss will be up to 20%~30% according to the customer's measurement. The patch here to limit the slub_debug only on the specific object size to alleviate the performance loss. [Fix] The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s-name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s-flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. [Test case] Install the patched kernel. sudo reboot sudo vim /etc/default/grub append slub_debug=FPZU,kmalloc-1024 to GRUB_CMDLINE_LINUX_DEFAULT sudo update-grub sudo reboot # Check if the kmalloc-1024 debug options are enabled sudo cat /sys/kernel/slab/kmalloc-1024/sanity_checks # shoulb be 1 sudo cat /sys/kernel/slab/kmalloc-1024/red_zone # shoulb be 1 sudo cat /sys/kernel/slab/kmalloc-1024/poison # shoulb be 1 # Check other object size sudo cat /sys/kernel/slab/kmalloc-8/sanity_checks # shoulb be 0 sudo cat /sys/kernel/slab/kmalloc-8/red_zone # shoulb be 0 sudo cat /sys/kernel/slab/kmalloc-8/poison # shoulb be 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
The problem we encountered with HyperV backups, filed here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456985, should be solved by these patches too. Our bug is an exact copy of the initial bug that was reported here: https://social.technet.microsoft.com/Forums/windowsserver/en-US /8807f61c-565e-45bc-abc4-af09abf59de2/ubuntu-14042-lts-generation-2 -scsi-errors-on-vss-based-backups. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: [Hyper-V] Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447371] Re: CVE-2015-3332
** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New = Invalid -- 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/1447371 Title: CVE-2015-3332 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty 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-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New 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-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New 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: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Committed Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: Invalid Status in linux-manta source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in
[Kernel-packages] [Bug 1456985] Re: Filesystem goes read-only while creating backups on HyperV
@brad-figg: I just found out that this bug will be solved by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456985 Title: Filesystem goes read-only while creating backups on HyperV Status in linux package in Ubuntu: Fix Committed Bug description: Because ubuntu-bug linux not works because I am on kernel 3.19.0-17, I create this report manually. Summary of problem: we create backups with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 machines (EXT4). Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read- only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that the CentOS machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV, including snapshots and exports. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en- us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal System details: - Version signature: Ubuntu 3.19.0-17.17~14.04.1-generic 3.19.6 - lspci.log: http://paste.ubuntu.com/11242312/ - boot.log: http://paste.ubuntu.com/11242303/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456985] Re: Filesystem goes read-only while creating backups on HyperV
*** This bug is a duplicate of bug 1445195 *** https://bugs.launchpad.net/bugs/1445195 ** This bug has been marked a duplicate of bug 1445195 [Hyper-V] Kernel patches for storvsc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456985 Title: Filesystem goes read-only while creating backups on HyperV Status in linux package in Ubuntu: Fix Committed Bug description: Because ubuntu-bug linux not works because I am on kernel 3.19.0-17, I create this report manually. Summary of problem: we create backups with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 machines (EXT4). Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read- only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that the CentOS machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV, including snapshots and exports. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en- us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal System details: - Version signature: Ubuntu 3.19.0-17.17~14.04.1-generic 3.19.6 - lspci.log: http://paste.ubuntu.com/11242312/ - boot.log: http://paste.ubuntu.com/11242303/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456732] Re: linux: 3.19.0-18.18 -proposed tracker
** Description changed: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC + kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456732 Title: linux: 3.19.0-18.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1453593] Re: [gm45] 3.19.0-17 freeze
According to comment #36, verification has been done already. Tagging bug as verified. ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453593 Title: [gm45] 3.19.0-17 freeze Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Bug description: boot with 3.19.0-17 freezes at very early stage, way before the appearance of login screen. no such problems with kernel 3.19.0-16. Tested upstream kernels 4.0.0-1, 4.01, 4.0.2 and 4.1-rc2: all of them boot normally. No problems to boot with 3.19.0-17 in a lubuntu15.04 virtual machine under virtualbox (running on the same hardware platform). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: volker 2576 F pulseaudio CurrentDesktop: LXDE Date: Sun May 10 21:09:41 2015 HibernationDevice: RESUME=UUID=56d8d5bd-f32d-4192-a0d4-2395d9df1637 InstallationDate: Installed on 2014-02-12 (451 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Dell Inc. Latitude E6500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=6ff58f38-956b-49de-99d4-01dfc84b96ad ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NY667 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/18/2008:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1453593] Re: [gm45] 3.19.0-17 freeze
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1453593 Title: [gm45] 3.19.0-17 freeze Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Bug description: boot with 3.19.0-17 freezes at very early stage, way before the appearance of login screen. no such problems with kernel 3.19.0-16. Tested upstream kernels 4.0.0-1, 4.01, 4.0.2 and 4.1-rc2: all of them boot normally. No problems to boot with 3.19.0-17 in a lubuntu15.04 virtual machine under virtualbox (running on the same hardware platform). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: volker 2576 F pulseaudio CurrentDesktop: LXDE Date: Sun May 10 21:09:41 2015 HibernationDevice: RESUME=UUID=56d8d5bd-f32d-4192-a0d4-2395d9df1637 InstallationDate: Installed on 2014-02-12 (451 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Dell Inc. Latitude E6500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=6ff58f38-956b-49de-99d4-01dfc84b96ad ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NY667 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/18/2008:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0NY667:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456987] Re: beaglebone: warning cpu cpu0: cpu0 regulator not ready, retry during boot
** Changed in: linux (Ubuntu) Assignee: (unassigned) = Paolo Pisati (p-pisati) ** Description changed: + SRU Justification: + + Impact: during boot, the logs are spammed with several repeated + warning messages. + + Fix: apply the patches, recompile and reboot. + + Testcase: try booting with and without the patches applied and see + if you can find the below warning messages in your logs. + + --- + + From dmesg: ... [2.583310] cpu cpu0: cpu0 regulator not ready, retry [2.588716] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.612048] bL_switcher_halve_cpus: no CPU pairing possible [2.786225] cpu cpu0: cpu0 regulator not ready, retry [2.791644] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.820171] cpu cpu0: cpu0 regulator not ready, retry [2.825579] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.880831] cpu cpu0: cpu0 regulator not ready, retry [2.891547] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.909836] cpu cpu0: cpu0 regulator not ready, retry [2.915227] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [7.437203] cpu cpu0: cpu0 regulator not ready, retry [7.470228] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.117120] cpu cpu0: cpu0 regulator not ready, retry [8.136001] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.368726] cpu cpu0: cpu0 regulator not ready, retry [8.383608] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.497935] cpu cpu0: cpu0 regulator not ready, retry [8.514540] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.604475] cpu cpu0: cpu0 regulator not ready, retry [8.619969] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.249407] cpu cpu0: cpu0 regulator not ready, retry [9.265457] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.393519] cpu cpu0: cpu0 regulator not ready, retry [9.411153] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.411513] cpu cpu0: cpu0 regulator not ready, retry [9.445954] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.664395] cpu cpu0: cpu0 regulator not ready, retry [9.684708] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral ... that's because the cpufreq-cpu0 driver (that's built-in) requires the tsp65217 regulator driver that is compiled as a module (and not available during boot). While it's only a warning and it goes away when the rootfs is mounted (and the tps65217_regulator module is loaded), it's annoying and it spams the syslog. ** Patch added: 0001-UBUNTU-Config-armhf-MFD_TPS65217-y-REGULATOR_TPS6521.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456987/+attachment/4400941/+files/0001-UBUNTU-Config-armhf-MFD_TPS65217-y-REGULATOR_TPS6521.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456987 Title: beaglebone: warning cpu cpu0: cpu0 regulator not ready, retry during boot Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: during boot, the logs are spammed with several repeated warning messages. Fix: apply the patches, recompile and reboot. Testcase: try booting with and without the patches applied and see if you can find the below warning messages in your logs. --- From dmesg: ... [2.583310] cpu cpu0: cpu0 regulator not ready, retry [2.588716] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.612048] bL_switcher_halve_cpus: no CPU pairing possible [2.786225] cpu cpu0: cpu0 regulator not ready, retry [2.791644] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.820171] cpu cpu0: cpu0 regulator not ready, retry [2.825579] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.880831] cpu cpu0: cpu0 regulator not ready, retry [2.891547] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.909836] cpu cpu0: cpu0 regulator not ready, retry [2.915227] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [7.437203] cpu cpu0: cpu0 regulator not ready, retry [7.470228] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.117120] cpu cpu0: cpu0 regulator not ready, retry [8.136001] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.368726] cpu cpu0: cpu0 regulator not ready, retry [8.383608] platform cpufreq-cpu0.0: Driver cpufreq-cpu0
[Kernel-packages] [Bug 1454160] [NEW] External monitor is disabled after resume
You have been subscribed to a public bug: I have an external screen connected to my machine (T450s, via docking station) and after resuming from suspend, my external monitor is disabled. After some trial and error I made an interesting observation: The external monitor only stops working if suspend via systemctl suspend, sudo pm-suspend, or via the hotkey on my keyboard (K750). However, this problem does not occur if I suspend via the menu entry in the upper right corner. How is this even possible? Mapping the suspend command from the upper right corner to a hotkey would be a sufficient workaround. But which command is used by that button? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 12 11:10:31 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2015-05-03 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20BWS03F00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET47WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS03F00 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:bvrJBET47WW(1.12):bd03/10/2015:svnLENOVO:pn20BWS03F00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS03F00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 12 11:08:05 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 latest-bios-1.13 needs-bisect regression-release ubuntu vivid -- External monitor is disabled after resume https://bugs.launchpad.net/bugs/1454160 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456987] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1456987 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/1456987 Title: beaglebone: warning cpu cpu0: cpu0 regulator not ready, retry during boot Status in linux package in Ubuntu: Incomplete Bug description: From dmesg: ... [2.583310] cpu cpu0: cpu0 regulator not ready, retry [2.588716] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.612048] bL_switcher_halve_cpus: no CPU pairing possible [2.786225] cpu cpu0: cpu0 regulator not ready, retry [2.791644] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.820171] cpu cpu0: cpu0 regulator not ready, retry [2.825579] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.880831] cpu cpu0: cpu0 regulator not ready, retry [2.891547] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.909836] cpu cpu0: cpu0 regulator not ready, retry [2.915227] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [7.437203] cpu cpu0: cpu0 regulator not ready, retry [7.470228] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.117120] cpu cpu0: cpu0 regulator not ready, retry [8.136001] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.368726] cpu cpu0: cpu0 regulator not ready, retry [8.383608] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.497935] cpu cpu0: cpu0 regulator not ready, retry [8.514540] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.604475] cpu cpu0: cpu0 regulator not ready, retry [8.619969] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.249407] cpu cpu0: cpu0 regulator not ready, retry [9.265457] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.393519] cpu cpu0: cpu0 regulator not ready, retry [9.411153] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.411513] cpu cpu0: cpu0 regulator not ready, retry [9.445954] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.664395] cpu cpu0: cpu0 regulator not ready, retry [9.684708] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral ... that's because the cpufreq-cpu0 driver (that's built-in) requires the tsp65217 regulator driver that is compiled as a module (and not available during boot). While it's only a warning and it goes away when the rootfs is mounted (and the tps65217_regulator module is loaded), it's annoying and it spams the syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by l
Someone should really look into this bug, I've been getting it *at least* once per day on my thinkpad t60 (it's more like 2-3 times daily on average though) running xubuntu 15.04 64 bit, rendering whole operating system pretty much unusable for anything that requires longer/permanent internet connection... Logs show same errors as the ones already attached. -- 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/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in linux-firmware package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] [NEW] linux: 3.13.0-53.89 -proposed tracker
Public bug reported: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 09:58 UTC ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Tags: block-proposed-trusty kernel-release-tracking-bug trusty ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-trusty ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) = Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Importance:
[Kernel-packages] [Bug 1453593] Re: [gm45] 3.19.0-17 freeze
This bug was fixed in the package linux - 3.19.0-18.18 --- linux (3.19.0-18.18) vivid; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1456732 [ Upstream Kernel Changes ] * Revert drm/i915: remove intel_pipe_set_base() (v4) - LP: #1453593 linux (3.19.0-17.17) vivid; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1452000 [ Damien Lespiau ] * SAUCE: i915_bpo: drm/i915/skl: Fix stepping check for a couple of W/As - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Implement WaDisableVFUnitClockGating - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add the INIT power domain to the MISC I/O power well - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Fix the CTRL typo in the DPLL_CRTL1 defines - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Make the Misc I/O power well part of the PLLS domain - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Deinit/init the display at suspend/resume - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Change CDCLK behind PCU's back - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: gen6+ platforms support runtime PM - LP: #1449469 [ Imre Deak ] * SAUCE: i915_bpo: drm/i915/gen9: fix PIPE_CONTROL flush for VS_INVALIDATE - LP: #1449469 [ Leann Ogasawara ] * [Config] Set CONFIG_XEN_MAX_DOMAIN_MEMORY defaults [ Matt Roper ] * SAUCE: i915_bpo: drm/i915: Switch to full atomic helpers for plane updates/disable, take two - LP: #1449469 [ Sonika Jindal ] * SAUCE: i915_bpo: drm/i915/skl: Allow universal planes to position - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Support for 90/270 rotation - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add back HDMI translation table - LP: #1449469 [ Stefan Bader ] * SAUCE: vesafb: Set mtrr:3 (write-combining) as default - LP: #1434581 [ Timo Aaltonen ] * SAUCE: Call i915_bpo specific functions from the hda driver - LP: #1449464 * SAUCE: i915_bpo: Use get_display_clock_speed - LP: #1449469 * SAUCE: i915_bpo: Add a few register definitions - LP: #1449469 [ Upstream Kernel Changes ] * Revert sparc/PCI: Clip bridge windows to fit in upstream windows - LP: #1446316 * Revert PM / hibernate: avoid unsafe pages in e820 reserved regions - LP: #1446316 * Revert libceph: use memalloc flags for net IO - LP: #1446316 * Revert net: Reset secmark when scrubbing packet - LP: #1451996 * ASoC: da732x: Fix control-less DAPM routes - LP: #1446316 * ASoC: ak4671: Fix control-less DAPM routes - LP: #1446316 * ASoC: sn95031: Fix control-less DAPM routes - LP: #1446316 * ASoC: sgtl5000: remove useless register write clearing CHRGPUMP_POWERUP - LP: #1446316 * ASoC: pcm1681: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: cs4271: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: es8238: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8960: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: tas5086: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8731: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm2000: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8903: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8904: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: ak4641: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: adav80x: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8955: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9712: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9713: Fix wrong value references for boolean kctl - LP: #1446316 * virtio_balloon: set DRIVER_OK before using device - LP: #1446316 * virtio-balloon: do not call blocking ops when !TASK_RUNNING - LP: #1446316 * clockevents: sun5i: Fix setup_irq init sequence - LP: #1446316 * regmap: regcache-rbtree: Fix present bitmap resize - LP: #1446316 * regmap: introduce regmap_name to fix syscon regmap trace events - LP: #1446316 * clocksource: efm32: Fix a NULL pointer dereference - LP: #1446316 * tcm_fc: missing curly braces in ft_invl_hw_context() - LP: #1446316 * tcm_qla2xxx: Fix incorrect use of __transport_register_session - LP: #1446316 * nl80211: ignore HT/VHT capabilities without QoS/WMM - LP: #1446316 * mac80211: disable u-APSD queues by default - LP: #1446316 * mac80211: drop unencrypted frames in mesh fwding - LP: #1446316 * mac80211: count interfaces correctly for combination checks - LP: #1446316 * iwlwifi: mvm: rs: fix BT Coex check to look at the correct ant - LP: #1446316 * iwlwifi: fix max_ht_ampdu_exponent for older devices
[Kernel-packages] [Bug 1456732] Re: linux: 3.19.0-18.18 -proposed tracker
This bug was fixed in the package linux - 3.19.0-18.18 --- linux (3.19.0-18.18) vivid; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1456732 [ Upstream Kernel Changes ] * Revert drm/i915: remove intel_pipe_set_base() (v4) - LP: #1453593 linux (3.19.0-17.17) vivid; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1452000 [ Damien Lespiau ] * SAUCE: i915_bpo: drm/i915/skl: Fix stepping check for a couple of W/As - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Implement WaDisableVFUnitClockGating - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add the INIT power domain to the MISC I/O power well - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Fix the CTRL typo in the DPLL_CRTL1 defines - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Make the Misc I/O power well part of the PLLS domain - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Deinit/init the display at suspend/resume - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Change CDCLK behind PCU's back - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: gen6+ platforms support runtime PM - LP: #1449469 [ Imre Deak ] * SAUCE: i915_bpo: drm/i915/gen9: fix PIPE_CONTROL flush for VS_INVALIDATE - LP: #1449469 [ Leann Ogasawara ] * [Config] Set CONFIG_XEN_MAX_DOMAIN_MEMORY defaults [ Matt Roper ] * SAUCE: i915_bpo: drm/i915: Switch to full atomic helpers for plane updates/disable, take two - LP: #1449469 [ Sonika Jindal ] * SAUCE: i915_bpo: drm/i915/skl: Allow universal planes to position - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Support for 90/270 rotation - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add back HDMI translation table - LP: #1449469 [ Stefan Bader ] * SAUCE: vesafb: Set mtrr:3 (write-combining) as default - LP: #1434581 [ Timo Aaltonen ] * SAUCE: Call i915_bpo specific functions from the hda driver - LP: #1449464 * SAUCE: i915_bpo: Use get_display_clock_speed - LP: #1449469 * SAUCE: i915_bpo: Add a few register definitions - LP: #1449469 [ Upstream Kernel Changes ] * Revert sparc/PCI: Clip bridge windows to fit in upstream windows - LP: #1446316 * Revert PM / hibernate: avoid unsafe pages in e820 reserved regions - LP: #1446316 * Revert libceph: use memalloc flags for net IO - LP: #1446316 * Revert net: Reset secmark when scrubbing packet - LP: #1451996 * ASoC: da732x: Fix control-less DAPM routes - LP: #1446316 * ASoC: ak4671: Fix control-less DAPM routes - LP: #1446316 * ASoC: sn95031: Fix control-less DAPM routes - LP: #1446316 * ASoC: sgtl5000: remove useless register write clearing CHRGPUMP_POWERUP - LP: #1446316 * ASoC: pcm1681: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: cs4271: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: es8238: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8960: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: tas5086: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8731: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm2000: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8903: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8904: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: ak4641: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: adav80x: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8955: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9712: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9713: Fix wrong value references for boolean kctl - LP: #1446316 * virtio_balloon: set DRIVER_OK before using device - LP: #1446316 * virtio-balloon: do not call blocking ops when !TASK_RUNNING - LP: #1446316 * clockevents: sun5i: Fix setup_irq init sequence - LP: #1446316 * regmap: regcache-rbtree: Fix present bitmap resize - LP: #1446316 * regmap: introduce regmap_name to fix syscon regmap trace events - LP: #1446316 * clocksource: efm32: Fix a NULL pointer dereference - LP: #1446316 * tcm_fc: missing curly braces in ft_invl_hw_context() - LP: #1446316 * tcm_qla2xxx: Fix incorrect use of __transport_register_session - LP: #1446316 * nl80211: ignore HT/VHT capabilities without QoS/WMM - LP: #1446316 * mac80211: disable u-APSD queues by default - LP: #1446316 * mac80211: drop unencrypted frames in mesh fwding - LP: #1446316 * mac80211: count interfaces correctly for combination checks - LP: #1446316 * iwlwifi: mvm: rs: fix BT Coex check to look at the correct ant - LP: #1446316 * iwlwifi: fix max_ht_ampdu_exponent for older devices
Re: [Kernel-packages] [Bug 1455852] Re: 15.04 will not boot on MacBook 2, 1
another possible candidate re boot hang: commit 0e126cfab3928e8b01e17e1e707eec2bfdb4f1c2 Author: Len Brown len.br...@intel.com Date: Wed Jan 15 00:37:34 2014 -0500 sched/idle/x86: Restore mwait_idle() to fix boot hangs, to improve power savings and to improve performance commit b253149b843f89cd300cbdbea27ce1f847506f99 upstream. In Linux-3.9 we removed the mwait_idle() loop: 69fb3676df33 (x86 idle: remove mwait_idle() and idle=mwait cmdline param) The reasoning was that modern machines should be sufficiently happy during the boot process using the default_idle() HALT loop, until cpuidle loads and either acpi_idle or intel_idle invoke the newer MWAIT-with-hints idle loop. But two machines reported problems: 1. Certain Core2-era machines support MWAIT-C1 and HALT only. MWAIT-C1 is preferred for optimal power and performance. But if they support just C1, cpuidle never loads and so they use the boot-time default idle loop forever. 2. Some laptops will boot-hang if HALT is used, but will boot successfully if MWAIT is used. This appears to be a hidden assumption in BIOS SMI, that is presumably valid on the proprietary OS where the BIOS was validated. https://bugzilla.kernel.org/show_bug.cgi?id=60770 So here we effectively revert the patch above, restoring the mwait_idle() loop. However, we don't bother restoring the idle=mwait cmdline parameter, since it appears to add no value. Maintainer notes: For 3.9, simply revert 69fb3676df for 3.10, patch -F3 applies, fuzz needed due to __cpuinit use in context For 3.11, 3.12, 3.13, this patch applies cleanly Tested-by: Mike Galbraith bitbuc...@online.de Signed-off-by: Len Brown len.br...@intel.com Acked-by: Mike Galbraith bitbuc...@online.de Cc: Borislav Petkov b...@alien8.de Cc: H. Peter Anvin h...@zytor.com Cc: Ian Malone ibmal...@gmail.com Cc: Josh Boyer jwbo...@redhat.com Cc: Linus Torvalds torva...@linux-foundation.org Cc: Mike Galbraith efa...@gmx.de Cc: Peter Zijlstra pet...@infradead.org Cc: Thomas Gleixner t...@linutronix.de Link: http://lkml.kernel.org/r/345254a551eb5a6a866e048d7ab570fd2193aca4.1389763084.git.len.br...@intel.com [ Ported to recent kernels. ] Signed-off-by: Ingo Molnar mi...@kernel.org Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org On 20 May 2015 at 16:50, Nils Fenner nilsfen...@web.de wrote: Agree'd. With this patch, screen turns off (not only black). -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1455852 Title: 15.04 will not boot on MacBook 2,1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455852/+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/1455852 Title: 15.04 will not boot on MacBook 2,1 Status in linux package in Ubuntu: Incomplete Bug description: see: http://ubuntuforums.org/showthread.php?t=2274999p=13286624#post13286624 Lubuntu 15.04 on refit grub dual boot macbook 2,1 linux-image-3.16 will boot, though sometimes hangs but, reboot will work eventually. With linux-image-3.19 never, ? is the GPU hang reported in kern.log relevant here? i915 problem? see kern.log snippet attached see error attached from GPU crash dump saved to /sys/class/drm/card0/error This seems to be a BUG as suggested by the log: ... Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel from: /sys/class/drm/card0/error: GPU HANG: ecode -1:0x, reason: Command parser error, iir 0x8000, action: continue Time: 1431810790 s 799079 us Kernel: 3.16.0-25-generic Reset count: 0 Suspend count: 0 PCI ID: 0x27a2 EIR: 0x0010 IER: 0x00028053 PGTBL_ER: 0x0102 FORCEWAKE: 0x DERRMR: 0x CCID: 0x Missed interrupts: 0x fence[0] = fence[1] = fence[2] = fence[3] = fence[4] = fence[5] = fence[6] = fence[7] = fence[8] = fence[9] = fence[10] = fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = INSTDONE_0: 0x7fc0 INSTDONE_1: 0x INSTDONE_2: 0x INSTDONE_3: 0x render command stream: bsd command stream: blt command stream: vebox command stream: bsd2 command stream: Active [0]: Pinned [0]: Num Pipes: 2 Pipe [0]: Power: on SRC: 027f01df STAT: 9a03 Plane [0]: CNTR: STRIDE: SIZE: POS: ADDR: Cursor
[Kernel-packages] [Bug 1453935] Re: Update iwlwifi -12 ucode to version 25.17.12.0
This bug was fixed in the package linux-firmware - 1.143.1 --- linux-firmware (1.143.1) vivid; urgency=medium * iwlwifi: update -12.ucode for 3160 / 7260 / 7265 / 7265D -LP: #1453935 -- Seth Forshee seth.fors...@canonical.com Mon, 11 May 2015 14:41:22 -0500 ** Changed in: linux-firmware (Ubuntu Vivid) Status: Fix Committed = Fix Released -- 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/1453935 Title: Update iwlwifi -12 ucode to version 25.17.12.0 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Vivid: Fix Released Bug description: Version number: 25.17.12.0 Revision number: 145607 Build number: WFFW12659 Intel says This release fixes disconnections and stability issues. This is a bug fix release of the iwlwifi firmware, targeted at addressing user-reported issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1453935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1453935] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1453935 Title: Update iwlwifi -12 ucode to version 25.17.12.0 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Vivid: Fix Released Bug description: Version number: 25.17.12.0 Revision number: 145607 Build number: WFFW12659 Intel says This release fixes disconnections and stability issues. This is a bug fix release of the iwlwifi firmware, targeted at addressing user-reported issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1453935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456952] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1456952 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/1456952 Title: support the slub_debug boot option on specific object size Status in linux package in Ubuntu: Incomplete Bug description: [Impact] slub_debug cannot work for specific kmem_cache size. e. g. slub_debug=PU,kmalloc-1024 The slub_debug is used to enable the debugging of use-after-free, poison overwritten, double free. And it also increases the up time of the server when the above mentioned errors happen instead of crashing immediately. However, currently, there exists bug that the slub_debug cannot be applied for the specific object size. This is not helpful to enable the whole system slub_debug because the performance loss will be up to 20%~30% according to the customer's measurement. The patch here to limit the slub_debug only on the specific object size to alleviate the performance loss. [Fix] The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s-name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s-flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. [Test case] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454160] Re: External monitor is disabled after resume
This bug still exists on 4.1.0-040100rc4-generic #201505181436 SMP Mon May 18 18:38:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-rc4 ** 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/1454160 Title: External monitor is disabled after resume Status in linux package in Ubuntu: Confirmed Bug description: I have an external screen connected to my machine (T450s, via docking station) and after resuming from suspend, my external monitor is disabled. After some trial and error I made an interesting observation: The external monitor only stops working if suspend via systemctl suspend, sudo pm-suspend, or via the hotkey on my keyboard (K750). However, this problem does not occur if I suspend via the menu entry in the upper right corner. How is this even possible? Mapping the suspend command from the upper right corner to a hotkey would be a sufficient workaround. But which command is used by that button? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 12 11:10:31 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2015-05-03 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 20BWS03F00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET47WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS03F00 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:bvrJBET47WW(1.12):bd03/10/2015:svnLENOVO:pn20BWS03F00:pvrThinkPadT450s:rvnLENOVO:rn20BWS03F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS03F00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 12 11:08:05 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456732] onibi (amd64) - tests ran: 274, failed: 31
tests ran: 274, failed: 31; http://kernel.ubuntu.com/testing/onibi__3.19.0-18.18__2015-05-20_05-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/1456732 Title: linux: 3.19.0-18.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455575] Re: vivid master-next kernel: intel driver fails at startup on Dell Inc. Inspiron 1545
*** This bug is a duplicate of bug 1453593 *** https://bugs.launchpad.net/bugs/1453593 ** This bug has been marked a duplicate of bug 1453593 [gm45] 3.19.0-17 freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1455575 Title: vivid master-next kernel: intel driver fails at startup on Dell Inc. Inspiron 1545 Status in linux package in Ubuntu: Incomplete Bug description: I built 3.19.0-18 from master-next (commit ccb645c) and my Dell 1545 boots, but X doesn't run. I was able to SSH to the machine and find this in dmesg output: [ 18.128077] [ cut here ] [ 18.128117] kernel BUG at /home/aaron/work/kernel/build/drivers/gpu/drm/i915/intel_display.c:11705! [ 18.128163] invalid opcode: [#1] SMP [ 18.128197] Modules linked in: arc4 b43 dell_wmi uvcvideo bcma gpio_ich sparse_keymap mac80211 dell_laptop dcdbas i8k snd_hda_codec_idt snd_hda_codec_generic cfg80211 videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common i915 videodev snd_hda_intel media coretemp snd_hda_controller joydev snd_hda_codec serio_raw snd_hwdep snd_pcm snd_seq_midi lpc_ich drm_kms_helper snd_seq_midi_event drm snd_rawmidi snd_seq snd_seq_device snd_timer shpchp snd i2c_algo_bit soundcore wmi mac_hid video cuse parport_pc ppdev lp parport autofs4 hid_generic usbhid hid ums_realtek uas usb_storage psmouse ahci sky2 libahci ssb [ 18.128735] CPU: 1 PID: 272 Comm: plymouthd Not tainted 3.19.0-18-generic #18 [ 18.128771] Hardware name: Dell Inc. Inspiron 1545 /0G848F, BIOS A13 10/23/2009 [ 18.128814] task: 8800d7dbebf0 ti: 88011a2f8000 task.ti: 88011a2f8000 [ 18.128851] RIP: 0010:[c04d1fa8] [c04d1fa8] intel_primary_plane_disable+0xe8/0xf0 [i915] [ 18.128933] RSP: 0018:88011a2fbb78 EFLAGS: 00010246 [ 18.128963] RAX: c051df40 RBX: 8800d6713b90 RCX: 8800d7ef [ 18.128999] RDX: 8000 RSI: 0297 RDI: 8800366c5c00 [ 18.129034] RBP: 88011a2fbb98 R08: 0001 R09: 88011a2fbb0c [ 18.129069] R10: 0297 R11: 1e85 R12: 8800d6713800 [ 18.129104] R13: R14: 8800d6713800 R15: 880119c02000 [ 18.129140] FS: 7f1c049b2740() GS:88011fd0() knlGS: [ 18.129184] CS: 0010 DS: ES: CR0: 80050033 [ 18.129213] CR2: 7f68e43c7000 CR3: 00011a2f5000 CR4: 000407e0 [ 18.129248] Stack: [ 18.129263] 0002 8800d6713b90 0002 0001 [ 18.129318] 88011a2fbc78 c04d52ff 03160308 [ 18.129373] 003c 880119c01000 8800d6713b60 ffea [ 18.129428] Call Trace: [ 18.129465] [c04d52ff] __intel_set_mode+0x8df/0xb70 [i915] [ 18.129518] [c04dbf4b] intel_crtc_set_config+0xc0b/0xfe0 [i915] [ 18.129574] [c0352ac6] drm_mode_set_config_internal+0x66/0x100 [drm] [ 18.129618] [c03c3298] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [ 18.129661] [c03c5309] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper] [ 18.129730] [c04e947e] intel_fbdev_restore_mode+0x1e/0x50 [i915] [ 18.129788] [c050e28e] i915_driver_lastclose+0xe/0x20 [i915] [ 18.129830] [c0345cde] drm_lastclose+0x2e/0x150 [drm] [ 18.129872] [c0346130] drm_release+0x330/0x520 [drm] [ 18.129906] [811f6617] __fput+0xe7/0x250 [ 18.129933] [811f67ce] fput+0xe/0x10 [ 18.129961] [81093e27] task_work_run+0xb7/0xf0 [ 18.129992] [81014ff7] do_notify_resume+0x97/0xb0 [ 18.130026] [817cb16f] int_signal+0x12/0x17 [ 18.130055] Code: 00 00 48 8b 3b 48 8d b3 88 00 00 00 e8 a2 e1 ff ff e9 69 ff ff ff 0f 1f 44 00 00 31 ff eb aa 0f 1f 40 00 31 ff eb 88 0f 1f 40 00 0f 0b 66 0f 1f 44 00 00 66 66 66 66 90 55 41 01 c9 48 89 e5 41 [ 18.130438] RIP [c04d1fa8] intel_primary_plane_disable+0xe8/0xf0 [i915] [ 18.130502] RSP 88011a2fbb78 [ 18.130523] ---[ end trace 7037451fb494950a ]--- The machine works fine with 3.19.0-16, which I built with one extra commit for bug 1448942. Since that fix has since been merged in master-next I was trying to test a newer kernel to see when I can get back out of the business of building my own. My first try failed due to a hang that was later fixed by commit 1ece1db, and my second try left me here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1456585] Re: DELL XPS 13 (9343) Only wireless 5GHz works, but not 2.4GHz
I managed to install the 4.1.0 rc4 kernel uname -a Linux xps13 4.1.0-040100rc4-generic #201505181436 SMP Mon May 18 18:38:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux but building the Broadcom wl module failed, the make.log is attached. There is no wireless at all on this kernel ullix@xps13:~$ sudo apt-get install --reinstall bcmwl-kernel-source [sudo] password for ullix: Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 1.512 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted bcmwl-kernel-source amd64 6.30.223.248+bdcom-0ubuntu0.1 [1.512 kB] Fetched 1.512 kB in 1s (1.007 kB/s) (Reading database ... 355279 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu0.1_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu0.1) over (6.30.223.248+bdcom-0ubuntu0.1) ... Setting up bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu0.1) ... Loading new bcmwl-6.30.223.248+bdcom DKMS files... Building only for 4.1.0-040100rc4-generic Building for architecture x86_64 Building initial module for 4.1.0-040100rc4-generic ERROR (dkms apport): kernel package linux-headers-4.1.0-040100rc4-generic is not supported Error! Bad return status for module build on kernel: 4.1.0-040100rc4-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more information. modprobe: FATAL: Module wl not found. update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.103ubuntu4.2) ... update-initramfs: Generating /boot/initrd.img-4.1.0-040100rc4-generic ** Attachment added: make.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456585/+attachment/4400983/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456585 Title: DELL XPS 13 (9343) Only wireless 5GHz works, but not 2.4GHz Status in linux package in Ubuntu: Confirmed Bug description: This laptop came factory preinstalled with Ubuntu 14.04, but it had and still has way too many problems. I have now kernel 3.16.0-37-generic running. The wireless driver is wl, installed from bcmwl-kernel-source. I have wireless working at 5GHz with good speed, everything well. However, I can't connect to wireless on 2.4GHz. Before I had kernel 3.13.0-52-generic, which had the same problem. I tried kernel 4.1.0-rc2 and rc3, but both failed on installing from bcmwl-kernel-source. Trying iwlist wlan0 freq I get a list of channels 1-14 at 2.4GHz, and 32-66 at 5GHz. Still, only the 5GHz works. Other devices in my house do connect well to the 2.4GHz (from a Fritzbox router). iwlist wlan0 scan has no scan result when 5GHz is disabled, and finds one network at 5.18GHz when enabled. --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ullix 1839 F pulseaudio /dev/snd/controlC0: ullix 1839 F pulseaudio CurrentDesktop: MATE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b6c248b-36d3-4dcf-9e9e-427d50206af6 InstallationDate: Installed on 2015-04-24 (25 days ago) InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. XPS 13 9343 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=fda802ca-9257-4fed-bb0d-9f4756dca419 ro pcie_aspm=force radeon.modeset=0 plymouth:debug drm.debug=0xe nouveau.modeset=0 video.use_native_backlight=1 quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 acpi_osi=Windows 2013 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 RelatedPackageVersions: linux-restricted-modules-3.16.0-37-generic N/A linux-backports-modules-3.16.0-37-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1450756] Re: suspend fails
I tried to bisect the kernel but ended up in a dead end. http://ubuntuforums.org/archive/index.php/t-2078650.html describes exactly my problem to help -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450756 Title: suspend fails Status in linux package in Ubuntu: Incomplete Bug description: On all kernel suspend is not possible. I ran pm_test and it hangs. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jott 1557 F pulseaudio CurrentDesktop: KDE Date: Fri May 1 11:55:32 2015 HibernationDevice: RESUME=UUID=38664fac-0972-4e0f-8425-34b54ed3e248 InstallationDate: Installed on 2015-04-26 (4 days ago) InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Acer Aspire E3-112 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=10924b10-cb76-4f0b-8275-1a2874fa4b00 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456987] Re: beaglebone: warning cpu cpu0: cpu0 regulator not ready, retry during boot
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456987 Title: beaglebone: warning cpu cpu0: cpu0 regulator not ready, retry during boot Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: during boot, the logs are spammed with several repeated warning messages. Fix: apply the patches, recompile and reboot. Testcase: try booting with and without the patches applied and see if you can find the below warning messages in your logs. --- From dmesg: ... [2.583310] cpu cpu0: cpu0 regulator not ready, retry [2.588716] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.612048] bL_switcher_halve_cpus: no CPU pairing possible [2.786225] cpu cpu0: cpu0 regulator not ready, retry [2.791644] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.820171] cpu cpu0: cpu0 regulator not ready, retry [2.825579] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.880831] cpu cpu0: cpu0 regulator not ready, retry [2.891547] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [2.909836] cpu cpu0: cpu0 regulator not ready, retry [2.915227] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [7.437203] cpu cpu0: cpu0 regulator not ready, retry [7.470228] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.117120] cpu cpu0: cpu0 regulator not ready, retry [8.136001] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.368726] cpu cpu0: cpu0 regulator not ready, retry [8.383608] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.497935] cpu cpu0: cpu0 regulator not ready, retry [8.514540] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [8.604475] cpu cpu0: cpu0 regulator not ready, retry [8.619969] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.249407] cpu cpu0: cpu0 regulator not ready, retry [9.265457] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.393519] cpu cpu0: cpu0 regulator not ready, retry [9.411153] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.411513] cpu cpu0: cpu0 regulator not ready, retry [9.445954] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral [9.664395] cpu cpu0: cpu0 regulator not ready, retry [9.684708] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral ... that's because the cpufreq-cpu0 driver (that's built-in) requires the tsp65217 regulator driver that is compiled as a module (and not available during boot). While it's only a warning and it goes away when the rootfs is mounted (and the tps65217_regulator module is loaded), it's annoying and it spams the syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456873] Re: 3.13.0-53-generic breaks networking after 3-5 minutes
** Description changed: Description: Ubuntu 14.04.2 LTS Release: 14.04 I did the usual update with the graphical updater, it asked me to reboot. I did, after logging back in things looked OK for a few short minutes then networking completely stopped. After several warm reboots and a cold reboot I saw it was still doing - the same thing. I tried switching wired off and went to wireless, same - behavior. + the same thing. I tried switching wired off and went to wireless, (edit) + the wireless (I remembered later) did not work. Perhaps if I'd + disabled/reenabled networking and switched to wireless fast it may have. I found that I could Disable networking then reenable and networking would work again for a few minutes. I finally booted into the previous kernel 3.13.0-52-generic and it's working since I'm here. This same hardware, no changes has worked for around 2 years without issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-52-generic 3.13.0-52.86 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: diltonm4731 F pulseaudio - /dev/snd/controlC2: diltonm4731 F pulseaudio - /dev/snd/controlC0: diltonm4731 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: diltonm4731 F pulseaudio + /dev/snd/controlC2: diltonm4731 F pulseaudio + /dev/snd/controlC0: diltonm4731 F pulseaudio CurrentDesktop: Unity Date: Tue May 19 23:48:20 2015 MachineType: Hewlett-Packard h8-1520t ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=ef1a04ba-1a00-46ec-b972-60b27d1aa52d ro quiet splash acpi_osi=Linux RelatedPackageVersions: - linux-restricted-modules-3.13.0-52-generic N/A - linux-backports-modules-3.13.0-52-generic N/A - linux-firmware 1.127.12 + linux-restricted-modules-3.13.0-52-generic N/A + linux-backports-modules-3.13.0-52-generic N/A + linux-firmware 1.127.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.14 dmi.board.name: 2AD5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.asset.tag: 2MD30309RG dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.14:bd12/17/2012:svnHewlett-Packard:pnh8-1520t:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: h8-1520t dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456873 Title: 3.13.0-53-generic breaks networking after 3-5 minutes Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04.2 LTS Release: 14.04 I did the usual update with the graphical updater, it asked me to reboot. I did, after logging back in things looked OK for a few short minutes then networking completely stopped. After several warm reboots and a cold reboot I saw it was still doing the same thing. I tried switching wired off and went to wireless, (edit) the wireless (I remembered later) did not work. Perhaps if I'd disabled/reenabled networking and switched to wireless fast it may have. I found that I could Disable networking then reenable and networking would work again for a few minutes. I finally booted into the previous kernel 3.13.0-52-generic and it's working since I'm here. This same hardware, no changes has worked for around 2 years without issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-52-generic 3.13.0-52.86 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: diltonm4731 F pulseaudio /dev/snd/controlC2: diltonm4731 F pulseaudio /dev/snd/controlC0: diltonm4731 F pulseaudio CurrentDesktop: Unity Date: Tue May 19 23:48:20 2015 MachineType: Hewlett-Packard h8-1520t ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=ef1a04ba-1a00-46ec-b972-60b27d1aa52d ro quiet splash acpi_osi=Linux RelatedPackageVersions: linux-restricted-modules-3.13.0-52-generic N/A linux-backports-modules-3.13.0-52-generic N/A linux-firmware 1.127.12 SourcePackage: linux UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1456123] Re: [i915_bpo] Update driver code to 4.1-rc4 + backported fixes
** Summary changed: - [i915_bpo] Update driver code to 4.1-rc3 + backported fixes + [i915_bpo] Update driver code to 4.1-rc4 + backported fixes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456123 Title: [i915_bpo] Update driver code to 4.1-rc4 + backported fixes Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Bug description: Pull changes from 4.1-rcN, and add further backports for CHV SKL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 09:58 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456285] Re: Intel 7260 problems on Thinkpad T440s
That's not enough to say that the bug exists upstream, as it sounds like there's some other issue. I just tried this kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc4-unstable/linux- image-4.1.0-040100rc4-generic_4.1.0-040100rc4.201505181436_amd64.deb with Intel 7265 wifi (which uses the same driver) and it worked fine. Maybe give that one a try, and if you still have problems capture dmesg (e.g. run 'dmesg dmesg.txt') before you reboot and attach it to this bug report. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456285 Title: Intel 7260 problems on Thinkpad T440s Status in linux package in Ubuntu: Confirmed Bug description: Very intermittent and inconsistent wireless connections. Occasionally the indicator will show that the connection has been lost, but more often it seems that the indicator just shows low signal strength -- as it generally does even when the connection is working well. I'm pretty sure this is not an access-point problem because we have other devices using the same network without any problem. Here's some of the additional information that has been requested in other discussions of similar problems, although I don't fully understand what all these results mean. I have these three firmware files in /lib/firmware: [code] -rw-r--r-- 1 root root 683236 Nov 24 09:42 iwlwifi-7260-7.ucode -rw-r--r-- 1 root root 679780 Dec 1 09:16 iwlwifi-7260-8.ucode -rw-r--r-- 1 root root 680508 Dec 1 14:45 iwlwifi-7260-9.ucode [/code] dmesg | grep iwlwifi | grep firmware [code] [ 11.974201] iwlwifi :03:00.0: loaded firmware version 22.24.8.0 op_mode iwlmvm [/code] lspci -nn | grep 0280 [code] 03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b2] (rev 83) [/code] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-52-generic 3.13.0-52.86 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: timh 2011 F pulseaudio timh 2801 F pulseaudio /dev/snd/controlC0: timh 2011 F pulseaudio timh 2801 F pulseaudio CurrentDesktop: XFCE Date: Mon May 18 12:05:48 2015 HibernationDevice: RESUME=UUID=799c429f-edb4-438c-bbc7-386342199d23 InstallationDate: Installed on 2014-03-12 (432 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) MachineType: LENOVO 20ARCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-52-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-52-generic N/A linux-backports-modules-3.13.0-52-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2015-03-16 (63 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20ARCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20ARCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457141] Re: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker
*** This bug is a duplicate of bug 1457142 *** https://bugs.launchpad.net/bugs/1457142 ** This bug has been marked a duplicate of bug 1457142 linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457141 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456985] Re: Filesystem goes read-only while creating backups on HyperV
*** This bug is a duplicate of bug 1445195 *** https://bugs.launchpad.net/bugs/1445195 To fix this problem, you will also need https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454758 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456985 Title: Filesystem goes read-only while creating backups on HyperV Status in linux package in Ubuntu: Fix Committed Bug description: Because ubuntu-bug linux not works because I am on kernel 3.19.0-17, I create this report manually. Summary of problem: we create backups with HyperV of 4 linux virtual machines. There is 1 CentOS machine (XFS) and 3 Ubuntu 14.04 machines (EXT4). Problems occur on the Ubuntu machine only and have occurred on multiple hypervisors (physical machines). During the start or at the end of the creation of a snapshot, the filesystem switches to read- only mode. This happens at completely random moments: at least we are not able to detect a pattern. What we find weird is that the CentOS machine with XFS is not having any problems. What actions did we undertake to get rid of problem? We tried multiple backup strategies with HyperV, including snapshots and exports. When this was not successful, we were adviced by the #ubuntu-kernel chat channel to upgrade our kernel to 3.19.0-17 (coming from 3.13.0-52). The reasons that this could solve the problem is that hyperv backups require freeze and thaw methods (https://msdn.microsoft.com/en- us/library/aa384589%28v=vs.85%29.aspx). Unfortunately the problem did not go away. The message we get from dmesg when the filesystem goes read-only is as follows on the 3.19.0-17 kernel: [85630.239889] blk_update_request: I/O error, dev sda, sector 201697672 [85630.239931] Aborting journal on device sda1-8. [85630.253386] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal [85630.253428] EXT4-fs (sda1): Remounting filesystem read-only While it was as follows on the 3.13.0-52 kernel (different machine): [66392.076569] end_request: I/O error, dev sda, sector 65127256 [66392.076610] Aborting journal on device sda5-8. [66392.280052] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal [66392.280090] EXT4-fs (sda5): Remounting filesystem read-only [66392.482903] EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal System details: - Version signature: Ubuntu 3.19.0-17.17~14.04.1-generic 3.19.6 - lspci.log: http://paste.ubuntu.com/11242312/ - boot.log: http://paste.ubuntu.com/11242303/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
** Description changed: - There appears to be an issue with the use of overlayfs in the image. See - the attached screenshot for details. Immediately after that overlayfs - error the kernel panics. + [Impact] + overlayfs support doesn't work with kernels 3.18 which will, for example, break MAAS commissioning/deploying using trusty+hwe-v (when it exists). + + [Test Case] + Create custom trusty image using the vivid kernel and attempt to commission a node with MAAS using that image. + + [Regression Potential] + If the kernel detection code is buggy, it could regress functionality on older kernels (e.g. 3.13/3.16). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cloud-initramfs-tools source package in Trusty: In Progress Status in linux source package in Trusty: Invalid Status in cloud-initramfs-tools source package in Utopic: In Progress Status in linux source package in Utopic: New Bug description: [Impact] overlayfs support doesn't work with kernels 3.18 which will, for example, break MAAS commissioning/deploying using trusty+hwe-v (when it exists). [Test Case] Create custom trusty image using the vivid kernel and attempt to commission a node with MAAS using that image. [Regression Potential] If the kernel detection code is buggy, it could regress functionality on older kernels (e.g. 3.13/3.16). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456732] rizzo (amd64) - tests ran: 277, failed: 1
tests ran: 277, failed: 1; http://kernel.ubuntu.com/testing/rizzo__3.19.0-18.18__2015-05-20_05-37-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456732 Title: linux: 3.19.0-18.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1426589] Re: tc class statistics rates are all zero after upgrade to Trusty
** 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/1426589 Title: tc class statistics rates are all zero after upgrade to Trusty Status in iproute2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After upgrading an Ubuntu server from Lucid - Precise - Trusty the command: tc -s class show dev eth0 no longer shows rates for my classification bands. This worked in Lucid, but not sure if something changed, or if I need to set some system configuration to make it work again. My current non-working version is: $ dpkg -s iproute2 Package: iproute2 Status: install ok installed Priority: important Section: net Installed-Size: 1147 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: amd64 Multi-Arch: foreign Version: 3.12.0-2 Replaces: iproute Provides: arpd Depends: libc6 (= 2.14), libdb5.3 Recommends: libatm1 (= 2.4.1-17~), libxtables10 Suggests: iproute2-doc Conflicts: arpd, iproute ( 2013-1) Conffiles: /etc/iproute2/group 3aea2c0e0dd75e13a5f8f48f2936915f /etc/iproute2/ematch_map b91e7f9b26918449bade9573f8871d61 /etc/iproute2/rt_realms 7137bdf40e8d58c87ac7e3bba503767f /etc/iproute2/rt_tables a1313318d6778fe6b8c680248ef5a463 /etc/iproute2/rt_dsfield 4264d5c7c8298300185aa04e1a736934 /etc/iproute2/rt_protos 95ce0b4b5b79f5a8a45941fb418a904c /etc/iproute2/rt_scopes 6298b8df09e9bda23ea7da49021ca457 Description: networking and traffic control tools The iproute2 suite is a collection of utilities for networking and traffic control. . These tools communicate with the Linux kernel via the (rt)netlink interface, providing advanced features not available through the legacy net-tools commands 'ifconfig' and 'route'. Original-Maintainer: Debian iproute2 Maintainers ah-ipro...@debian.org Homepage: http://www.linux-foundation.org/en/Net:Iproute2 Here is the current output of the command, note that 'rate 0bit 0pps' is common to all classes, in Lucid this would produce non-zero values for active traffic: $ tc -s class show dev eth0 class htb 2:1 root rate 4000Kbit ceil 1Kbit burst 1600b cburst 1600b Sent 140162776 bytes 377793 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 23022 borrowed: 0 giants: 0 tokens: 46812 ctokens: 18725 class htb 2:2 parent 2:1 leaf 3: prio 0 rate 1000Kbit ceil 4000Kbit burst 1600b cburst 1600b Sent 2021584 bytes 6949 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 6505 borrowed: 189 giants: 0 tokens: 187250 ctokens: 46812 class htb 2:3 parent 2:1 leaf 4: prio 1 rate 2000Kbit ceil 4000Kbit burst 1600b cburst 1600b Sent 16695548 bytes 216855 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 216846 borrowed: 9 giants: 0 tokens: 94375 ctokens: 47187 class htb 2:4 parent 2:1 leaf 5: prio 2 rate 1000Kbit ceil 4000Kbit burst 1600b cburst 1600b Sent 2963040 bytes 46619 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 46619 borrowed: 0 giants: 0 tokens: 193250 ctokens: 48312 class htb 2:5 parent 2:1 leaf 6: prio 3 rate 1000Kbit ceil 4000Kbit burst 1600b cburst 1600b Sent 6 bytes 745 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 745 borrowed: 0 giants: 0 tokens: 183000 ctokens: 45750 class htb 2:6 parent 2:1 leaf 7: prio 4 rate 1000Kbit ceil 4000Kbit burst 1600b cburst 1600b Sent 80608262 bytes 79347 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 50544 borrowed: 13902 giants: 0 tokens: 190750 ctokens: 47687 class htb 2:7 parent 2:1 leaf 8: prio 5 rate 1000Kbit ceil 4000Kbit burst 1600b cburst 1600b Sent 37606539 bytes 26129 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 5617 borrowed: 8922 giants: 0 tokens: -178485 ctokens: 24056 class htb 2:8 parent 2:1 leaf 9: prio 6 rate 512000bit ceil 1000Kbit burst 1600b cburst 1600b Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 0 borrowed: 0 giants: 0 tokens: 390625 ctokens: 20 class htb 2:9 parent 2:1 leaf a: prio 7 rate 1000Kbit ceil 1000Kbit burst 1600b cburst 1600b Sent 167807 bytes 1149 pkt (dropped 0, overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 lended: 1149 borrowed: 0 giants: 0 tokens: 189875 ctokens: 189875 Did something change upstream to make the rates unavailable? Do I need to set some config to enable collection? Running the command as root does not make a difference. My kernel is: Linux
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
We now have test kernels available for Trusty, Utopic and Vivid. They are all available from: http://kernel.ubuntu.com/~jsalisbury/lp1445195/ It would be great if you could test the kernels for all releases. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: [Hyper-V] Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457142] [NEW] linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker
Public bug reported: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Tags: block-proposed-precise kernel-release-tracking-bug precise ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-precise ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Tags added: precise ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) = Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Invalid
[Kernel-packages] [Bug 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: cloud-initramfs-tools (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: cloud-initramfs-tools (Ubuntu Trusty) Assignee: (unassigned) = dann frazier (dannf) ** Changed in: cloud-initramfs-tools (Ubuntu Utopic) Assignee: (unassigned) = dann frazier (dannf) ** Changed in: cloud-initramfs-tools (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: cloud-initramfs-tools (Ubuntu Utopic) Status: New = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411294 Title: kernel panic during MAAS fastpath install of Vivid images Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cloud-initramfs-tools source package in Trusty: In Progress Status in linux source package in Trusty: Invalid Status in cloud-initramfs-tools source package in Utopic: In Progress Status in linux source package in Utopic: New Bug description: [Impact] overlayfs support doesn't work with kernels 3.18 which will, for example, break MAAS commissioning/deploying using trusty+hwe-v (when it exists). [Test Case] Create custom trusty image using the vivid kernel and attempt to commission a node with MAAS using that image. [Regression Potential] If the kernel detection code is buggy, it could regress functionality on older kernels (e.g. 3.13/3.16). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 09:58 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Packages available
All builds are complete, packages in this bug can be copied to -proposed. Derivative packages from packages here can be worked on, the following tracking bugs were opened for them: linux-keystone - bug 1457136 Backport packages from packages here can be worked on, the following tracking bugs were opened for them: linux-lts-trusty (precise1) - bug 1457141 ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:07 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:07 UTC kernel-stable-phase-changed:Wednesday, 20. May 2015 17:07 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Packages available
All builds are complete, packages in this bug can be copied to -proposed. Derivative packages from packages here can be worked on, the following tracking bugs were opened for them: linux-keystone - bug 1457137 Backport packages from packages here can be worked on, the following tracking bugs were opened for them: linux-lts-trusty (precise1) - bug 1457142 ** Description changed: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Wednesday, 20. May 2015 09:58 UTC + kernel-stable-phase:CopyToProposed + kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:07 UTC + kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:07 UTC + kernel-stable-phase-changed:Wednesday, 20. May 2015 17:07 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:07 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:07 UTC kernel-stable-phase-changed:Wednesday, 20. May 2015 17:07 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457141] [NEW] linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker
*** This bug is a duplicate of bug 1457142 *** https://bugs.launchpad.net/bugs/1457142 Public bug reported: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/package-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Platform QA Team (canonical-platform-qa) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Tags: block-proposed-precise kernel-release-tracking-bug precise ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-precise ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Tags added: precise ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/package-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New = In Progress ** Changed in: kernel-sru-workflow Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) = Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/package-testing Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/package-testing Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided = Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) = Canonical Kernel Team
[Kernel-packages] [Bug 1450584] Re: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm
On my website www.medinet.fr, I am using Ubuntu Server and Mono. I downgraded the serverto one CPU for having no crashes and waiting for the right fix. The said fixed one does not work at all. The server crashes eash 10 minutes max. Regards. M. Badr CHOUFFAI. .Net Software Architect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450584 Title: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: [Impact] The addition of the commit: http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2 Causes SIGSEGVs when running certain workloads on multi-cpu VMs. [Test Case] Mono test case here that causes the SIGSEGV https://bugzilla.xamarin.com/show_bug.cgi?id=29212 [Fix] These two commits are required for fixing this issue: https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27 -- Gradually since late March more and more users started to complain about frequent SIGSEGV crashes in our .net/mono application. Early April I started to investigate it actively. After eliminating possible native libraries, and testing various mono versions I discovered the crashes would occur more frequently on a vbox vm with multiple cpus configured. And discovered that the mono bug-18026.cs testcase would fairly consistently crash. At that point it was reported to the mono bug tracker. I finally got a break when we found a correlation with the kernel version. 3.13.0-46 didn't crash while 3.13.0-48,49 did. More and more users upgrade to these newer kernel versions and start running into issues, which explains the gradual increase in reports. Early this week I performed a full git bisect on the kernel between 3.13.0-46 and -48 and isolated the commit that seems to trigger the crashes. Namely http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2 At this point I don't know if the commit messed up something, or that mono simply handles it incorrectly. However, a few commits for linux 4.x seem to fix it: https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27 I applied these commits myself on top of commit 11f4e033, compiled and ran the testcase... didn't crash in the 200x test runs I did. Although I don't know if those two patches have unknown side-effects. I'm not an expert on the kernel, not even remotely. But I thought it would be nice to be able to point at a possible solution. My current test vm is a virtualbox vm 64bit installed using the 14.04.2 server iso running on an older i7 quad core Windows 7 64bit host. In the vm I've tested numerous mono and kernel combinations. Last test was with kernel 3.16.0-36 and 3.13.0-51 and mono 4.0.1, in which the problem still occurs. By now I've debugged the app using gdb several dozen times on various user setups, compiled mono half a dozen times, and then the 8x3h compile kernel bisect :) Speaking of down the rabbit-hole... So I'm pretty desperate for some expert to help me out here. :D Reference to mono bug report: https://bugzilla.xamarin.com/show_bug.cgi?id=29212 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-51-generic 3.13.0-51.84 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 30 18:53 seq crw-rw 1 root audio 116, 33 Apr 30 18:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [9.379188] init: plymouth-upstart-bridge main process ended, respawning Date: Thu Apr 30 19:45:43 2015 HibernationDevice: RESUME=UUID=b35ef328-166d-4476-a418-e7e80d22cb30 InstallationDate: Installed on 2015-04-22 (7 days ago) InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[Kernel-packages] [Bug 1425270] Re: CVE-2015-0275
** Changed in: linux (Ubuntu Vivid) 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/1425270 Title: CVE-2015-0275 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty 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-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New 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-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove 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-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New 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-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: New Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: Invalid Status in linux-manta source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid:
[Kernel-packages] [Bug 1240940] Re: Need support for Realtek Wifi card rtl8723be [10ec:b723]
The line in #78 that ends with modprobe. should continue like this: modprobe.d/rtl8723be.conf But you can always just create the file and put this in it: options rtl8723be fwlps=0 swlps=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1240940 Title: Need support for Realtek Wifi card rtl8723be [10ec:b723] Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: This device is appearing in some OEM machines, but driver is not yet available upstream. This bug is only for the initial support of this WiFi adapter, it's not working 100% well yet, please report new not working bug or contact upstream but not keep posting comments, thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1240940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457142] Re: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457142 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New Status in Kernel SRU Workflow prepare-package series: New 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Precise) Importance: Undecided = High ** Changed in: linux (Ubuntu Precise) Status: New = Triaged ** Changed in: linux (Ubuntu Precise) Assignee: (unassigned) = Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: [Hyper-V] Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Status in linux source package in Precise: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1444179] Re: add hid drivers to virtual kernel
The fix for this bug is now in the Utopic master-next branch, so it should be in the next kernel release. Here's that commit: commit 5ed2727f369394a9f1da5c082ab748bde1e043a2 Author: Brad Figg brad.f...@canonical.com Date: Mon May 11 12:38:35 2015 -0700 UBUNTU: hyper-v -- add hid and fb drivers to linux-virtual BugLink: http://bugs.launchpad.net/bugs/1444179 Signed-off-by: Brad Figg brad.f...@canonical.com Acked-by: Tim Gardner tim.gard...@canonical.com Acked-by: Andy Whitcroft andy.whitcr...@canonical.com The fix is also in the Trusty master-next branch: commit 04d144a3c2168bcc373ed4c4b5aef03a92297dfa Author: Brad Figg brad.f...@canonical.com Date: Tue May 12 10:23:10 2015 -0700 UBUNTU: hyper-v -- add hid and fb drivers to linux-virtual BugLink: http://bugs.launchpad.net/bugs/1444179 Signed-off-by: Brad Figg brad.f...@canonical.com Acked-by: Chris J. Arges chris.j.ar...@canonical.com Acked-by: Andy Whitcroft andy.whitcr...@canonical.com Signed-off-by: Brad Figg brad.f...@canonical.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1444179 Title: add hid drivers to virtual kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: Please move hid_hyperv and hyperv_fb to the -virtual kernel. Microsoft reports that these drivers are needed for connecting to Azure VM's using the Hyper-V manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC + kernel-stable-Certification-testing-end:Wednesday, 20. May 2015 20:00 UTC + kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 20:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-end:Wednesday, 20. May 2015 20:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v
Confirmed that commit a45de93 is missing from Vivid. I build a Vivid test kernel with this commit and posted it for download from: http://kernel.ubuntu.com/~jsalisbury/lp1423343/ Can you test this kernel and comfirm it resolves this bug? ** Changed in: linux (Ubuntu) Status: Fix Committed = Triaged ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New = Triaged ** Changed in: linux (Ubuntu Vivid) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) = Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423343 Title: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Bug description: Following patches are missing from ubuntu vivid 15.04 compared to latest upstream (linux-next) , please include them in ubuntu vivid , all the patches listed here are already upstream . /arch/x86/include/uapi/asm/hyperv.h 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1 /drivers/hv/hyperv_vmbus.h 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2 drivers/hv/vmbus_drv.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac 5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945 6. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c /drivers/hv/hv_snapshot.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6 /drivers/hv/hv_kvp.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4 /drivers/hv/hv_fcopy.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed /drivers/hv/channel.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314 /drivers/hv/channel_mgmt.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64 5. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7 /drivers/hv/hv_balloon.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8 /tools/hv/hv_vss_daemon.c 1. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e 2. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6 3. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9 4. http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd
[Kernel-packages] [Bug 1454758] Re: [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed
*** This bug is a duplicate of bug 1445195 *** https://bugs.launchpad.net/bugs/1445195 ** This bug has been marked a duplicate of bug 1445195 [Hyper-V] Kernel patches for storvsc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1454758 Title: [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed Status in linux package in Ubuntu: Triaged Status in linux source package in Precise: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Bug description: The following critical bugfix has been accepted into the upstream kernel. It is needed for 15.10, 15.02, 14.10, 14.04 and 14.04 HWE (and, by extension, 12.04 and 12.04 HWE). We have seen IHV drivers in the field throw errors and time out due to receiving SRB flags set when no data transfer is expected. storvsc: Set the SRB flags correctly when no data transfer is needed Set the SRB flags correctly when there is no data transfer. Without this change some IHV drivers will fail valid commands such as TEST_UNIT_READY. Commit http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=dc45708ca9988656d706940df5fd102672c5de92 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1444179] Re: add hid drivers to virtual kernel
** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1444179 Title: add hid drivers to virtual kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: Please move hid_hyperv and hyperv_fb to the -virtual kernel. Microsoft reports that these drivers are needed for connecting to Azure VM's using the Hyper-V manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:07 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:07 UTC kernel-stable-phase-changed:Wednesday, 20. May 2015 17:07 UTC + kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 18:56 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457180] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1457180 Title: btrfs crash Status in linux package in Ubuntu: Confirmed Bug description: btrfs filesystem crash when deleting files. dmesg shows: [41255.051093] kernel BUG at /build/buildd/linux-3.19.0/fs/btrfs/inode.c:3142! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed May 20 21:48:51 2015 InstallationDate: Installed on 2015-04-10 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=17624252-4d7d-4b40-8ee9-b3a78b7210ef ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:07 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:07 UTC kernel-stable-phase-changed:Wednesday, 20. May 2015 17:07 UTC - kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 18:56 UTC + kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:08 UTC ** Description changed: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-phase:CopyToProposed - kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:07 UTC - kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:07 UTC - kernel-stable-phase-changed:Wednesday, 20. May 2015 17:07 UTC - kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:08 UTC + kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC + kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC + kernel-stable-phase-changed:Wednesday, 20. May 2015 17:00 UTC + kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad (adconrad) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New = Confirmed ** Description changed: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC - kernel-stable-phase-changed:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC + kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC + kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC + kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC + proposed-announcement-sent:True + kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
For the apparmor trusty SRU, I reproduced the failure with the source for apparmor 2.8.95~2430-0ubuntu5.1 from trusty-updates with a hardware enablement kernel and confirmed that apparmor 2.8.95~2430-0ubuntu5.2 addresses the issue. I also verified that the rest of the apparmor regression tests passed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: In Progress Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Fix Released Bug description: [apparmor impact] This bug generates false positives when using the apparmor regression tests on the HWE kernels (utopic and newer), which means the kernel team needs to examine test output to ensure that addiitional failures didn't occur when testing new kernels. [apparmor test case] 1) install hwe kernel libapparmor-dev libdbus-1-dev attr 2) apt-get source apparmor 3) cd apparmor-2.8.95~2430/tests/regression/apparmor/ 4) make USE_SYSTEM=1 5) sudo bash unix_socket_file.sh If the bug has not been addressed, this test script will fail with the following messages: Error: unix_socket_file failed. Test 'socket file (dgram); confined server / access (w)' was expected to 'pass'. Reason for failure 'FAIL CLIENT - connect: Permission denied FAIL - poll timed out' Error: unix_socket_file failed. Test 'socket file (dgram); confined client w/ access (rw)' was expected to 'pass'. Reason for failure 'FAIL CLIENT - connect: Permission denied FAIL - poll timed out' and a return code of 2 (echo $?). If it has been fixed it should return silently, with a return code of 0. [apparmor regression potential] The patch for this bug only affects the test suite for apparmor, which is a loosening of the policy used in the specific failing testcases. There should be no effect on the apparmor implementation proper from this fix. [apparmor additional info] This testsuite is run as part of the test-apparmor.py test script from lp:qa-regression-testing, and used as part of the kernel update process, but is useful for ensuring that apparmor is functioning properly. [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64
[Kernel-packages] [Bug 1456976] Re: linux: 3.13.0-53.89 -proposed tracker
Planning to release this kernel to -security, as it covers a regression in the last -security release. ** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) = Adam Conrad (adconrad) ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456976 Title: linux: 3.13.0-53.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-53.89 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 09:58 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 17:00 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 19:01 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 19:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 19:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
I built Trusty, Utopic and Vivid test kernels, with the commits requested in this bug, any pre-reqs and commit dc45708ca per bug 1454758 . The details are as follows: Trusty: dc45708 storvsc: Set the SRB flags correctly when no data transfer is needed - Added per bug 1454758 b9ec3a5 scsi: storvsc: Increase the ring buffer size f458aad scsi: storvsc: Size the queue depth based on the ringbuffer size 0147dab scsi: storvsc: Always send on the selected outgoing channel 5117b93 scsi: storvsc: Retrieve information about the capability of the target 8de5807 scsi: storvsc: Fix a bug in copy_from_bounce_buffer() aaced99 scsi: storvsc: Don't assume that the scatterlist is not chained be0cf6c scsi: storvsc: Set the tablesize based on the information given by the d61031e Drivers: hv: vmbus: Support a vmbus API for efficiently sending page arrays Pre-req needed for all releases. 011a7c3 Drivers: hv: vmbus: Cleanup the packet send path - Pre-req only needed for Trusty. Utopic: dc45708 storvsc: Set the SRB flags correctly when no data transfer is needed - Added per bug 1454758 b9ec3a5 scsi: storvsc: Increase the ring buffer size f458aad scsi: storvsc: Size the queue depth based on the ringbuffer size 0147dab scsi: storvsc: Always send on the selected outgoing channel 5117b93 scsi: storvsc: Retrieve information about the capability of the target 8de5807 scsi: storvsc: Fix a bug in copy_from_bounce_buffer() aaced99 scsi: storvsc: Don't assume that the scatterlist is not chained be0cf6c scsi: storvsc: Set the tablesize based on the information given by the d61031e Drivers: hv: vmbus: Support a vmbus API for efficiently sending page arrays Pre-req needed for all releases. Vivid: dc45708 storvsc: Set the SRB flags correctly when no data transfer is needed - Added per bug 1454758 b9ec3a5 scsi: storvsc: Increase the ring buffer size f458aad scsi: storvsc: Size the queue depth based on the ringbuffer size 0147dab scsi: storvsc: Always send on the selected outgoing channel 5117b93 scsi: storvsc: Retrieve information about the capability of the target 8de5807 scsi: storvsc: Fix a bug in copy_from_bounce_buffer() aaced99 scsi: storvsc: Don't assume that the scatterlist is not chained be0cf6c scsi: storvsc: Set the tablesize based on the information given by the d61031e Drivers: hv: vmbus: Support a vmbus API for efficiently sending page arrays Pre-req needed for all releases. The test kernels can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1445195/ Can you test these kernels and post back the results? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: [Hyper-V] Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1405807] Re: linux-lts-utopic-tools-common package is empty
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New = Fix Committed ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1405807 Title: linux-lts-utopic-tools-common package is empty Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Bug description: Hi, I installed linux-lts-utopic-tools-common under Ubuntu 14.04.1 and hoped to find the same binaries in it as under Ubuntu utopic, but the package is empty. I guess, do_tools must be set to true somewhere, but I don't know exactly where. Under utopic, it looks like this: /. /usr /usr/share /usr/share/man /usr/share/man/man1 /usr/share/man/man1/cpupower-frequency-set.1.gz /usr/share/man/man1/perf-inject.1.gz /usr/share/man/man1/cpupower-idle-info.1.gz /usr/share/man/man1/perf-buildid-cache.1.gz /usr/share/man/man1/perf-diff.1.gz /usr/share/man/man1/cpupower-monitor.1.gz /usr/share/man/man1/perf-mem.1.gz /usr/share/man/man1/cpupower-idle-set.1.gz /usr/share/man/man1/perf-report.1.gz /usr/share/man/man1/perf.1.gz /usr/share/man/man1/usbip.8.gz /usr/share/man/man1/perf-timechart.1.gz /usr/share/man/man1/perf-script-perl.1.gz /usr/share/man/man1/cpupower-info.1.gz /usr/share/man/man1/perf-help.1.gz /usr/share/man/man1/perf-archive.1.gz /usr/share/man/man1/perf-buildid-list.1.gz /usr/share/man/man1/perf-kmem.1.gz /usr/share/man/man1/perf-top.1.gz /usr/share/man/man1/perf-trace.1.gz /usr/share/man/man1/perf-stat.1.gz /usr/share/man/man1/usbipd.8.gz /usr/share/man/man1/cpupower-set.1.gz /usr/share/man/man1/perf-bench.1.gz /usr/share/man/man1/perf-sched.1.gz /usr/share/man/man1/perf-annotate.1.gz /usr/share/man/man1/perf-record.1.gz /usr/share/man/man1/perf-script-python.1.gz /usr/share/man/man1/cpupower-frequency-info.1.gz /usr/share/man/man1/perf-kvm.1.gz /usr/share/man/man1/perf-script.1.gz /usr/share/man/man1/perf-test.1.gz /usr/share/man/man1/perf-probe.1.gz /usr/share/man/man1/perf-lock.1.gz /usr/share/man/man1/perf-evlist.1.gz /usr/share/man/man1/cpupower.1.gz /usr/share/man/man1/perf-list.1.gz /usr/share/man/man8 /usr/share/man/man8/x86_energy_perf_policy.8.gz /usr/share/man/man8/turbostat.8.gz /usr/share/doc /usr/share/doc/linux-tools-common /usr/share/doc/linux-tools-common/copyright /usr/share/doc/linux-tools-common/changelog.Debian.gz /usr/bin /usr/bin/turbostat /usr/bin/usbip /usr/bin/x86_energy_perf_policy /usr/bin/perf /usr/bin/usbipd /usr/bin/cpupower To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1405807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455937] Re: HP 1018 not seen after upgrade to Ubuntu 15.04
Before I get into bisection, I did another experiment. I also have a macbookpro running Ubuntu 15.04 same kernel. I plugged the printer into the macbook and it is properly recognized. I'm attaching the relevant portions of the syslog from the workstation and the macbook. They are quite a bit different. The workstation, is the original machine that lost the printer after the upgrade. The macbook is running the same OS/kernel but sees the printer. ** Attachment added: syslog on machine that worked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455937/+attachment/4401190/+files/macbook-log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1455937 Title: HP 1018 not seen after upgrade to Ubuntu 15.04 Status in linux package in Ubuntu: Confirmed Bug description: My usb connect Hp Laserjet 1018 worked on Ubuntu 14.04 but after a update through 14.10 and then 15.04, CUPS no longer sees it. I did not test in 14.10 since I went right to 15.04. Here is some of the requested info $ lsmod |grep usb btusb 32768 0 usb_storage69632 1 uas bluetooth 491520 22 bnep,btusb,rfcomm usbhid 53248 0 hid 110592 2 hid_generic,usbhid $ tail -f /var/log/syslog May 17 10:58:07 orac kernel: [ 229.204084] usb 1-12: new high-speed USB device number 17 using xhci_hcd May 17 10:58:07 orac kernel: [ 229.408652] usb 1-12: New USB device found, idVendor=03f0, idProduct=4117 May 17 10:58:07 orac kernel: [ 229.408654] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 17 10:58:07 orac kernel: [ 229.408656] usb 1-12: Product: HP LaserJet 1018 May 17 10:58:07 orac kernel: [ 229.408657] usb 1-12: Manufacturer: Hewlett-Packard May 17 10:58:07 orac kernel: [ 229.408658] usb 1-12: SerialNumber: KP2920Z May 17 10:58:07 orac logger: loading HP Device 001 017 May 17 10:58:07 orac logger: loading hp_laserjet_1018 firmware 001 017 May 17 10:58:11 orac kernel: [ 233.074425] WARNING! power/level is deprecated; use power/control instead May 17 10:58:11 orac udev-configure-printer: add /devices/pci:00/:00:14.0/usb1/1-12 May 17 10:58:11 orac udev-configure-printer: device devpath is /devices/pci:00/:00:14.0/usb1/1-12 May 17 10:58:11 orac udev-configure-printer: Device vendor/product is 03F0:4117 May 17 10:58:17 orac udev-configure-printer: Failed to fetch Device ID May 17 10:58:23 orac /lib/udev/hplj1018: foo2zjs: Missing HP LaserJet 1018 firmware file /lib/firmware/hp/sihp1018.dl May 17 10:58:23 orac /lib/udev/hplj1018: foo2zjs: ...read foo2zjs installation instructions and run ./getweb 1018 May 17 10:58:28 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:28 orac python3: io/hpmud/musb.c 2212: invalid product id string ret=-7 May 17 10:58:33 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:33 orac python3: io/hpmud/musb.c 2217: invalid serial id string ret=-7 May 17 10:58:38 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:38 orac python3: io/hpmud/musb.c 2081: invalid product id string ret=-7 May 17 10:58:43 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:43 orac python3: io/hpmud/musb.c 2086: invalid serial id string ret=-7 May 17 10:58:48 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:48 orac python3: io/hpmud/musb.c 2091: invalid manufacturer string ret=-7 May 17 10:58:48 orac /hp-firmware: hp-firmware[4977]: error: Invalid USB Device ID or USB bus ID. No device found. May 17 10:58:48 orac systemd[1]: Reached target Printer. May 17 10:58:48 orac systemd[1]: Starting Printer. May 17 10:58:53 orac kernel: [ 275.303504] usblp 1-12:1.0: usblp0: USB Bidirectional printer dev 17 if 0 alt 0 proto 2 vid 0x03F0 pid 0x4117 May 17 10:58:53 orac kernel: [ 275.303536] usbcore: registered new interface driver usblp May 17 10:58:53 orac colord-sane: io/hpmud/musb.c 2076: Invalid usb_open: Permission denied $ lsusb Bus 004 Device 002: ID 8087:8000 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8008 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard Bus 001 Device 011: ID 0566:4006 Monterey International Corp. Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB
[Kernel-packages] [Bug 1455937] Re: HP 1018 not seen after upgrade to Ubuntu 15.04
Correspond ing syslog from workstation ** Attachment added: syslog on non-working machine https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455937/+attachment/4401191/+files/workstation-log ** 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/1455937 Title: HP 1018 not seen after upgrade to Ubuntu 15.04 Status in linux package in Ubuntu: Confirmed Bug description: My usb connect Hp Laserjet 1018 worked on Ubuntu 14.04 but after a update through 14.10 and then 15.04, CUPS no longer sees it. I did not test in 14.10 since I went right to 15.04. Here is some of the requested info $ lsmod |grep usb btusb 32768 0 usb_storage69632 1 uas bluetooth 491520 22 bnep,btusb,rfcomm usbhid 53248 0 hid 110592 2 hid_generic,usbhid $ tail -f /var/log/syslog May 17 10:58:07 orac kernel: [ 229.204084] usb 1-12: new high-speed USB device number 17 using xhci_hcd May 17 10:58:07 orac kernel: [ 229.408652] usb 1-12: New USB device found, idVendor=03f0, idProduct=4117 May 17 10:58:07 orac kernel: [ 229.408654] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3 May 17 10:58:07 orac kernel: [ 229.408656] usb 1-12: Product: HP LaserJet 1018 May 17 10:58:07 orac kernel: [ 229.408657] usb 1-12: Manufacturer: Hewlett-Packard May 17 10:58:07 orac kernel: [ 229.408658] usb 1-12: SerialNumber: KP2920Z May 17 10:58:07 orac logger: loading HP Device 001 017 May 17 10:58:07 orac logger: loading hp_laserjet_1018 firmware 001 017 May 17 10:58:11 orac kernel: [ 233.074425] WARNING! power/level is deprecated; use power/control instead May 17 10:58:11 orac udev-configure-printer: add /devices/pci:00/:00:14.0/usb1/1-12 May 17 10:58:11 orac udev-configure-printer: device devpath is /devices/pci:00/:00:14.0/usb1/1-12 May 17 10:58:11 orac udev-configure-printer: Device vendor/product is 03F0:4117 May 17 10:58:17 orac udev-configure-printer: Failed to fetch Device ID May 17 10:58:23 orac /lib/udev/hplj1018: foo2zjs: Missing HP LaserJet 1018 firmware file /lib/firmware/hp/sihp1018.dl May 17 10:58:23 orac /lib/udev/hplj1018: foo2zjs: ...read foo2zjs installation instructions and run ./getweb 1018 May 17 10:58:28 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:28 orac python3: io/hpmud/musb.c 2212: invalid product id string ret=-7 May 17 10:58:33 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:33 orac python3: io/hpmud/musb.c 2217: invalid serial id string ret=-7 May 17 10:58:38 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:38 orac python3: io/hpmud/musb.c 2081: invalid product id string ret=-7 May 17 10:58:43 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:43 orac python3: io/hpmud/musb.c 2086: invalid serial id string ret=-7 May 17 10:58:48 orac python3: io/hpmud/musb.c 151: unable get_string_descriptor -7: Resource temporarily unavailable May 17 10:58:48 orac python3: io/hpmud/musb.c 2091: invalid manufacturer string ret=-7 May 17 10:58:48 orac /hp-firmware: hp-firmware[4977]: error: Invalid USB Device ID or USB bus ID. No device found. May 17 10:58:48 orac systemd[1]: Reached target Printer. May 17 10:58:48 orac systemd[1]: Starting Printer. May 17 10:58:53 orac kernel: [ 275.303504] usblp 1-12:1.0: usblp0: USB Bidirectional printer dev 17 if 0 alt 0 proto 2 vid 0x03F0 pid 0x4117 May 17 10:58:53 orac kernel: [ 275.303536] usbcore: registered new interface driver usblp May 17 10:58:53 orac colord-sane: io/hpmud/musb.c 2076: Invalid usb_open: Permission denied $ lsusb Bus 004 Device 002: ID 8087:8000 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8008 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard Bus 001 Device 011: ID 0566:4006 Monterey International Corp. Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub Bus 001 Device 012: ID 04e6:5410 SCM Microsystems, Inc. SCR35xx Smart Card Reader Bus 001 Device 009: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card Reader Bus 001 Device 006: ID 0424:2602 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 004: ID 0424:2502 Standard Microsystems
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
It sounds like the following commit is also needed to solve bug 1456985 : commit dc45708ca9988656d706940df5fd102672c5de92 Author: K. Y. Srinivasan k...@microsoft.com Date: Fri May 1 11:03:02 2015 -0700 storvsc: Set the SRB flags correctly when no data transfer is needed That commit was requested in bug 1454758 . I'm going to mark bug 1454758 as a duplicate of this bug and build all of the commits requested in that bug and this bug together in a test kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: [Hyper-V] Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457180] [NEW] btrfs crash
Public bug reported: btrfs filesystem crash when deleting files. dmesg shows: [41255.051093] kernel BUG at /build/buildd/linux-3.19.0/fs/btrfs/inode.c:3142! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed May 20 21:48:51 2015 InstallationDate: Installed on 2015-04-10 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=17624252-4d7d-4b40-8ee9-b3a78b7210ef ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1457180 Title: btrfs crash Status in linux package in Ubuntu: Confirmed Bug description: btrfs filesystem crash when deleting files. dmesg shows: [41255.051093] kernel BUG at /build/buildd/linux-3.19.0/fs/btrfs/inode.c:3142! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed May 20 21:48:51 2015 InstallationDate: Installed on 2015-04-10 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=17624252-4d7d-4b40-8ee9-b3a78b7210ef ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449401] Re: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno
3.16.0-38 seems to work on Thinkpad Yoga S3 (14), Broadwell... -36/-37 didn't work, -34 worked too. Ubuntu 14.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449401 Title: After 14.10 updates to kernel 3.16.0-36, system is not booting, resulting in black screen due to NULL pointer in intel_ring_init_seqno Status in linux package in Ubuntu: Invalid Status in linux source package in Utopic: Fix Released Bug description: This happens everytime I boot after updating kernel from 3.16.0-34 to 3.16.0-36. Keeping 3.16.0-34 still works. Blackscreen is illuminated. I do not see any splash screen, nor X. Failsafe mode works, booting with nomodeset works (but it's slow). When this happens, on the next reboot I do see some BUG: lines in syslog, like: Apr 27 21:01:54 portable-alex kernel: [2.457904] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 27 21:01:54 portable-alex kernel: [2.457911] IP: [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457913] PGD 51b93d067 PUD 51b8ec067 PMD 0 Apr 27 21:01:54 portable-alex kernel: [2.457916] Oops: 0010 [#1] SMP Apr 27 21:01:54 portable-alex kernel: [2.457918] Modules linked in: rtsx_pci_sdmmc i915(+) e1000e ahci ptp i2c_algo_bit drm_kms_helper libahci pps_core psmouse drm rtsx_pci wmi video Apr 27 21:01:54 portable-alex kernel: [2.457926] CPU: 0 PID: 128 Comm: systemd-udevd Not tainted 3.16.0-36-generic #48-Ubuntu Apr 27 21:01:54 portable-alex kernel: [2.457929] Hardware name: LENOVO 20BXCTO1WW/20BXCTO1WW, BIOS JBET45WW (1.10 ) 02/03/2015 Apr 27 21:01:54 portable-alex kernel: [2.457930] task: 88051be6bd20 ti: 88051b9a8000 task.ti: 88051b9a8000 Apr 27 21:01:54 portable-alex kernel: [2.457932] RIP: 0010:[] [ (null)] (null) Apr 27 21:01:54 portable-alex kernel: [2.457934] RSP: 0018:88051b9ab890 EFLAGS: 00010286 Apr 27 21:01:54 portable-alex kernel: [2.457936] RAX: 0246 RBX: 88051bbb1928 RCX: 0001 Apr 27 21:01:54 portable-alex kernel: [2.457937] RDX: 0001 RSI: effe RDI: 88051bbb1928 Apr 27 21:01:54 portable-alex kernel: [2.457938] RBP: 88051b9ab8b0 R08: 88051bbb R09: 0246 Apr 27 21:01:54 portable-alex kernel: [2.457940] R10: 880529403900 R11: 811a6ddf R12: effe Apr 27 21:01:54 portable-alex kernel: [2.457941] R13: 88051bbb R14: effe R15: 88051bf90800 Apr 27 21:01:54 portable-alex kernel: [2.457942] FS: 7f8127b4f880() GS:88053dc0() knlGS: Apr 27 21:01:54 portable-alex kernel: [2.457944] CS: 0010 DS: ES: CR0: 80050033 Apr 27 21:01:54 portable-alex kernel: [2.457945] CR2: CR3: 00051b942000 CR4: 003407f0 Apr 27 21:01:54 portable-alex kernel: [2.457947] DR0: DR1: DR2: Apr 27 21:01:54 portable-alex kernel: [2.457948] DR3: DR6: fffe0ff0 DR7: 0400 Apr 27 21:01:54 portable-alex kernel: [2.457949] Stack: Apr 27 21:01:54 portable-alex kernel: [2.457950] c02499fd 88051bbb1928 88051bbb7148 88051bbb7148 Apr 27 21:01:54 portable-alex kernel: [2.457953] 88051b9ab8e8 c022e5b7 efff effe Apr 27 21:01:54 portable-alex kernel: [2.457955] 88051bbb 88051bbb 88051bbb 88051b9ab910 Apr 27 21:01:54 portable-alex kernel: [2.457957] Call Trace: Apr 27 21:01:54 portable-alex kernel: [2.457977] [c02499fd] ? intel_ring_init_seqno+0x3d/0xb0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.457991] [c022e5b7] i915_gem_init_seqno+0x77/0xc0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458002] [c022e629] i915_gem_set_seqno+0x29/0x60 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458013] [c022fdcd] i915_gem_init_hw+0x12d/0x380 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458022] [c0230075] i915_gem_init+0x55/0x1d0 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458039] [c02956a2] i915_driver_load+0xe32/0x1030 [i915] Apr 27 21:01:54 portable-alex kernel: [2.458042] [813a05e8] ? kobject_uevent_env+0x178/0x690 Apr 27 21:01:54 portable-alex kernel: [2.458046] [814cf087] ? get_device+0x17/0x30 Apr 27 21:01:54 portable-alex kernel: [2.458048] [814d4af5] ? klist_class_dev_get+0x15/0x20 Apr 27 21:01:54 portable-alex kernel: [2.458051] [817773b8] ? klist_node_init+0x38/0x60 Apr 27 21:01:54 portable-alex kernel: [2.458054] [81777476] ?
[Kernel-packages] [Bug 1456732] Re: linux: 3.19.0-18.18 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress = Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/package-testing Status: Confirmed = Fix Released ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed = Invalid ** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/promote-to-security Status: New = Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New = Confirmed ** Description changed: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC - kernel-stable-phase:Verification Testing - kernel-stable-phase-changed:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC + kernel-stable-phase:CopyToUpdates + kernel-stable-Promote-to-updates-start:Wednesday, 20. May 2015 22:09 UTC + kernel-stable-phase-changed:Wednesday, 20. May 2015 22:09 UTC + kernel-stable-Certification-testing-end:Wednesday, 20. May 2015 22:09 UTC + kernel-stable-Regression-testing-end:Wednesday, 20. May 2015 22:09 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456732 Title: linux: 3.19.0-18.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC kernel-stable-phase:CopyToUpdates kernel-stable-Promote-to-updates-start:Wednesday, 20. May 2015 22:09 UTC kernel-stable-phase-changed:Wednesday, 20. May 2015 22:09 UTC kernel-stable-Certification-testing-end:Wednesday, 20. May 2015 22:09 UTC kernel-stable-Regression-testing-end:Wednesday, 20. May 2015 22:09 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1446316] Re: Vivid update to 3.19.4 and 3.19.5 stable release
This bug was fixed in the package linux - 3.19.0-18.18 --- linux (3.19.0-18.18) vivid; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1456732 [ Upstream Kernel Changes ] * Revert drm/i915: remove intel_pipe_set_base() (v4) - LP: #1453593 linux (3.19.0-17.17) vivid; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1452000 [ Damien Lespiau ] * SAUCE: i915_bpo: drm/i915/skl: Fix stepping check for a couple of W/As - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Implement WaDisableVFUnitClockGating - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add the INIT power domain to the MISC I/O power well - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Fix the CTRL typo in the DPLL_CRTL1 defines - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Make the Misc I/O power well part of the PLLS domain - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Deinit/init the display at suspend/resume - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Change CDCLK behind PCU's back - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: gen6+ platforms support runtime PM - LP: #1449469 [ Imre Deak ] * SAUCE: i915_bpo: drm/i915/gen9: fix PIPE_CONTROL flush for VS_INVALIDATE - LP: #1449469 [ Leann Ogasawara ] * [Config] Set CONFIG_XEN_MAX_DOMAIN_MEMORY defaults [ Matt Roper ] * SAUCE: i915_bpo: drm/i915: Switch to full atomic helpers for plane updates/disable, take two - LP: #1449469 [ Sonika Jindal ] * SAUCE: i915_bpo: drm/i915/skl: Allow universal planes to position - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Support for 90/270 rotation - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add back HDMI translation table - LP: #1449469 [ Stefan Bader ] * SAUCE: vesafb: Set mtrr:3 (write-combining) as default - LP: #1434581 [ Timo Aaltonen ] * SAUCE: Call i915_bpo specific functions from the hda driver - LP: #1449464 * SAUCE: i915_bpo: Use get_display_clock_speed - LP: #1449469 * SAUCE: i915_bpo: Add a few register definitions - LP: #1449469 [ Upstream Kernel Changes ] * Revert sparc/PCI: Clip bridge windows to fit in upstream windows - LP: #1446316 * Revert PM / hibernate: avoid unsafe pages in e820 reserved regions - LP: #1446316 * Revert libceph: use memalloc flags for net IO - LP: #1446316 * Revert net: Reset secmark when scrubbing packet - LP: #1451996 * ASoC: da732x: Fix control-less DAPM routes - LP: #1446316 * ASoC: ak4671: Fix control-less DAPM routes - LP: #1446316 * ASoC: sn95031: Fix control-less DAPM routes - LP: #1446316 * ASoC: sgtl5000: remove useless register write clearing CHRGPUMP_POWERUP - LP: #1446316 * ASoC: pcm1681: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: cs4271: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: es8238: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8960: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: tas5086: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8731: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm2000: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8903: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8904: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: ak4641: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: adav80x: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8955: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9712: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9713: Fix wrong value references for boolean kctl - LP: #1446316 * virtio_balloon: set DRIVER_OK before using device - LP: #1446316 * virtio-balloon: do not call blocking ops when !TASK_RUNNING - LP: #1446316 * clockevents: sun5i: Fix setup_irq init sequence - LP: #1446316 * regmap: regcache-rbtree: Fix present bitmap resize - LP: #1446316 * regmap: introduce regmap_name to fix syscon regmap trace events - LP: #1446316 * clocksource: efm32: Fix a NULL pointer dereference - LP: #1446316 * tcm_fc: missing curly braces in ft_invl_hw_context() - LP: #1446316 * tcm_qla2xxx: Fix incorrect use of __transport_register_session - LP: #1446316 * nl80211: ignore HT/VHT capabilities without QoS/WMM - LP: #1446316 * mac80211: disable u-APSD queues by default - LP: #1446316 * mac80211: drop unencrypted frames in mesh fwding - LP: #1446316 * mac80211: count interfaces correctly for combination checks - LP: #1446316 * iwlwifi: mvm: rs: fix BT Coex check to look at the correct ant - LP: #1446316 * iwlwifi: fix max_ht_ampdu_exponent for older devices
[Kernel-packages] [Bug 1441335] Re: PCI: Don't clear ASPM bits when the FADT declares it's unsupported
This bug was fixed in the package linux - 3.19.0-18.18 --- linux (3.19.0-18.18) vivid; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1456732 [ Upstream Kernel Changes ] * Revert drm/i915: remove intel_pipe_set_base() (v4) - LP: #1453593 linux (3.19.0-17.17) vivid; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1452000 [ Damien Lespiau ] * SAUCE: i915_bpo: drm/i915/skl: Fix stepping check for a couple of W/As - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Implement WaDisableVFUnitClockGating - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add the INIT power domain to the MISC I/O power well - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Fix the CTRL typo in the DPLL_CRTL1 defines - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Make the Misc I/O power well part of the PLLS domain - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Deinit/init the display at suspend/resume - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Change CDCLK behind PCU's back - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: gen6+ platforms support runtime PM - LP: #1449469 [ Imre Deak ] * SAUCE: i915_bpo: drm/i915/gen9: fix PIPE_CONTROL flush for VS_INVALIDATE - LP: #1449469 [ Leann Ogasawara ] * [Config] Set CONFIG_XEN_MAX_DOMAIN_MEMORY defaults [ Matt Roper ] * SAUCE: i915_bpo: drm/i915: Switch to full atomic helpers for plane updates/disable, take two - LP: #1449469 [ Sonika Jindal ] * SAUCE: i915_bpo: drm/i915/skl: Allow universal planes to position - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Support for 90/270 rotation - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add back HDMI translation table - LP: #1449469 [ Stefan Bader ] * SAUCE: vesafb: Set mtrr:3 (write-combining) as default - LP: #1434581 [ Timo Aaltonen ] * SAUCE: Call i915_bpo specific functions from the hda driver - LP: #1449464 * SAUCE: i915_bpo: Use get_display_clock_speed - LP: #1449469 * SAUCE: i915_bpo: Add a few register definitions - LP: #1449469 [ Upstream Kernel Changes ] * Revert sparc/PCI: Clip bridge windows to fit in upstream windows - LP: #1446316 * Revert PM / hibernate: avoid unsafe pages in e820 reserved regions - LP: #1446316 * Revert libceph: use memalloc flags for net IO - LP: #1446316 * Revert net: Reset secmark when scrubbing packet - LP: #1451996 * ASoC: da732x: Fix control-less DAPM routes - LP: #1446316 * ASoC: ak4671: Fix control-less DAPM routes - LP: #1446316 * ASoC: sn95031: Fix control-less DAPM routes - LP: #1446316 * ASoC: sgtl5000: remove useless register write clearing CHRGPUMP_POWERUP - LP: #1446316 * ASoC: pcm1681: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: cs4271: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: es8238: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8960: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: tas5086: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8731: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm2000: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8903: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8904: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: ak4641: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: adav80x: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8955: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9712: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9713: Fix wrong value references for boolean kctl - LP: #1446316 * virtio_balloon: set DRIVER_OK before using device - LP: #1446316 * virtio-balloon: do not call blocking ops when !TASK_RUNNING - LP: #1446316 * clockevents: sun5i: Fix setup_irq init sequence - LP: #1446316 * regmap: regcache-rbtree: Fix present bitmap resize - LP: #1446316 * regmap: introduce regmap_name to fix syscon regmap trace events - LP: #1446316 * clocksource: efm32: Fix a NULL pointer dereference - LP: #1446316 * tcm_fc: missing curly braces in ft_invl_hw_context() - LP: #1446316 * tcm_qla2xxx: Fix incorrect use of __transport_register_session - LP: #1446316 * nl80211: ignore HT/VHT capabilities without QoS/WMM - LP: #1446316 * mac80211: disable u-APSD queues by default - LP: #1446316 * mac80211: drop unencrypted frames in mesh fwding - LP: #1446316 * mac80211: count interfaces correctly for combination checks - LP: #1446316 * iwlwifi: mvm: rs: fix BT Coex check to look at the correct ant - LP: #1446316 * iwlwifi: fix max_ht_ampdu_exponent for older devices
[Kernel-packages] [Bug 1457142] Re: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457142 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: New 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457142] Packages available
All builds are complete, packages in this bug can be copied to -proposed. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457142 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Thursday, 21. May 2015 00:27 UTC kernel-stable-Promote-to-proposed-start:Thursday, 21. May 2015 00:27 UTC kernel-stable-phase-changed:Thursday, 21. May 2015 00:27 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457142] Packages available
All builds are complete, packages in this bug can be copied to -proposed. ** Description changed: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 + kernel-stable-phase:CopyToProposed + kernel-stable-Prepare-package-end:Thursday, 21. May 2015 00:27 UTC + kernel-stable-Promote-to-proposed-start:Thursday, 21. May 2015 00:27 UTC + kernel-stable-phase-changed:Thursday, 21. May 2015 00:27 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457142 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Thursday, 21. May 2015 00:27 UTC kernel-stable-Promote-to-proposed-start:Thursday, 21. May 2015 00:27 UTC kernel-stable-phase-changed:Thursday, 21. May 2015 00:27 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457142] Re: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 kernel-stable-phase:CopyToProposed - kernel-stable-Prepare-package-end:Thursday, 21. May 2015 00:27 UTC - kernel-stable-Promote-to-proposed-start:Thursday, 21. May 2015 00:27 UTC - kernel-stable-phase-changed:Thursday, 21. May 2015 00:27 UTC - kernel-stable-Promote-to-proposed-end:Thursday, 21. May 2015 00:37 UTC + kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 22:27 UTC + kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 22:27 UTC + kernel-stable-phase-changed:Wednesday, 20. May 2015 22:27 UTC + kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 22:37 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457142 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 22:27 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 22:27 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 22:37 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 21. May 2015 00:43 UTC kernel-stable-Verification-testing-start:Thursday, 21. May 2015 00:43 UTC kernel-stable-Certification-testing-start:Thursday, 21. May 2015 00:43 UTC kernel-stable-Security-signoff-start:Thursday, 21. May 2015 00:43 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 21. May 2015 00:43 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456732] Re: linux: 3.19.0-18.18 -proposed tracker
** Description changed: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC kernel-stable-phase:CopyToUpdates kernel-stable-Promote-to-updates-start:Wednesday, 20. May 2015 22:09 UTC kernel-stable-phase-changed:Wednesday, 20. May 2015 22:09 UTC kernel-stable-Certification-testing-end:Wednesday, 20. May 2015 22:09 UTC kernel-stable-Regression-testing-end:Wednesday, 20. May 2015 22:09 UTC + kernel-stable-Promote-to-updates-end:Thursday, 21. May 2015 01:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456732 Title: linux: 3.19.0-18.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: This bug is for tracking the 3.19.0-18.18 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 kernel-stable-Prepare-package-start:Tuesday, 19. May 2015 17:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 03:56 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 03:59 UTC kernel-stable-Verification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Certification-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-start:Wednesday, 20. May 2015 05:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 20. May 2015 05:00 UTC kernel-stable-Security-signoff-end:Wednesday, 20. May 2015 11:00 UTC kernel-stable-phase:CopyToUpdates kernel-stable-Promote-to-updates-start:Wednesday, 20. May 2015 22:09 UTC kernel-stable-phase-changed:Wednesday, 20. May 2015 22:09 UTC kernel-stable-Certification-testing-end:Wednesday, 20. May 2015 22:09 UTC kernel-stable-Regression-testing-end:Wednesday, 20. May 2015 22:09 UTC kernel-stable-Promote-to-updates-end:Thursday, 21. May 2015 01:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1456732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1457142] Packages available
All builds are complete, packages in this bug can be copied to -proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457142 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow package-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Thursday, 21. May 2015 00:27 UTC kernel-stable-Promote-to-proposed-start:Thursday, 21. May 2015 00:27 UTC kernel-stable-phase-changed:Thursday, 21. May 2015 00:27 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar
This bug was fixed in the package linux - 3.19.0-18.18 --- linux (3.19.0-18.18) vivid; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1456732 [ Upstream Kernel Changes ] * Revert drm/i915: remove intel_pipe_set_base() (v4) - LP: #1453593 linux (3.19.0-17.17) vivid; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1452000 [ Damien Lespiau ] * SAUCE: i915_bpo: drm/i915/skl: Fix stepping check for a couple of W/As - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Implement WaDisableVFUnitClockGating - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add the INIT power domain to the MISC I/O power well - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Fix the CTRL typo in the DPLL_CRTL1 defines - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Make the Misc I/O power well part of the PLLS domain - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Deinit/init the display at suspend/resume - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Change CDCLK behind PCU's back - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: gen6+ platforms support runtime PM - LP: #1449469 [ Imre Deak ] * SAUCE: i915_bpo: drm/i915/gen9: fix PIPE_CONTROL flush for VS_INVALIDATE - LP: #1449469 [ Leann Ogasawara ] * [Config] Set CONFIG_XEN_MAX_DOMAIN_MEMORY defaults [ Matt Roper ] * SAUCE: i915_bpo: drm/i915: Switch to full atomic helpers for plane updates/disable, take two - LP: #1449469 [ Sonika Jindal ] * SAUCE: i915_bpo: drm/i915/skl: Allow universal planes to position - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Support for 90/270 rotation - LP: #1449469 * SAUCE: i915_bpo: drm/i915/skl: Add back HDMI translation table - LP: #1449469 [ Stefan Bader ] * SAUCE: vesafb: Set mtrr:3 (write-combining) as default - LP: #1434581 [ Timo Aaltonen ] * SAUCE: Call i915_bpo specific functions from the hda driver - LP: #1449464 * SAUCE: i915_bpo: Use get_display_clock_speed - LP: #1449469 * SAUCE: i915_bpo: Add a few register definitions - LP: #1449469 [ Upstream Kernel Changes ] * Revert sparc/PCI: Clip bridge windows to fit in upstream windows - LP: #1446316 * Revert PM / hibernate: avoid unsafe pages in e820 reserved regions - LP: #1446316 * Revert libceph: use memalloc flags for net IO - LP: #1446316 * Revert net: Reset secmark when scrubbing packet - LP: #1451996 * ASoC: da732x: Fix control-less DAPM routes - LP: #1446316 * ASoC: ak4671: Fix control-less DAPM routes - LP: #1446316 * ASoC: sn95031: Fix control-less DAPM routes - LP: #1446316 * ASoC: sgtl5000: remove useless register write clearing CHRGPUMP_POWERUP - LP: #1446316 * ASoC: pcm1681: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: cs4271: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: es8238: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8960: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: tas5086: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8731: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm2000: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8903: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8904: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: ak4641: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: adav80x: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm8955: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9712: Fix wrong value references for boolean kctl - LP: #1446316 * ASoC: wm9713: Fix wrong value references for boolean kctl - LP: #1446316 * virtio_balloon: set DRIVER_OK before using device - LP: #1446316 * virtio-balloon: do not call blocking ops when !TASK_RUNNING - LP: #1446316 * clockevents: sun5i: Fix setup_irq init sequence - LP: #1446316 * regmap: regcache-rbtree: Fix present bitmap resize - LP: #1446316 * regmap: introduce regmap_name to fix syscon regmap trace events - LP: #1446316 * clocksource: efm32: Fix a NULL pointer dereference - LP: #1446316 * tcm_fc: missing curly braces in ft_invl_hw_context() - LP: #1446316 * tcm_qla2xxx: Fix incorrect use of __transport_register_session - LP: #1446316 * nl80211: ignore HT/VHT capabilities without QoS/WMM - LP: #1446316 * mac80211: disable u-APSD queues by default - LP: #1446316 * mac80211: drop unencrypted frames in mesh fwding - LP: #1446316 * mac80211: count interfaces correctly for combination checks - LP: #1446316 * iwlwifi: mvm: rs: fix BT Coex check to look at the correct ant - LP: #1446316 * iwlwifi: fix max_ht_ampdu_exponent for older devices
[Kernel-packages] [Bug 1457142] Re: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: New = In Progress ** Changed in: kernel-sru-workflow/certification-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New = Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New = Confirmed ** Description changed: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 - kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 22:27 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 22:27 UTC - kernel-stable-phase-changed:Wednesday, 20. May 2015 22:27 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 22:37 UTC + kernel-stable-phase:Verification Testing + kernel-stable-phase-changed:Thursday, 21. May 2015 00:43 UTC + kernel-stable-Verification-testing-start:Thursday, 21. May 2015 00:43 UTC + kernel-stable-Certification-testing-start:Thursday, 21. May 2015 00:43 UTC + kernel-stable-Security-signoff-start:Thursday, 21. May 2015 00:43 UTC + proposed-announcement-sent:True + kernel-stable-Regression-testing-start:Thursday, 21. May 2015 00:43 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1457142 Title: linux-lts-trusty: 3.13.0-53.89~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow package-testing series: Confirmed 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New Bug description: This bug is for tracking the 3.13.0-53.89~precise1 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 kernel-stable-Prepare-package-start:Wednesday, 20. May 2015 17:01 UTC kernel-stable-master-bug:1456976 kernel-stable-Prepare-package-end:Wednesday, 20. May 2015 22:27 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. May 2015 22:27 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 20. May 2015 22:37 UTC kernel-stable-phase:Verification Testing kernel-stable-phase-changed:Thursday, 21. May 2015 00:43 UTC kernel-stable-Verification-testing-start:Thursday, 21. May 2015 00:43 UTC kernel-stable-Certification-testing-start:Thursday, 21. May 2015 00:43 UTC kernel-stable-Security-signoff-start:Thursday, 21. May 2015 00:43 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 21. May 2015 00:43 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1457142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
