[Kernel-packages] [Bug 1323882] Re: Dell M4800 kernel crashes every few hours
Why is this assigned to bcmwl? OP problem seems to be the kernel thinking that no RAM is available (making OOM Killer kill everything). Even if 32GB RAM are present the kernel command line has all these weird options: "irqpoll maxcpus=1 nousb memmap=exactmap memmap=577K@4K memmap=130476K@737280K elfcorehdr=867756K memmap=28K#3121240K memmap=396K#3292788K memmap=1068K#3316692K" Question is: who put that there any why? I bet this is causing (or at least contributing to) the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1323882 Title: Dell M4800 kernel crashes every few hours Status in “bcmwl” package in Ubuntu: Incomplete Bug description: Every few hours my laptop screen locks up, the fans max out, and it needs a hard power reset. I'm running Ubuntu -14.04 on a Dell Precision M4800. The memory test passed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 uname -a Linux noel-m4800 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux /var/log/kern.log is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1323882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1332384] Re: [Dell Inspiron 5547] Unable to scroll with the clickpad
Also affect 201401-14528 Dell Inspiron 5447 It works with the latest mainline kernel as well (3.16.0-rc4) xinput list with 3.16.0-rc4 ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=10 [slave pointer (2)] ⎜ ↳ DLL063E:00 06CB:2934 id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ Integrated_Webcam_HD id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ Dell WMI hotkeys id=15 [slave keyboard (3)] ** Summary changed: - [Dell Inspiron 5547] Unable to scroll with the clickpad + [Dell Inspiron 5547/5447] Unable to scroll with the clickpad ** Tags added: 201401-14528 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1332384 Title: [Dell Inspiron 5547/5447] Unable to scroll with the clickpad Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: New Bug description: CID: 201401-14530 Dell Inspiron 5547 The Clickpad on this system was detected as a SynPS/2 Synaptics TouchPad, I'm not sure if this is expected, but the scrolling feature is not working on 14.04 + update(both two fingers scrolling and one finger edge scrolling). Also, the "disable while typing", three and four fingers tapping are not working as well. Steps: 1. Install 14.04 + update (3.13.0-29), boot to desktop 2. Test the touchpad Expected result: * At least edge scrolling should work Actual result: * Only left / right click, one-finger single / double tapping works. Debugging information: ubuntu@201401-14530:~$ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DLL063E:00 06CB:2934id=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1609 F pulseaudio /dev/snd/controlC1: ubuntu 1609 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Jun 19 22:04:37 2014 HibernationDevice: RESUME=UUID=7454cf26-0b42-44d7-ac45-01977170fad5 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=3dfa4af3-a788-4fbe-b7db-b895afb04d77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 0598GM
[Kernel-packages] [Bug 1332437] Re: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900]
Also affects 201401-14528 Dell Inspiron 5447 with the same graphic card, 3.16.0-rc4 would fix this. ** Summary changed: - [Dell Inspiron 5547] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900] + [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900] ** Tags added: 201401-14528 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1332437 Title: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900] Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: New Bug description: CID: 201401-14542 Dell Inspiron 5547 This issue is similar to bug 1332379, but with I+A config, Brightness cannot be controlled without the open-source driver as well. Steps: 1. Install 14.04 + update (3.13.0-29) + fglrx 2. Try to adjust the screen brightness with hotkeys and "Brightness and Lock" applet Expected result: * Screen brightness could be adjusted in both ways. Actual result: * Unable to control screen brightness, the brightness indicator would change according to key press on the hotkeys Debugging information: ubuntu@201401-14542:~$ ls /sys/class/backlight/ acpi_video0 intel_backlight ubuntu@201401-14542:~$ grep -r . /proc/acpi/ /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S3*disabled pci::00:1c.0 /proc/acpi/wakeup:PEGP S4*disabled pci::03:00.0 /proc/acpi/wakeup:PEGA S4*disabled /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled ubuntu@201401-14542:~$ dmesg | grep 'ACPI: Video' [ 16.334321] ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no) [ 16.335955] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1689 F pulseaudio /dev/snd/controlC1: ubuntu 1689 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jun 20 03:14:08 2014 HibernationDevice: RESUME=UUID=202f89f5-b720-4ad7-b55e-dce344e24df1 InstallationDate: Installed on 2014-06-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=7cc3cad1-0797-443f-b3d3-5484a70cc255 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1041790] Re: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0
** Attachment added: "error log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1041790/+attachment/4147886/+files/error3.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0" run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1332437] Re: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900]
Tweak in comment #7 works on 201401-14528 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1332437 Title: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900] Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: New Bug description: CID: 201401-14542 Dell Inspiron 5547 This issue is similar to bug 1332379, but with I+A config, Brightness cannot be controlled without the open-source driver as well. Steps: 1. Install 14.04 + update (3.13.0-29) + fglrx 2. Try to adjust the screen brightness with hotkeys and "Brightness and Lock" applet Expected result: * Screen brightness could be adjusted in both ways. Actual result: * Unable to control screen brightness, the brightness indicator would change according to key press on the hotkeys Debugging information: ubuntu@201401-14542:~$ ls /sys/class/backlight/ acpi_video0 intel_backlight ubuntu@201401-14542:~$ grep -r . /proc/acpi/ /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S3*disabled pci::00:1c.0 /proc/acpi/wakeup:PEGP S4*disabled pci::03:00.0 /proc/acpi/wakeup:PEGA S4*disabled /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled ubuntu@201401-14542:~$ dmesg | grep 'ACPI: Video' [ 16.334321] ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no) [ 16.335955] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1689 F pulseaudio /dev/snd/controlC1: ubuntu 1689 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jun 20 03:14:08 2014 HibernationDevice: RESUME=UUID=202f89f5-b720-4ad7-b55e-dce344e24df1 InstallationDate: Installed on 2014-06-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=7cc3cad1-0797-443f-b3d3-5484a70cc255 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1332379] Re: [Dell Inspiron 5547/5447] Unable to control brightness with Intel Haswell GPU
Also affect 201401-14528 Dell Inspiron 5447 This could be fixed by 3.16.0-rc4 as well The GRUB tweak mentioned in comment #7 of bug 1332437 "video.use_native_backlight=1" works. So I think this issue is well explained in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332437/comments/8 Maybe we could set this as a duplicated one after we confirm these two bugs are identical. ** Summary changed: - [Dell Inspiron 5547] Unable to control brightness + [Dell Inspiron 5547/5447] Unable to control brightness with Intel Haswell GPU ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: 201401-14528 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1332379 Title: [Dell Inspiron 5547/5447] Unable to control brightness with Intel Haswell GPU Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: New Bug description: CID: 201401-14530 Dell Inspiron 5547 Unable to control the brightness on this system. Steps: 1. Install 14.04 + update (3.13.0-29), boot to desktop 2. Try to adjust the screen brightness with hotkeys and "Brightness and Lock" applet Expected result: * Screen brightness could be adjusted in both ways. Actual result: * Unable to control screen brightness, the brightness indicator would change according to key press on the hotkeys Debugging information: ubuntu@201401-14530:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201401-14530:~$ grep -r . /proc/acpi /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S3*disabled pci::00:1c.0 /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled ubuntu@201401-14530:~$ dmesg | grep 'ACPI: Video' [ 13.689138] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1609 F pulseaudio /dev/snd/controlC1: ubuntu 1609 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Jun 19 21:47:08 2014 HibernationDevice: RESUME=UUID=7454cf26-0b42-44d7-ac45-01977170fad5 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=3dfa4af3-a788-4fbe-b7db-b895afb04d77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn0598GM:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333638] Re: [Dell Vostro 5470] Unable to control brightness with the Intel GPU / nVidia GPU + proprietary driver
** Also affects: hwe-next/trusty Importance: Undecided Status: New ** Also affects: hwe-next/utopic Importance: Undecided Status: New ** Changed in: hwe-next/utopic Status: New => Invalid ** Changed in: hwe-next/trusty Assignee: (unassigned) => Edward Lin (airken) ** Changed in: hwe-next/trusty 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/1333638 Title: [Dell Vostro 5470] Unable to control brightness with the Intel GPU / nVidia GPU + proprietary driver Status in HWE Next Project: Invalid Status in HWE Next trusty series: New Status in HWE Next utopic series: Invalid Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201307-14038 Dell Vostro 5470 The brightness cannot be adjusted when running on Intel GPU This bug is similar to bug 1332437, but this one is a I+N system Steps: 1. Install 14.04 + update (3.13.0-29), boot to desktop 2. Try to adjust the screen brightness with hotkeys and "Brightness and Lock" applet Expected result: * Screen brightness could be adjusted in both ways. Actual result: * Unable to control screen brightness, the brightness indicator would change according to key press on the hotkeys Debugging information: ubuntu@201307-14038:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201307-14038:~$ grep -r . /proc/acpi /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:GLAN S4*disabled /proc/acpi/wakeup:EHC1 S4*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S4*disabled /proc/acpi/wakeup:XHC S4*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP02 S4*disabled pci::00:1c.1 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP03 S4*disabled pci::00:1c.2 /proc/acpi/wakeup:PXSX S4*enabled pci::07:00.0 /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::08:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled ubuntu@201307-14038:~$ dmesg | grep 'ACPI: Video' [4.106881] ACPI: Video Device [PEGP] (multi-head: no rom: yes post: no) [4.121059] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1533 F pulseaudio /dev/snd/controlC0: ubuntu 1533 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Jun 24 06:08:39 2014 HibernationDevice: RESUME=UUID=a006ee47-418d-4b00-a823-81ac84d903e4 InstallationDate: Installed on 2010-01-01 (1635 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 5470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=d578d54f-0310-4907-83ba-ffb8e071368e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/02/2013:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1333638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1250401] Re: [Dell Inspiron 5737] brightness could not be controlled by the indicator applet "System settings -> Brightness and Lock"" but sysfs works
** Also affects: hwe-next/trusty Importance: Undecided Status: New ** Also affects: hwe-next/utopic Importance: Undecided Status: New ** Changed in: hwe-next/utopic Status: New => Invalid ** Changed in: hwe-next/trusty Assignee: (unassigned) => Edward Lin (airken) ** Changed in: hwe-next/trusty 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/1250401 Title: [Dell Inspiron 5737] brightness could not be controlled by the indicator applet "System settings -> Brightness and Lock"" but sysfs works Status in HWE Next Project: Invalid Status in HWE Next trusty series: New Status in HWE Next utopic series: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: New Status in “linux” source package in Trusty: Triaged Status in “linux-lts-raring” source package in Trusty: Invalid Bug description: Dell Inspiron 5737 (CID 201305-13636) with ubuntu 12.04.3 steps to reproduce the bug: 1. install 12.04.3 on this machine 2. update the system via update manager to make the system up-to-date 3. click the upper-right indicator to launch the "System settings -> Brightness and Lock" applet 4. try to adjust the brightness bar to control the brightness expected result: the brightness could be adjusted by the bar actual result: screen brightness has no response -- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: ALC283 Analog [ALC283 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1708 F pulseaudio /dev/snd/controlC0: ubuntu 1708 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0x9071 irq 62' Mixer name : 'Intel Haswell HDMI' Components : 'HDA:80862807,80860101,0010' Controls : 21 Simple ctrls : 3 Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0x90714000 irq 63' Mixer name : 'Realtek ALC283' Components : 'HDA:10ec0283,102805ec,0012' Controls : 16 Simple ctrls : 7 Date: Tue Nov 12 05:49:09 2013 HibernationDevice: RESUME=UUID=d809501f-7daa-47a2-8299-1844cd4d75cc InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Dell Inc. Inspiron 5737 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=fdac94e0-b7ee-402a-a160-6567b65501c6 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.79.7 SourcePackage: linux-lts-raring StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04X8RP dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/30/2013:svnDellInc.:pnInspiron5737:pvrA05:rvnDellInc.:rn04X8RP:rvrX01:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 5737 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1250401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1332437] Re: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900]
** Also affects: hwe-next/trusty Importance: Undecided Status: New ** Also affects: hwe-next/utopic Importance: Undecided Status: New ** Changed in: hwe-next/utopic Status: New => Invalid ** Changed in: hwe-next/trusty Assignee: (unassigned) => Edward Lin (airken) ** Changed in: hwe-next/trusty 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/1332437 Title: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900] Status in HWE Next Project: Invalid Status in HWE Next trusty series: New Status in HWE Next utopic series: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: New Bug description: CID: 201401-14542 Dell Inspiron 5547 This issue is similar to bug 1332379, but with I+A config, Brightness cannot be controlled without the open-source driver as well. Steps: 1. Install 14.04 + update (3.13.0-29) + fglrx 2. Try to adjust the screen brightness with hotkeys and "Brightness and Lock" applet Expected result: * Screen brightness could be adjusted in both ways. Actual result: * Unable to control screen brightness, the brightness indicator would change according to key press on the hotkeys Debugging information: ubuntu@201401-14542:~$ ls /sys/class/backlight/ acpi_video0 intel_backlight ubuntu@201401-14542:~$ grep -r . /proc/acpi/ /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S3*disabled pci::00:1c.0 /proc/acpi/wakeup:PEGP S4*disabled pci::03:00.0 /proc/acpi/wakeup:PEGA S4*disabled /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled ubuntu@201401-14542:~$ dmesg | grep 'ACPI: Video' [ 16.334321] ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no) [ 16.335955] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1689 F pulseaudio /dev/snd/controlC1: ubuntu 1689 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jun 20 03:14:08 2014 HibernationDevice: RESUME=UUID=202f89f5-b720-4ad7-b55e-dce344e24df1 InstallationDate: Installed on 2014-06-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=7cc3cad1-0797-443f-b3d3-5484a70cc255 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338946] [NEW] linux: 2.6.32-64.127 -proposed tracker
Public bug reported: This bug is for tracking the 2.6.32-64.127 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, 08. July 2014 08:49 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 08. July 2014 08:49 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-lbm 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: New ** Affects: kernel-sru-workflow/prepare-package-ports-meta 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 Lucid) Importance: Medium Status: New ** Tags: kernel-release-tracking-bug lucid ** Tags added: kernel-release-tracking-bug ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Tags added: lucid ** 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-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-ports-meta 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-lbm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned) =
[Kernel-packages] [Bug 1298119] Re: CVE-2014-0131
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) 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/1298119 Title: CVE-2014-0131 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-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: Won't Fix Status in “linux-lts-backport-natty” package in Ubuntu: Won't Fix 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Won't Fix Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New 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-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: Use-after-free vulnerability in the skb_segment function in net/core/skbuff.c in the Linux kernel through 3.13.6 allows attackers to obtain sensitive information from kernel memory by leveraging the absence of a certain orphaning operati
[Kernel-packages] [Bug 1333605] Re: CVE-2014-0203
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) 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/1333605 Title: CVE-2014-0203 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-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid 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-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix 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-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: 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-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix 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 “li
[Kernel-packages] [Bug 1334985] Re: CVE-2014-0206
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Precise) 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/1334985 Title: CVE-2014-0206 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: 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-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid 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-fsl-imx51” 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: New 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 Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: 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-fsl-imx51” 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-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-fsl-imx51” 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug desc
[Kernel-packages] [Bug 1322068] Re: Turn on bluetooth with Fn+F12 not working
Antoine Sibold: "Is there more to do?" Yes. "Are there other Kernels between 3.5.0-52.79 and 3.8.0-19.28?" Yes. ** 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/1322068 Title: Turn on bluetooth with Fn+F12 not working Status in “linux” package in Ubuntu: Incomplete Bug description: After installing Ubuntu 14.04 LTS, i cannot turn on Bluetooth with Fn+F12 as usual. I have tested other versions of Ubuntu the results are: Ubuntu 12.04.LTS it works Ubuntu 12.04.1 LTS it works Ubuntu 12.04.2 LTS it works Ubuntu 12.04.3 LTS it does not working Ubuntu 12.04.4 LTS it does not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibold 1910 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 09:31:55 2014 HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab InstallationDate: Installed on 2014-05-17 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336278] Re: linux: 3.13.0-31.55 -proposed tracker
*** This bug is a duplicate of bug 1338524 *** https://bugs.launchpad.net/bugs/1338524 ** This bug has been marked a duplicate of bug 1338524 linux: 3.13.0-32.56 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1336278 Title: linux: 3.13.0-31.55 -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: 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress 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-31.55 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, 01. July 2014 14:11 UTC kernel-stable-Prepare-package-end:Wednesday, 02. July 2014 04:12 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. July 2014 04:12 UTC ppa-package-testing-start:Wednesday, 02. July 2014 04:12 UTC kernel-stable-Promote-to-proposed-end:Thursday, 03. July 2014 16:17 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 03. July 2014 18:04 UTC kernel-stable-Verification-testing-start:Thursday, 03. July 2014 18:04 UTC kernel-stable-Certification-testing-start:Thursday, 03. July 2014 18:04 UTC kernel-stable-Security-signoff-start:Thursday, 03. July 2014 18:04 UTC kernel-stable-Regression-testing-start:Thursday, 03. July 2014 18:04 UTC kernel-stable-Certification-testing-end:Thursday, 03. July 2014 20:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1336278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1006446] Re: nfs4 causes enormous load in ubuntu-server making it unusable
*** This bug is a duplicate of bug 879334 *** https://bugs.launchpad.net/bugs/879334 Is this bug solved?? I am having similar issues with my Ubuntu server 12.04.04 64 bits. I am using ldap authentication with NFS to mount users home. The server uses 2 gigabyte ethernet using bonding and there are 20 users and have 2x4 processors with 12 Gb ram (it is an ACER gateway gr320 f1 server). I change my server to the 12.04 becouse we were using an old version (7.10) and I was having some problems, but since the change, the clients are too slow. I notice that the server processors load it's high and I think this bug could be afecting me. Sorry about my english and thank you in advance :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1006446 Title: nfs4 causes enormous load in ubuntu-server making it unusable Status in “linux” package in Ubuntu: Triaged Status in “nfs-utils” package in Ubuntu: Confirmed Bug description: Problem: -- I just had to remove ubuntu server 12.04 to install redhat enterprise linux 6. The intermittent slowness was completely unacceptable for the users, who have workstations with /home mounted with nfs4 on this server. The mail server, also accesses the /home because the /home/$USER/Maildir directories are there. Using nfs4, the kernel nfs threads caused enormous load. The users had frozen desktops (greyed out windows) and mail slowed or arrived days later as a result. With RHEL6, all nfs4 problems are completely gone. I used the exact same /etc/exports file, and the same settings and mount options on the workstations, the same number of nfs threads. Both the redhat and ubuntu systems are KVM virtual guests on an redhat 6 virtual host (one of 3 actually). The storage backend is a very fast equallogic array, which exports iscsi targets to the virtual hosts. I am sorry, but I have to conclude the current nfs4 implementation of ubuntu server 12.04 is NOT fit for use. A complete university department suffered for weeks while I tried to solve the problems with ubuntu, but in the end it was decided to install redhat instead, re-using the same iscsi targets for system, home and data. A missed chance for ubuntu... Therefore I urge Canonical's people to classify this bug as critical. Also I think quality assurance should have caught this bug before shipping. Analysis LOAD: The nfs threads cause the kernel to use enormous amounts of 'sy' time as measured in top. I will attach a sample of top's output, of a particular _quiet_ time on the network. Load is 7.82. On busier moments, the load went through the roof, beyond 50 and further. It consumes actual CPU cycles. Each thread consumes upto 30% of a cpu core. I enabled 128 threads. rx an tx block sizes are 32768 on the clients. Both server and clients used async, both on redhat and ubuntu. SYSTEM vs IO-WAIT: The replacement redhat system can surely be overloaded, but then it does not consume CPU cycles doing so. Top does report high load, but it spends in in the 'wa' state. This indicates it is simply waiting for its backend iscsi devices to complete writes. I tested this by simultaneously letting all workstations write multi-gigabyte files with dd to /home. On ubuntu, the nfs threads spend their time in 'sy', doing who-knows-what. LOGS: Nothing at all appears in the logs. But when I set bitwise debug options in the /proc/sys/sunrpc/*debug files, lots of log entries appear. Those seem like normal NFS protocol messages to me though. I also tried to discover what was happening with wireshark, but the traffic looks like normal nfs4 traffic to me. SLOWNESS: That is the thing. The ubuntu nfs server is actually NOT slow at all. During my dd tests, it wrote half a gigabyte per second to its iscsi backends. It's _throughput_ is better than that of the redhat server. As far as I can tell, it falls down because it makes client side processes that want to do IO wait on other writes. A simple 'ls' has to wait until a write has been completed. And both server and client used async nfs. People's firefoxes freeze all the time because firefox need to read and write a lot to its cache and other files in the .mozilla directory. The dovecot imap server almost grinds to a halt trying to write all those little files in people's /home/$USER/Maildir's. The problems go on and on. Basically, a complete network of workstations is almost unusable because of this. Upfront tests were done of course, but showed only the excellent throughput but not the appalling `waiting´ behaviour. With redhat 6 there is no such problem. SITUATION: People use their own, and each others linux workstations for science, doing la
[Kernel-packages] [Bug 1336203] Re: linux: 3.11.0-25.43 -proposed tracker
*** This bug is a duplicate of bug 1338556 *** https://bugs.launchpad.net/bugs/1338556 ** This bug has been marked a duplicate of bug 1338556 linux: 3.11.0-26.44 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1336203 Title: linux: 3.11.0-25.43 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-25.43 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, 01. July 2014 09:02 UTC kernel-stable-Prepare-package-end:Wednesday, 02. July 2014 15:58 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 02. July 2014 15:58 UTC ppa-package-testing-start:Wednesday, 02. July 2014 15:58 UTC kernel-stable-Promote-to-proposed-end:Thursday, 03. July 2014 16:31 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 03. July 2014 18:03 UTC kernel-stable-Verification-testing-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Certification-testing-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Security-signoff-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Regression-testing-start:Thursday, 03. July 2014 18:03 UTC kernel-stable-Regression-testing-end:Monday, 07. July 2014 14:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1336203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305371] Re: [Dell Inspiron 1525] suspend/resume failure
Mark smith, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305371 Title: [Dell Inspiron 1525] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: suspend/resume failed. restart required to bring back system ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ashraf 1484 F pulseaudio Date: Thu Apr 10 06:30:00 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=f4caffe3-3165-417b-bd56-386b8e3852b8 InstallationDate: Installed on 2014-03-29 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. Inspiron 1525 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=26592a1f-092c-4949-9107-771865219fcd ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux Title: [Dell Inc. Inspiron 1525] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338177] Re: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295]
RichardNeill, could you please comment to the source (Ubuntu repository or upstream) and which version of fglrx specifically you tested? ** Tags removed: bios-outdated-4105 ** Tags added: latest-bios-4105 ** Description changed: I've just installed Utopic, and my machine is really slow to boot. + + WORKAROUND: Use Radeon driver. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC3: rjn2642 F pulseaudio - /dev/snd/controlC2: rjn2642 F pulseaudio - /dev/snd/controlC0: rjn2642 F pulseaudio - /dev/snd/controlC1: rjn2642 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC3: rjn2642 F pulseaudio + /dev/snd/controlC2: rjn2642 F pulseaudio + /dev/snd/controlC0: rjn2642 F pulseaudio + /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: - eth0 no wireless extensions. - - eth1 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + eth1 no wireless extensions. + + lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: - + SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338177 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] Status in “linux” package in Ubuntu: Incomplete Bug description: I've just installed Utopic, and my machine is really slow to boot. WORKAROUND: Use Radeon driver. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679
[Kernel-packages] [Bug 1332437] Re: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900]
@Po-Hsu, Can you try this kernel for bug 1333638 / bug 1250401 / bug 1332437 to see if it fixes the backlight issue ? http://people.canonical.com/~airken/bug/lp1332437/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1332437 Title: [Dell Inspiron 5547/5447] Unable to contorl brightness with fglrx driver on AMD Radeon R7 M260 [1002:6900] Status in HWE Next Project: Invalid Status in HWE Next trusty series: New Status in HWE Next utopic series: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: New Bug description: CID: 201401-14542 Dell Inspiron 5547 This issue is similar to bug 1332379, but with I+A config, Brightness cannot be controlled without the open-source driver as well. Steps: 1. Install 14.04 + update (3.13.0-29) + fglrx 2. Try to adjust the screen brightness with hotkeys and "Brightness and Lock" applet Expected result: * Screen brightness could be adjusted in both ways. Actual result: * Unable to control screen brightness, the brightness indicator would change according to key press on the hotkeys Debugging information: ubuntu@201401-14542:~$ ls /sys/class/backlight/ acpi_video0 intel_backlight ubuntu@201401-14542:~$ grep -r . /proc/acpi/ /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S3*disabled pci::00:1c.0 /proc/acpi/wakeup:PEGP S4*disabled pci::03:00.0 /proc/acpi/wakeup:PEGA S4*disabled /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled ubuntu@201401-14542:~$ dmesg | grep 'ACPI: Video' [ 16.334321] ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no) [ 16.335955] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1689 F pulseaudio /dev/snd/controlC1: ubuntu 1689 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jun 20 03:14:08 2014 HibernationDevice: RESUME=UUID=202f89f5-b720-4ad7-b55e-dce344e24df1 InstallationDate: Installed on 2014-06-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=7cc3cad1-0797-443f-b3d3-5484a70cc255 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 08KNCD dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn08KNCD:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1328594] Re: [Lenovo ThinkPad Edge E320] Wifi disappears ubuntu 13.10 and 14.04
** 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/1328594 Title: [Lenovo ThinkPad Edge E320] Wifi disappears ubuntu 13.10 and 14.04 Status in “linux” package in Ubuntu: Incomplete Bug description: I have been running in this desktop dual boot win 7 / ubuntu 12.04;12.10;13.04. From 13.10 my wifi connection is very slow. upgraded to 14.04 - the problem exists. Changed the wifi router - same result. Did a fresh install of ubuntu 14.04 and again having wifi problem - connection slows down unexpectedly and the router disappears. Boot to windows 7 - and have no problem with the speed and connection. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: momchi44 2000 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 10 19:12:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-08 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 003: ID 04f2:b27c Chicony Electronics Co., Ltd Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 12984WG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=839407ba-fe38-4074-bfdd-d98cda56f9c2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8NET27WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 12984WG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8NET27WW(1.11):bd07/27/2011:svnLENOVO:pn12984WG:pvrThinkPadEdgeE320:rvnLENOVO:rn12984WG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 12984WG dmi.product.version: ThinkPad Edge E320 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335875] Re: linux: 2.6.32-63.126 -proposed tracker
*** This bug is a duplicate of bug 1338946 *** https://bugs.launchpad.net/bugs/1338946 ** This bug has been marked a duplicate of bug 1338946 linux: 2.6.32-64.127 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1335875 Title: linux: 2.6.32-63.126 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Bug description: This bug is for tracking the 2.6.32-63.126 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:Monday, 30. June 2014 14:25 UTC kernel-stable-Prepare-package-end:Tuesday, 01. July 2014 04:52 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. July 2014 04:52 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. July 2014 00:23 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Verification-testing-start:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Certification-testing-start:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Security-signoff-start:Wednesday, 02. July 2014 01:37 UTC kernel-stable-Regression-testing-start:Wednesday, 02. July 2014 01:37 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1335875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336485] Re: [HP Pavilion dv6t-7000 CTO Entertainment Notebook PC] suspend/resume failure
Aaahh Ahh, did this problem not occur in a release prior to 14.10? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1336485 Title: [HP Pavilion dv6t-7000 CTO Entertainment Notebook PC] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: "Fixed but needed restart"??? ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaahh 2555 F pulseaudio Date: Tue Jul 1 10:54:28 2014 DuplicateSignature: suspend/resume:Hewlett-Packard HP Pavilion dv6 Notebook PC:F.29 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1403099049 Failure: suspend/resume HibernationDevice: RESUME=UUID=46299c15-e9a2-44ad-b58a-6ef48099477a InstallationDate: Installed on 2014-06-27 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-6-generic root=UUID=5ee7f7cb-22cc-4bfa-b5ac-1c4d0577a870 ro acpi_osi=Linux acpi_backlight=vendor intel_pstate=enable quiet splash acpi_osi=Linux acpi_backlight=vendor intel_pstate=enable vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/03/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181E dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr07901020571620100:rvnHewlett-Packard:rn181E:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 07901020571620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1333609] Re: CVE-2014-1739
** Changed in: linux-lts-raring (Ubuntu Precise) 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/1333609 Title: CVE-2014-1739 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-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix 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-mvl-dove” source package in Trusty: Invalid Status in “linux-ti-omap4” source package in Trusty: Invalid Status in “linux” source package in Utopic: Invalid Status in “linux-armadaxp” source package in Utopic: Invalid Status in “linux-ec2” source package in Utopic: Invalid Status in “linux-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The media_device_enum_entities function in drivers/media/media- device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. Break-Fix: 1651333b09743887bc2dd3d158a11853a2be3fe7 e6a623460e5fc960ac3ee9f946d3106233fd28d8 To manage notifications about this bug go to: https://bugs.lau
[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1
Augusto Bortoluzzi, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-3.16-rc4 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing 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. ** Description changed: - I started to report this bug here: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777 since I thought it was related. + Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: user 2131 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 2131 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 20:01:28 2014 HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35 InstallationDate: Installed on 2014-06-22 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-30-generic N/A - linux-backports-modules-3.13.0-30-generic N/A - linux-firmware 1.127.4 + linux-restricted-modules-3.13.0-30-generic N/A + linux-backports-modules-3.13.0-30-generic N/A + linux-firmware 1.127.4 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Tags added: latest-bios-0901 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338706 Title: Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1 Status in “linux” package in Ubuntu: Incomplete Bug description: Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2131 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 20:01:28 2014 HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35 InstallationDate: Installed on 2014-06-22 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacture
[Kernel-packages] [Bug 879334] Re: nfsd from nfs-kernel-server very slow and system load from 25%-100% from nfsd
Is this bug solved?? I am having similar issues with my Ubuntu server 12.04.04 64 bits. I am using ldap authentication with NFS to mount users home. The server uses 2 gigabyte ethernet using bonding and there are 20 users and have 2x4 processors with 12 Gb ram (it is an ACER gateway gr320 f1 server). I change my server to the 12.04 becouse we were using an old version (7.10) and I was having some problems, but since the change, the clients are too slow. I notice that the server processors load it's high and I think this bug could be afecting me. Sorry about my english and thank you in advance :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/879334 Title: nfsd from nfs-kernel-server very slow and system load from 25%-100% from nfsd Status in “linux” package in Ubuntu: Incomplete Status in “nfs-utils” package in Ubuntu: Confirmed Status in “linux” package in Debian: Fix Released Bug description: I have a diskless ubuntu 10.10 machine which I boot regularly using pxe-boot from another ubuntu machine where I have the root filesystem of the diskless machine exported over nfs. I set it up about a year ago using 10.10. In the mean while the server machine got upgraded to 11.04 and as of yesterday to 11.10. After the upgrade to 11.10 the diskless machine is dead slow (most of the times it wont even boot completely) and the load on the server machine is high (25%-100% as shown from top). If in the middle of the diskless computer booting I do a restart of the nfs server, the client computer proceeds with the boot a bit more and then it gets stuck again. I have to restart and nfs-server 3-4 times in order to get the gdm login screen at the client machine ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nfs-kernel-server 1:1.2.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Fri Oct 21 12:53:02 2011 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nfs-utils UpgradeStatus: Upgraded to oneiric on 2011-10-20 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/879334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1325941] Re: CVE-2014-3917
** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) 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/1325941 Title: CVE-2014-3917 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux-lts-backport-maverick” source package in Quantal: Won't Fix Status in “linux-lts-backport-natty” source package in Quantal: Won't Fix Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New 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-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix 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-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-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: kernel/auditsc.c in the Linux kernel through 3.14.5, when CONFIG_AUDITSYSCALL is enabled with certain syscall rules, allows local users to obtain potentially sensitive single-bit values from kernel memory or cause a denial of service (OOPS) via a large
[Kernel-packages] [Bug 1300349] Re: 8086:0a16 [Dell Inspiron 17R 5737] Video looks interlaced
Since this bug is still open and it looks similar to mine #1318531 I suggest to the people following this channel to check if the 3.13 kernel posted on bug #1318531 fixes this bug so that we can mark one of the two as the duplicate of the other. Regards, Giuseppe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1300349 Title: 8086:0a16 [Dell Inspiron 17R 5737] Video looks interlaced Status in “linux” package in Ubuntu: Confirmed Bug description: The video looks like interlaced video where every other line is shifted. This occurs in 12.04.3 - 14.04 beta2. This doesn't occur in 12.04.0. --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2164 F pulseaudio /dev/snd/controlC0: ubuntu 2164 F pulseaudio CasperVersion: 1.339 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: Dell Inc. Inspiron 5737 Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 StagingDrivers: rts5139 Tags: trusty staging Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 04X8RP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5737:pvrA07:rvnDellInc.:rn04X8RP:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5737 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307473] Re: guest hang due to missing clock interrupt
I'm not confident yet we're seeing the exact same problem, but it is pretty close. We're running a somewhat wide range of hyperisor kernels, these are our observations so far. node-1-1 3.13.0-24-generic is affected for 0% of vms node-1-3 3.13.0-24-generic is affected for 0% of vms node-1-5 3.13.0-24-generic is affected for 0% of vms node-1-6 3.13.0-27-generic is affected for 0% of vms node-1-7 3.13.0-29-generic is affected for 0% of vms node-2-3 3.13.0-30-generic is affected for 0% of vms node-2-4 3.13.0-27-generic is affected for 0% of vms node-2-5 3.13.0-24-generic is affected for 0% of vms node-1-8 3.13.0-27-generic is affected for 2% of vms node-1-10 3.13.0-30-generic is affected for 33% of vms node-1-2 3.13.0-29-generic is affected for 48% of vms node-1-9 3.13.0-30-generic is affected for 32% of vms node-2-1 3.13.0-30-generic is affected for 20% of vms node-2-2 3.13.0-30-generic is affected for 7% of vms node-1-4 3.13.0-29-generic is affected for 61% of vm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307473 Title: guest hang due to missing clock interrupt Status in QEMU: New Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing: - in case of Windows VMs I'm getting BSOD with error message: "A clock interrupt was not received on a secondary processor within the allocated time interval." - On linux VMs I'm noticing "hrtimer: interrupt took 2992229 ns" messages - On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts QEMU version is: QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3) Full command line: qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc- i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a- 4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb- uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio- disk0,id=virtio-disk0,bootindex=1 -drive file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en- us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio- win-0.1-74.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1307473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1307473] Re: guest hang due to missing clock interrupt
Note that my list of affected nodes also include migrated VMs, so there are some false positives (VMs that came from an affected node). The affected VMs on node 1-8 all seem to be migrated from another node. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307473 Title: guest hang due to missing clock interrupt Status in QEMU: New Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing: - in case of Windows VMs I'm getting BSOD with error message: "A clock interrupt was not received on a secondary processor within the allocated time interval." - On linux VMs I'm noticing "hrtimer: interrupt took 2992229 ns" messages - On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts QEMU version is: QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3) Full command line: qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc- i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a- 4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb- uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio- disk0,id=virtio-disk0,bootindex=1 -drive file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en- us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio- win-0.1-74.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1307473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338946] Re: linux: 2.6.32-64.127 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/prepare-package-ports-meta Status: New => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-ports-meta 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/1338946 Title: linux: 2.6.32-64.127 -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-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta 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 Lucid: New Bug description: This bug is for tracking the 2.6.32-64.127 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, 08. July 2014 08:49 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 08. July 2014 08:49 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1326367] Re: exploitable futex vulnerability
This fix seems to trigger problems with virtualization LP #1307473. -- 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/1326367 Title: exploitable futex vulnerability Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Released Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Released Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-armadaxp” source package in Precise: Fix Released Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux-lts-raring” source package in Precise: Fix Released Status in “linux-lts-saucy” source package in Precise: Fix Released Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: Fix Released Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-quantal” source package in Trusty: Invalid Status in “linux-lts-raring” source package in Trusty: Invalid Status in “linux-lts-saucy” source package in Trusty: Invalid Status in “linux-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-fsl-imx51” source package in Utopic: Invalid 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The futex_requeue function in kernel/futex.c in the Linux kernel through 3.14.5 does not ensure that calls have two different futex addresses, which allows local users to gain privileges via a crafted FUTEX_REQUEUE command that facilitates unsafe waiter modification. Break-Fix: 52400ba946759af28442dee6265c5c0180ac7122 54a217887a7b658e2650c3feff22756ab80c7339 Break-Fix: 52400ba946759af28442dee6265c5c0180ac7122 13fbca4c6ecd96ec1a1cfa2e4f2ce191fe928a5e Break-Fix: 52400ba946759af28442dee6265c5c0180ac7122 b3eaa9fc5cd0a4d74b18f6b8dc617aeaf1873270 Break-Fix: 52400ba946759af28442dee6265c5c0180ac7122 e9c243a5a6de0be8e584c604d353412584b592f8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
** Tags removed: bios-outdated-1.80 ** Tags added: latest-bios-1.80 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed Status in “linux” package in Ubuntu: Incomplete Bug description: Using Ubuntu 14.04. Recently updated to kernel version Ubuntu 3.13.0-30.54-generic 3.13.11.2 I expect brightness of my LCD screen to remain the same and be controllable after waking from suspend. It doesn't and isn't. This seems to have only started recently - presumably after a recent update. What happens: Brightness controls fully working after initial boot, both through function keys and system settings. After putting computer into suspend and then re-awakening the LCD screen comes up with lowest brightness in actual appearance but settings still show the brightness as set at suspend time. Controls for brightness have become ineffective - they slide the brightness bar along but make no difference to the actual brightness of the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2060 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 5 18:55:05 2014 InstallationDate: Installed on 2012-06-04 (760 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=865f4d37-5ceb-4e4a-b59b-032fa8a2c80b ro quiet splash elevator=noop vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (68 days ago) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-01W00C:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-01W00C dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1329103] Re: CVE-2014-4014
** Changed in: linux-lts-saucy (Ubuntu Precise) 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/1329103 Title: CVE-2014-4014 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: Won't Fix Status in “linux-lts-backport-natty” source package in Lucid: Won't Fix Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: Won't Fix Status in “linux-lts-backport-natty” source package in Precise: Won't Fix Status in “linux-lts-quantal” source package in Precise: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: Won't Fix Status in “linux-lts-backport-natty” source package in Saucy: Won't Fix Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New 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-fsl-imx51” source package in Trusty: Invalid Status in “linux-lts-backport-maverick” source package in Trusty: Won't Fix Status in “linux-lts-backport-natty” source package in Trusty: Won't Fix 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-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-fsl-imx51” source package in Utopic: Invalid Status in “linux-lts-backport-maverick” source package in Utopic: Won't Fix Status in “linux-lts-backport-natty” source package in Utopic: Won't Fix 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: The capabilities implementation in the Linux kernel before 3.14.8 does not properly consider that namespaces are inapplicable to inodes, which allows local users to bypass intended chmod restrictions by first creating a user namespace, as demonstrated by setting the setgid bit on a file with group ownership of root. Break-Fix: - 23adbe12ef7d3d4195e80800ab36b37bee28cd03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329103/+subscriptions --
[Kernel-packages] [Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
John D Marsden, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-3.16-rc4 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing 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. ** Changed in: linux (Ubuntu) Importance: Low => 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/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed Status in “linux” package in Ubuntu: Incomplete Bug description: Using Ubuntu 14.04. Recently updated to kernel version Ubuntu 3.13.0-30.54-generic 3.13.11.2 I expect brightness of my LCD screen to remain the same and be controllable after waking from suspend. It doesn't and isn't. This seems to have only started recently - presumably after a recent update. What happens: Brightness controls fully working after initial boot, both through function keys and system settings. After putting computer into suspend and then re-awakening the LCD screen comes up with lowest brightness in actual appearance but settings still show the brightness as set at suspend time. Controls for brightness have become ineffective - they slide the brightness bar along but make no difference to the actual brightness of the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2060 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 5 18:55:05 2014 InstallationDate: Installed on 2012-06-04 (760 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=865f4d37-5ceb-4e4a-b59b-032fa8a2c80b ro quiet splash elevator=noop vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (68 days ago) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-01W00C:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-01W00C dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1332379] Re: [Dell Inspiron 5547/5447] Unable to control brightness with Intel Haswell GPU
Pending https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332379/comments/7 . ** 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/1332379 Title: [Dell Inspiron 5547/5447] Unable to control brightness with Intel Haswell GPU Status in HWE Next Project: New Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Trusty: New Bug description: CID: 201401-14530 Dell Inspiron 5547 Unable to control the brightness on this system. Steps: 1. Install 14.04 + update (3.13.0-29), boot to desktop 2. Try to adjust the screen brightness with hotkeys and "Brightness and Lock" applet Expected result: * Screen brightness could be adjusted in both ways. Actual result: * Unable to control screen brightness, the brightness indicator would change according to key press on the hotkeys Debugging information: ubuntu@201401-14530:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201401-14530:~$ grep -r . /proc/acpi /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S3*disabled pci::00:1c.0 /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled ubuntu@201401-14530:~$ dmesg | grep 'ACPI: Video' [ 13.689138] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1609 F pulseaudio /dev/snd/controlC1: ubuntu 1609 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Jun 19 21:47:08 2014 HibernationDevice: RESUME=UUID=7454cf26-0b42-44d7-ac45-01977170fad5 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=3dfa4af3-a788-4fbe-b7db-b895afb04d77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X18 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X18 dmi.modalias: dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5547:pvrX18:rvnDellInc.:rn0598GM:rvrX01:cvnDellInc.:ct8:cvrX18: dmi.product.name: Inspiron 5547 dmi.product.version: X18 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1332379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1334989] Re: CVE-2014-4508
** Changed in: linux (Ubuntu Utopic) 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/1334989 Title: CVE-2014-4508 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: 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-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: New 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 Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: 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-fsl-imx51” 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-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-fsl-imx51” 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: arch/x86/kernel/entry_32.S in the Linux kernel through 3.15.1 on 32-bit x86 platforms, when syscall auditing is enabled and the sep CPU feature flag is set, allows local users to cause a denial of service (OOPS and system crash) via an invalid syscall number, as demonstrated by number 1000. Break-Fix: - 554086d85e71f30abe46fc014fea31929a7c6a8a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https:/
[Kernel-packages] [Bug 1337177] Re: [Hewlett-Packard HP Pavilion m6 Notebook PC] suspend/resume failure
Will Lueking, could you please provide the full computer model as noted on the sticker (ex. HP Pavilion m6-1002xx Entertainment Notebook PC)? ** Tags added: needs-full-computer-model ** 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/1337177 Title: [Hewlett-Packard HP Pavilion m6 Notebook PC] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Possible Duplicate, see bug #1337173 Went to wake from suspend, laptop powered back on, but screen would not wake. Forced power off. Upon reboot, went into recovery mode and fsck'ed the drive due to some errors with some x authority lock files (? I think?). Reboot, normal boot sequence. Another fsk done automagically. Reboot. Now all is well except for System Errors out of the wazoo. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wash 2596 F pulseaudio /dev/snd/controlC0: wash 2596 F pulseaudio Date: Thu Jul 3 02:18:50 2014 DuplicateSignature: suspend/resume:Hewlett-Packard HP Pavilion m6 Notebook PC:F.03 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=0ef77934-024e-4227-a6c3-74c32565d740 InstallationDate: Installed on 2013-10-20 (255 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: Hewlett-Packard HP Pavilion m6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=be71cf3e-3a6e-4ff3-92f4-d50876cb40d9 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 SourcePackage: linux Title: [Hewlett-Packard HP Pavilion m6 Notebook PC] suspend/resume failure UpgradeStatus: Upgraded to utopic on 2014-07-03 (0 days ago) UserGroups: dmi.bios.date: 05/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 18A6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 74.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd05/04/2012:svnHewlett-Packard:pnHPPavilionm6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn18A6:rvr74.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion m6 Notebook PC dmi.product.version: 07911020561620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335313] Re: CVE-2014-4608
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-ec2 (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Saucy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux (Ubuntu Lucid) Status: New => Fix Committed ** Changed in: linux-lts-raring (Ubuntu Precise) 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/1335313 Title: CVE-2014-4608 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: 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-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Fix Committed Status in “linux-armadaxp” source package in Precise: Fix Committed Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: Fix Committed Status in “linux-lts-raring” source package in Precise: Fix Committed Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-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-fsl-imx51” 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-mvl-dove” source pac
[Kernel-packages] [Bug 1307473] Re: guest hang due to missing clock interrupt
Ondergetekende, can you provide further details to why you believe Bug #1326367 is causing this? Would you be willing to test a 3.11.0-24-generic kernel (reported stable) + the futex fix, or a chosen stable version of the 3.13 or 3.15 kernel with just the futex fix. To verify that the futex fix is the problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1307473 Title: guest hang due to missing clock interrupt Status in QEMU: New Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: I noticed on 2 different systems that after upgrade from precise to latest trusty VMs are crashing: - in case of Windows VMs I'm getting BSOD with error message: "A clock interrupt was not received on a secondary processor within the allocated time interval." - On linux VMs I'm noticing "hrtimer: interrupt took 2992229 ns" messages - On some proprietary virtual appliances I'm noticing crashes an due to missing timer interrupts QEMU version is: QEMU emulator version 1.7.91 (Debian 2.0.0~rc1+dfsg-0ubuntu3) Full command line: qemu-system-x86_64 -enable-kvm -name win7eval -S -machine pc- i440fx-1.7,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid 05e5089a- 4aa1-6bb2-ef06-ab4d020a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7eval.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -boot strict=on -device piix3-usb- uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/vm/win7eval.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio- disk0,id=virtio-disk0,bootindex=1 -drive file=/home/damarion/iso/7600.16385.090713-1255_x86fre_enterprise_en- us_EVAL_Eval_Enterprise-GRMCENEVAL_EN_DVD.iso,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -drive file=/home/damarion/iso/virtio- win-0.1-74.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:38:31:0a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa- serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -device VGA,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1307473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338866] Re: [Compaq 15 Touchsmart] Wireless LED won't change color
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338866 Title: [Compaq 15 Touchsmart] Wireless LED won't change color Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201309-13164 Compaq 15 Touchsmart The wireless LED won't change color while disabled Steps: 1. Install 14.04 + update (3.13.0-30) 2. Test the wireless key Expected result: * Wireless key should work, and the LED should change color when the wireless is disabled Actual result: * Wireless would be disabled by the hotkey, but the LED won't change color. Note: the wireless key does not work at all before upgrading the system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1451 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 21.821955] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 48.284935] type=1400 audit(1404790545.469:74): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2014 comm="apparmor_parser" [ 48.284942] type=1400 audit(1404790545.469:75): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2014 comm="apparmor_parser" [ 48.285354] type=1400 audit(1404790545.469:76): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2014 comm="apparmor_parser" [ 106.599254] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Date: Mon Jul 7 23:36:43 2014 HibernationDevice: RESUME=UUID=506e69ad-2133-4a43-9371-0ccac623c380 InstallationDate: Installed on 2014-07-08 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard Compaq 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=8ac44edb-d2cd-4778-81c7-19b1a86d27bb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.13.T02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 218F dmi.board.vendor: Hewlett-Packard dmi.board.version: 39.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.13.T02:bd11/20/2013:svnHewlett-Packard:pnCompaq15NotebookPC:pvr099B1002005000112:rvnHewlett-Packard:rn218F:rvr39.21:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Compaq 15 Notebook PC dmi.product.version: 099B1002005000112 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1338866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318837] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
This is affecting me too, on a system that worked perfectly with some older Ubuntu release (I guess it was 12.04 LTS but not 100% sure about it, sorry). I did not see it mentioned anywhere on this BR but afaik the kernel bug is this - maybe could be helpful to narrow down the search for the fix: https://bugzilla.kernel.org/show_bug.cgi?id=61621 I tested some kernels on my system with these results: - 3.13.0-30-generic (Trusty's stock kernel) is affected - 3.13.11-03131104 is affected (and so are a few other 3.13.x that I tested) - 3.14.1-031401 works (and so do all 3.14.x at least up to 3.14.9-031409) - 3.15.4-031504 works - 3.16.0-031600rc2 and rc4 both work ** Bug watch added: Linux Kernel Bug Tracker #61621 http://bugzilla.kernel.org/show_bug.cgi?id=61621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318837 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Status in “linux” package in Ubuntu: Incomplete Bug description: In Trusty, happens continuously 100% of the time after boot/reboot, finally fails, followed by authentication failure. This doesn't happen with 12.04 Precise. --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kit284 2043 F pulseaudio /dev/snd/controlC1: kit284 2043 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11 InstallationDate: Installed on 2014-04-02 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: CLEVO D900K NonfreeKernelModules: nvidia Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=e838aadc-8afe-436a-a3cb-a2908622ffc4 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2005 dmi.bios.vendor: Phoenix dmi.bios.version: 4.06CJ15 dmi.board.name: D900K dmi.board.vendor: CLEVO dmi.board.version: VT8341B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: D900K dmi.product.version: VT8341B dmi.sys.vendor: CLEVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338177] Re: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295]
Hello. I tried using both of the Ubuntu packages of the driver, from the utopic repositories, namely: fglrx and fglrx-updates. I also observed the same problem with the fglrx packages under Trusty. The versions were: fglrx_13.350.1-0ubuntu3_amd64.deb fglrx- amdcccle_13.350.1-0ubuntu3_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338177 Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] Status in “linux” package in Ubuntu: Incomplete Bug description: I've just installed Utopic, and my machine is really slow to boot. WORKAROUND: Use Radeon driver. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 [modified: boot/vmlinuz-3.15.0-6-generic] ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rjn2642 F pulseaudio /dev/snd/controlC2: rjn2642 F pulseaudio /dev/snd/controlC0: rjn2642 F pulseaudio /dev/snd/controlC1: rjn2642 F pulseaudio Date: Sun Jul 6 00:58:31 2014 DuplicateSignature: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] RIP: 0010:location location ulReadMmRegisterUlongViaAddr+0xc/0x10 [fglrx] Failure: oops HibernationDevice: RESUME=UUID=dd46a6f0-bcb8-4e75-b77d-6158117027ac InstallationDate: Installed on 2014-07-05 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140703) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=41c3bf4e-49c3-4546-aea6-30a91309679d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:1295] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Installed latest upstream mainline kernel: 3.16.0-031600rc4-generic Unfortunately this failed to solve the problem. Brightness control on systems settings and via function keys works on initial boot but ceases to work after a suspend, as before. Thank you for your help. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.16.0-031600rc4-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed Status in “linux” package in Ubuntu: Confirmed Bug description: Using Ubuntu 14.04. Recently updated to kernel version Ubuntu 3.13.0-30.54-generic 3.13.11.2 I expect brightness of my LCD screen to remain the same and be controllable after waking from suspend. It doesn't and isn't. This seems to have only started recently - presumably after a recent update. What happens: Brightness controls fully working after initial boot, both through function keys and system settings. After putting computer into suspend and then re-awakening the LCD screen comes up with lowest brightness in actual appearance but settings still show the brightness as set at suspend time. Controls for brightness have become ineffective - they slide the brightness bar along but make no difference to the actual brightness of the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2060 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 5 18:55:05 2014 InstallationDate: Installed on 2012-06-04 (760 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=865f4d37-5ceb-4e4a-b59b-032fa8a2c80b ro quiet splash elevator=noop vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (68 days ago) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-01W00C:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-01W00C dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1286388] Re: changes to the boot order made via efibootmgr are not sticking
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (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/1286388 Title: changes to the boot order made via efibootmgr are not sticking Status in “grub2” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: I installed Ubuntu 14.04 beta on my HP Elitebook Folio laptop. Fresh install, complete hard disk formatted. After successful installation I rebooted. The system tells me I am missing the OS. Then from BIOS menu F9 I could manually boot via EFI and got the system working. However I could not change bios settings such that the system would boot automatically via UEFI. After long trial and error with advice from several IRC colleagues I somehow managed to get the system boot via BIOS. But it seems that changes that are done to boot order, do not stay permanent. I was told that my boot firmware "assumes that a drive without a "boot flag" on any of its primary partitions in its msdos label cannot be booted via BIOS (again, only true with Windows). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub-efi-amd64 (not installed) ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5 Uname: Linux 3.13.0-13-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 1 00:10:27 2014 InstallationDate: Installed on 2014-02-28 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1286388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260
>From the upstream kernel bug, it seems that fixes for bad iwlwifi 7260 >behaviour upstream are in 3.14.6 https://bugzilla.kernel.org/show_bug.cgi?id=72601#c92 and, a second fix in https://bugzilla.kernel.org/show_bug.cgi?id=42978#c29 will land upstream shortly. If these fixes are causing xps 13 wifi issues, it does not seem that bisecting 3.13 will be too helpful. Anyway, I'm not too knowledgeable on bisection and patch backporting. ** Bug watch added: Linux Kernel Bug Tracker #42978 http://bugzilla.kernel.org/show_bug.cgi?id=42978 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315221 Title: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260 Status in “linux” package in Ubuntu: Incomplete Bug description: My Intel 7260 network card regularly shows very poor performance and/or loses its connection entirely. On several occasions I have been unable to reestablish an association with the AP without rebooting. This occurs even if the laptop is within a few feet of the AP. I did not have this problem on 12.04 with a quantal backport kernel. Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Thu May 1 22:59:32 2014 HibernationDevice: RESUME=/dev/mapper/cswap0 InstallationDate: Installed on 2014-04-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338946] Re: linux: 2.6.32-64.127 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lbm 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/1338946 Title: linux: 2.6.32-64.127 -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-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta 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 Lucid: New Bug description: This bug is for tracking the 2.6.32-64.127 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, 08. July 2014 08:49 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 08. July 2014 08:49 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260
asala: While it's known that there are forward fixes, it also worked in an earlier kernel. This means that there is previous breakage, as well. The fixes may be for that same breakage, I haven't looked into that. I believe 3.16 is fixed, as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1315221 Title: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260 Status in “linux” package in Ubuntu: Incomplete Bug description: My Intel 7260 network card regularly shows very poor performance and/or loses its connection entirely. On several occasions I have been unable to reestablish an association with the AP without rebooting. This occurs even if the laptop is within a few feet of the AP. I did not have this problem on 12.04 with a quantal backport kernel. Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Thu May 1 22:59:32 2014 HibernationDevice: RESUME=/dev/mapper/cswap0 InstallationDate: Installed on 2014-04-25 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338524] Re: linux: 3.13.0-32.56 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges (arges) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338524 Title: linux: 3.13.0-32.56 -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: Fix Released 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-32.56 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:Monday, 07. July 2014 10:33 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Monday, 07. July 2014 18:08 UTC kernel-stable-Prepare-package-end:Monday, 07. July 2014 18:08 UTC kernel-stable-Promote-to-proposed-start:Monday, 07. July 2014 18:08 UTC ppa-package-testing-start:Monday, 07. July 2014 18:08 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1337667] Re: [HP 14 Notebook] 2-finger pinch / expand does not work on this system.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1337667 Title: [HP 14 Notebook] 2-finger pinch / expand does not work on this system. Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201310-14246 HP 14 Notebook Two finger scrolling works fine on this system, but two finger pinch / zoom does not. Steps: 1. Install the gallery app on 14.04 2. Open a picture, try to pinch / expand on the touchpad to zoom Expected result: * Pinch / expeand should work. Actual result: * Nothing happened ubuntu@201310-14246:~$ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePointid=11 [slave pointer (2)] ⎜ ↳ ALPS PS/2 Deviceid=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ HP Truevision HDid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=10 [slave keyboard (3)] ↳ HP Wireless hotkeys id=13 [slave keyboard (3)] ↳ HP WMI hotkeys id=14 [slave keyboard (3)] ubuntu@201310-14246:~$ xinput list-props 11 | grep Capa Synaptics Capabilities (291): 1, 1, 1, 1, 1, 1, 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1544 F pulseaudio /dev/snd/pcmC0D0p: ubuntu 1544 F...m pulseaudio CurrentDesktop: Unity Date: Thu Jul 3 05:32:38 2014 HibernationDevice: RESUME=UUID=4a726311-b83d-46a5-b10e-c4d9b5dd5992 InstallationDate: Installed on 2014-07-02 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP 240 G2 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=2a0776f8-27d4-48bc-b025-01f0466204a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.13.T02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 218B dmi.board.vendor: Hewlett-Packard dmi.board.version: 39.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.13.T02:bd11/20/2013:svnHewlett-Packard:pnHP240G2NotebookPC:pvr0981100200505E112:rvnHewlett-Packard:rn218B:rvr39.21:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 240 G2 Notebook PC dmi.product.version: 0981100200505E112 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1337177] Re: [Hewlett-Packard HP Pavilion m6 Notebook PC] suspend/resume failure
Full computer model: HP Pavilion m6-1035dx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1337177 Title: [Hewlett-Packard HP Pavilion m6 Notebook PC] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Possible Duplicate, see bug #1337173 Went to wake from suspend, laptop powered back on, but screen would not wake. Forced power off. Upon reboot, went into recovery mode and fsck'ed the drive due to some errors with some x authority lock files (? I think?). Reboot, normal boot sequence. Another fsk done automagically. Reboot. Now all is well except for System Errors out of the wazoo. ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wash 2596 F pulseaudio /dev/snd/controlC0: wash 2596 F pulseaudio Date: Thu Jul 3 02:18:50 2014 DuplicateSignature: suspend/resume:Hewlett-Packard HP Pavilion m6 Notebook PC:F.03 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=0ef77934-024e-4227-a6c3-74c32565d740 InstallationDate: Installed on 2013-10-20 (255 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: Hewlett-Packard HP Pavilion m6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=be71cf3e-3a6e-4ff3-92f4-d50876cb40d9 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 SourcePackage: linux Title: [Hewlett-Packard HP Pavilion m6 Notebook PC] suspend/resume failure UpgradeStatus: Upgraded to utopic on 2014-07-03 (0 days ago) UserGroups: dmi.bios.date: 05/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 18A6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 74.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd05/04/2012:svnHewlett-Packard:pnHPPavilionm6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn18A6:rvr74.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion m6 Notebook PC dmi.product.version: 07911020561620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338893] Re: Backport igb fix to trusty (kernel 3.13)
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Utopic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338893 Title: Backport igb fix to trusty (kernel 3.13) Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: Fix Released Bug description: I'd like to request that the following trivial patch be backported into the trusty kernel: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/intel/igb?id=e66c083aab32842f225bae2a2c30744bf96abaec Without this patch, it's extremely difficult to debug packet loss issues on igb interfaces because as soon as you've had one rx drop ethtool will report constant rx drops (because the counter is not reset). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338924] [NEW] Some warning messages(''NUMA: Warning: node ids are out of bound'' & ''WARNING: CPU: 5 PID: 0'' & ''warn_slowpath_common'' & ''warn_slowpath_fmt'') log in Ubuntu1
You have been subscribed to a public bug:
Problem Circumstances
==
Test Case ID :9858.1
Affected System: 2
Time to Failure: 30 minutes
Reproducible: Yes,
Current Behavior
==
Some warning messages("NUMA: Warning: node ids are out of bound" & "WARNING:
CPU: 5 PID: 0" & "warn_slowpath_common" & "warn_slowpath_fmt") log in
Ubuntu14.04 dmesg, please refer to attached files.
Reference Verification
==
1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No.
2. Which similar project/product passed? No.
Steps to reproduce the problem
==
1. Install Ubuntu 14.04 UEFI mode.
Expected Behavior
==
No abnormal message log in Ubuntu14.04 dmesg.
Config:
(Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA
2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2
VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000
(2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16
Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2
USB KB/mouse
AHCI
QTFAMW40300028, 31F06MB00E0-B2A
Ubuntu14.04 UEFI mode
Intel I210 OB LAN
AST2400-RKVM
Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID
0,1,5,6,10,50,60,8i,mini-SAS,2,
Delta DPS-650SB A
QTFCMW4140003
0.01
2A06
2.03
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
Some warning messages(''NUMA: Warning: node ids are out of bound'' & ''WARNING:
CPU: 5 PID: 0'' & ''warn_slowpath_common'' & ''warn_slowpath_fmt'') log in
Ubuntu14.04 dmesg.
https://bugs.launchpad.net/bugs/1338924
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 1338919] [NEW] The information - CPU cores is incorrect in Ubuntu14.04 cpuinfo.
You have been subscribed to a public bug: Problem Circumstances == Test Case ID :9859.2 Affected System: 2 Time to Failure: Immediately Reproducible: Yes, Current Behavior == Boot into Ubuntu 14.04, then type command "cat /proc/cpuinfo" to check CPU information, the information - CPU cores is incorrect, please refer to attached photo. Reference Verification == 1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No. 2. Which similar project/product passed? No. Steps to reproduce the problem == 1.Boot into Ubuntu 14.04 2.type command "cat /proc/cpuinfo" to check CPU information Expected Behavior == The information - CPU cores is correct in Ubuntu14.04 cpuinfo. Config: (Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA 2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2 VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000 (2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16 Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2 USB KB/mouse AHCI QTFAMW40300028, 31F06MB00E0-B2A Ubuntu14.04 UEFI mode Intel I210 OB LAN AST2400-RKVM Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID 0,1,5,6,10,50,60,8i,mini-SAS,2, Delta DPS-650SB A QTFCMW4140003 0.01 2A06 2.03 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- The information - CPU cores is incorrect in Ubuntu14.04 cpuinfo. https://bugs.launchpad.net/bugs/1338919 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 1338924] Re: Some warning messages(''NUMA: Warning: node ids are out of bound'' & ''WARNING: CPU: 5 PID: 0'' & ''warn_slowpath_common'' & ''warn_slowpath_fmt'') log in Ubuntu14.
** 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/1338924
Title:
Some warning messages(''NUMA: Warning: node ids are out of bound'' &
''WARNING: CPU: 5 PID: 0'' & ''warn_slowpath_common'' &
''warn_slowpath_fmt'') log in Ubuntu14.04 dmesg.
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Problem Circumstances
==
Test Case ID :9858.1
Affected System: 2
Time to Failure: 30 minutes
Reproducible: Yes,
Current Behavior
==
Some warning messages("NUMA: Warning: node ids are out of bound" & "WARNING:
CPU: 5 PID: 0" & "warn_slowpath_common" & "warn_slowpath_fmt") log in
Ubuntu14.04 dmesg, please refer to attached files.
Reference Verification
==
1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No.
2. Which similar project/product passed? No.
Steps to reproduce the problem
==
1. Install Ubuntu 14.04 UEFI mode.
Expected Behavior
==
No abnormal message log in Ubuntu14.04 dmesg.
Config:
(Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA
2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2
VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000
(2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16
Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2
USB KB/mouse
AHCI
QTFAMW40300028, 31F06MB00E0-B2A
Ubuntu14.04 UEFI mode
Intel I210 OB LAN
AST2400-RKVM
Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID
0,1,5,6,10,50,60,8i,mini-SAS,2,
Delta DPS-650SB A
QTFCMW4140003
0.01
2A06
2.03
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338924] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1338924
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: 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/1338924
Title:
Some warning messages(''NUMA: Warning: node ids are out of bound'' &
''WARNING: CPU: 5 PID: 0'' & ''warn_slowpath_common'' &
''warn_slowpath_fmt'') log in Ubuntu14.04 dmesg.
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Problem Circumstances
==
Test Case ID :9858.1
Affected System: 2
Time to Failure: 30 minutes
Reproducible: Yes,
Current Behavior
==
Some warning messages("NUMA: Warning: node ids are out of bound" & "WARNING:
CPU: 5 PID: 0" & "warn_slowpath_common" & "warn_slowpath_fmt") log in
Ubuntu14.04 dmesg, please refer to attached files.
Reference Verification
==
1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No.
2. Which similar project/product passed? No.
Steps to reproduce the problem
==
1. Install Ubuntu 14.04 UEFI mode.
Expected Behavior
==
No abnormal message log in Ubuntu14.04 dmesg.
Config:
(Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA
2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2
VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000
(2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16
Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2
USB KB/mouse
AHCI
QTFAMW40300028, 31F06MB00E0-B2A
Ubuntu14.04 UEFI mode
Intel I210 OB LAN
AST2400-RKVM
Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID
0,1,5,6,10,50,60,8i,mini-SAS,2,
Delta DPS-650SB A
QTFCMW4140003
0.01
2A06
2.03
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1337281] Re: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot
I have the impression that packets larger than the MTU are not treated correctly. It would be worthwhile if someone who knows more about this did some MTU and IMCP "fragmentation needed" functionality tests. The buggy kernel update seems to contains this patch: http://patchwork.ozlabs.org/patch/345509/ ... which is related to my suspicion. It might be useful to double-check that patch for side-effects. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1337281 Title: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot Status in “linux” package in Ubuntu: Confirmed Bug description: Since we installed the latest kernel update on our firewall this weekend (3.2.0-65.98) we got massive problems connecting from thunderbird (windows client) to an external imap-server (dovecot with tls). With our Linux client we got no problems. Opening or sending mails with attachments which was done in a second before the update, took some minutes after the update to kernel 3.2.0-65! Installing the kernel version 3.2.0-64 on our firewall system fixed the problem, also the newer kernel linux-generic-lts-trusty did fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338919] Re: The information - CPU cores is incorrect in Ubuntu14.04 cpuinfo.
** 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/1338919 Title: The information - CPU cores is incorrect in Ubuntu14.04 cpuinfo. Status in “linux” package in Ubuntu: Incomplete Bug description: Problem Circumstances == Test Case ID :9859.2 Affected System: 2 Time to Failure: Immediately Reproducible: Yes, Current Behavior == Boot into Ubuntu 14.04, then type command "cat /proc/cpuinfo" to check CPU information, the information - CPU cores is incorrect, please refer to attached photo. Reference Verification == 1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No. 2. Which similar project/product passed? No. Steps to reproduce the problem == 1.Boot into Ubuntu 14.04 2.type command "cat /proc/cpuinfo" to check CPU information Expected Behavior == The information - CPU cores is correct in Ubuntu14.04 cpuinfo. Config: (Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA 2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2 VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000 (2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16 Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2 USB KB/mouse AHCI QTFAMW40300028, 31F06MB00E0-B2A Ubuntu14.04 UEFI mode Intel I210 OB LAN AST2400-RKVM Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID 0,1,5,6,10,50,60,8i,mini-SAS,2, Delta DPS-650SB A QTFCMW4140003 0.01 2A06 2.03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338919] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1338919 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1338919 Title: The information - CPU cores is incorrect in Ubuntu14.04 cpuinfo. Status in “linux” package in Ubuntu: Incomplete Bug description: Problem Circumstances == Test Case ID :9859.2 Affected System: 2 Time to Failure: Immediately Reproducible: Yes, Current Behavior == Boot into Ubuntu 14.04, then type command "cat /proc/cpuinfo" to check CPU information, the information - CPU cores is incorrect, please refer to attached photo. Reference Verification == 1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No. 2. Which similar project/product passed? No. Steps to reproduce the problem == 1.Boot into Ubuntu 14.04 2.type command "cat /proc/cpuinfo" to check CPU information Expected Behavior == The information - CPU cores is correct in Ubuntu14.04 cpuinfo. Config: (Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA 2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2 VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000 (2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16 Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2 USB KB/mouse AHCI QTFAMW40300028, 31F06MB00E0-B2A Ubuntu14.04 UEFI mode Intel I210 OB LAN AST2400-RKVM Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID 0,1,5,6,10,50,60,8i,mini-SAS,2, Delta DPS-650SB A QTFCMW4140003 0.01 2A06 2.03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1337281] Re: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot
http://lists.openwall.net/netdev/2014/06/10/108 confirms and has information about this issue in version 3.4.92. Hope it helps -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1337281 Title: network problems after update to kernel 3.2.0-65 - thunderbird/imap/dovecot Status in “linux” package in Ubuntu: Confirmed Bug description: Since we installed the latest kernel update on our firewall this weekend (3.2.0-65.98) we got massive problems connecting from thunderbird (windows client) to an external imap-server (dovecot with tls). With our Linux client we got no problems. Opening or sending mails with attachments which was done in a second before the update, took some minutes after the update to kernel 3.2.0-65! Installing the kernel version 3.2.0-64 on our firewall system fixed the problem, also the newer kernel linux-generic-lts-trusty did fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
I've been able to reproduce a similar problem to chuxinxin and collected logs. Distro: Ubuntu 14.04 with Ubuntu mainline 3.16rc4 uname -a: Linux Cockatoo 3.16.0-031600rc4-generic #201407061635 SMP Sun Jul 6 20:36:26 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Step-by-step procedure to reproduce: 1. Boot system with r8192ee module blacklisted 2. modprobe r8192ee 3. Connect to wireless network with NetworkManager 4. Connection works well for a while 5. Connection suddenly disconnects 6. The wireless network is no longer visible in NetworkManager, but others remain visible. 7. Kill NetworkManager and wpa_supplicant 8. NetworkManager no longer shows device 9. Attempt to modprobe -r r8192ee renders system unresponsive The attached tarball include lsmod, dmesg and syslog. I split the logs into before/after killing NetworkManager & wpa_supplicant since there was a lot of spam in the logs after that event. It may be relevant that this was done in an environment with a lot of radio interference and dropped packets. ** Attachment added: "r8192ee-3.16rc4-armstrong.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239578/+attachment/4148033/+files/r8192ee-3.16rc4-armstrong.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339196] [NEW] keypad stops working
Public bug reported: This started with a recent update. Using 3.13.0-30-generic Ubuntu 64 bit 14.04 LTS. 1: The keystrokes suddenly stop working e.g. when using LYX [latest version]. 2: The text input stops and moves to the beginning of the previously written line and overrights it [although hitting return will still execute the full line] e.g. when using R [latest version]. The problem does not occur on my 32-bit system only the 64 bit. System characteristics: Gigabyte Ultra board Keyboard: logitech K330 Mouse: Logitech M215 Memory: 15.6 GiB Processor: AMDA10-6800K APU with Radeon HD Graphics x4 Graphics: Gallium 04 on AMD RV670 Disk: 980.1 GB I've tried to fix it for a couple of weeks now but could not. Any ideas what is wrong. George Hart ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1339196 Title: keypad stops working Status in “linux” package in Ubuntu: New Bug description: This started with a recent update. Using 3.13.0-30-generic Ubuntu 64 bit 14.04 LTS. 1: The keystrokes suddenly stop working e.g. when using LYX [latest version]. 2: The text input stops and moves to the beginning of the previously written line and overrights it [although hitting return will still execute the full line] e.g. when using R [latest version]. The problem does not occur on my 32-bit system only the 64 bit. System characteristics: Gigabyte Ultra board Keyboard: logitech K330 Mouse: Logitech M215 Memory: 15.6 GiB Processor: AMDA10-6800K APU with Radeon HD Graphics x4 Graphics: Gallium 04 on AMD RV670 Disk: 980.1 GB I've tried to fix it for a couple of weeks now but could not. Any ideas what is wrong. George Hart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
One thing I forgot to mention: I've been able to reproduce the problem every time for several times with the procedure described. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next Project: Confirmed Status in HWE Next trusty series: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. Status: waiting for this driver being moved out of staging directory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339199] [NEW] mpi getmem.64 user job crashes ubuntu 14.04 ppc64le LE
Public bug reported: mpi getmem.64 user job crashes ubuntu 14.04 ppc64le LE SUMMARY: mpi user job launch getmem.64 user job crashes ubuntu 14.04 We still have the node c656f2n05 in debug with console opened and can give access when needed. ^^ CONFIGURATION: ^^ Job launched across cluster of 4 p8 22L systems ( hostnames on the ibm 9.* net ) c656f2n03 is c656f2n03.pok.stglabs.ibm.com is 9.114.39.143 c656f2n04 is c656f2n04.pok.stglabs.ibm.com is 9.114.39.144 c656f2n05 is c656f2n05.pok.stglabs.ibm.com is 9.114.39.145 <--- node crashed c656f2n06 is c656f2n06.pok.stglabs.ibm.com is 9.114.39.146 ^^ BUILD: ^^ Ubuntu 14.04 LTS c656f2n05 hvc0 Linux c656f2n05 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:46:02 UTC 2014 ppc 64le ppc64le ppc64le GNU/Linux ^ SCENARIO: ^ Hi, all: P8 server c656f2n05 crashed again. I have launched openshmem regression with the efix of D198270 before the server crashed. Here below are the steps that I have used to launched the test: - 1. ssh c656f2n03 with root/davega. 2. su - qixiaol 3. cd /u/qixiaol/fvt/openshmem/get 4. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> env | grep MP MP_ADAPTER_USE=shared MP_EUIDEVICE=sn_all MP_EUILIB=us MP_EUILIBPATH=/u/qixiaol/fvt/efix/RVIN_LE/ MP_HOSTFILE=/u/qixiaol/fvt/openshmem/host.list MP_PROCS=8 MP_RESD=poe 5. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> ./run.all And the test log is at /u/qixiaol/fvt/openshmem/get/RESULTS: --- [c656f2n03][/u/qixiaol/fvt/openshmem/get/RESULTS]> /afs/apd/u/shapiro/gpfs/PRO140708.12 (12:52:10) c199sq03:/u/shapiro/le # cat /afs/apd/u/shapiro/gpfs/PRO140708.11 mpi getmem.64 user job crashes ubuntu 14.04 ppc64le LE SUMMARY: mpi user job launch getmem.64 user job crashes ubuntu 14.04 We still have the node c656f2n05 in debug with console opened and can give access when needed. ^^ CONFIGURATION: ^^ Job launched across cluster of 4 p8 22L systems ( hostnames on the ibm 9.* net ) c656f2n03 is c656f2n03.pok.stglabs.ibm.com is 9.114.39.143 c656f2n04 is c656f2n04.pok.stglabs.ibm.com is 9.114.39.144 c656f2n05 is c656f2n05.pok.stglabs.ibm.com is 9.114.39.145 <--- node crashed c656f2n06 is c656f2n06.pok.stglabs.ibm.com is 9.114.39.146 ^^ BUILD: ^^ Ubuntu 14.04 LTS c656f2n05 hvc0 Linux c656f2n05 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:46:02 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ^ SCENARIO: ^ Hi, all: P8 server c656f2n05 crashed again. I have launched openshmem regression with the efix of D198270 before the server crashed. Here below are the steps that I have used to launched the test: - 1. ssh c656f2n03 with root/davega. 2. su - qixiaol 3. cd /u/qixiaol/fvt/openshmem/get 4. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> env | grep MP MP_ADAPTER_USE=shared MP_EUIDEVICE=sn_all MP_EUILIB=us MP_EUILIBPATH=/u/qixiaol/fvt/efix/RVIN_LE/ MP_HOSTFILE=/u/qixiaol/fvt/openshmem/host.list MP_PROCS=8 MP_RESD=poe 5. [c656f2n03][/u/qixiaol/fvt/openshmem/get]> ./run.all And the test log is at /u/qixiaol/fvt/openshmem/get/RESULTS: --- [c656f2n03][/u/qixiaol/fvt/openshmem/get/RESULTS]> The binary file of getmem.64 is at c656f2n03:/u/qixiaol/fvt/openshmem/get/bin/ppc64le/getmem.64 And its source code is at c656f2n03:/u/qixiaol/fvt/openshmem/get/src/getmem.c Best Wishes Xiao Lu Qi(???) SYMPTOM: Ubuntu 14.04 LTS c656f2n05 hvc0 c656f2n05 login: [418442.082487] rport-1:0-3: blocked FC remote port time out: removing rport [418442.082492] rport-5:0-6: blocked FC remote port time out: removing rport [418442.082494] rport-2:0-3: blocked FC remote port time out: removing rport [466884.681785] kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! cpu 0x19: Vector: 700 (Program Check) at [c01f39a13310] pc: c022fa34: .kfree+0x124/0x220[466884.683019] kernel BUG at /b uild/buildd/linux-3.13.0/mm/slub.c:3365! lr: c07fb6a8: .skb_free_head+0x78/0xb0 sp: c01f39a13590 msr: 90029033 current = 0xc01f58828bf0 paca= 0xcfe45780 softe: 0irq_happened: 0x01 pid = 98622, comm = getmem.64 [466884.685546] kekernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! [466884.687415] kernel BUG at /build/buildd/linux-3.13.0/mm/slub .c:3365! cpu 0x11: Vector: 700 (Program Check) at [c01f39a6b310] pc: c022fa34: .kfree+0x124/0x220 lr: c07fb6a8: .skb_free_head+0x78/0xb0 sp: c01f39a6b590 msr: 90029033 current = 0xc01f5886f840 paca= 0xcfe43b80 softe: 0irq_happened: 0x01 pid = 98621, comm = getmem.64 kernel BUG at /build/buildd/linux-3.13.0/mm/slub.c:3365! enter ? for help 19:mon> t print backtrace 19:mon> t [c01f39a13620] c07fb6a8 .skb_free_head+0x78/0xb0 [c
[Kernel-packages] [Bug 1339196] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1339196 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1339196 Title: keypad stops working Status in “linux” package in Ubuntu: Incomplete Bug description: This started with a recent update. Using 3.13.0-30-generic Ubuntu 64 bit 14.04 LTS. 1: The keystrokes suddenly stop working e.g. when using LYX [latest version]. 2: The text input stops and moves to the beginning of the previously written line and overrights it [although hitting return will still execute the full line] e.g. when using R [latest version]. The problem does not occur on my 32-bit system only the 64 bit. System characteristics: Gigabyte Ultra board Keyboard: logitech K330 Mouse: Logitech M215 Memory: 15.6 GiB Processor: AMDA10-6800K APU with Radeon HD Graphics x4 Graphics: Gallium 04 on AMD RV670 Disk: 980.1 GB I've tried to fix it for a couple of weeks now but could not. Any ideas what is wrong. George Hart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338666] [NEW] ppc64le kernel module nx_crypto blocks loading other kernel modules
You have been subscribed to a public bug: == Comment: #0 - David A. Harnett - 2014-03-12 20:43:09 == ---Problem Description--- On Ubuntu 14.04 ppc64le in a Power7 LPAR , if kernel module nx_crypto is already loaded , attempts to load additional kernel modules fail with this message : modprobe: ERROR: could not insert 'xxx': Invalid argument where xxx is the name of module we tried to load . dmesg shows: [ 33.012917] nx: scatter/gather list overflow, pid: 806 ---uname output--- Linux c277f3u1crash2 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:47:19 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- special PowerVM Little Endian firmware level b0108l_1446.780 Machine Type = Power 780+ 9179-MHD LPAR ---Debugger--- A debugger is not configured ---Steps to Reproduce--- "lsmod" , if nx_crypto module not loaded , then "modprobe nx_crypto" ; try to load any kernel module , "modprobe nfs" Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Dave Harnett/dober...@us.ibm.com , no backup: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. == Comment: #3 - David A. Harnett - 2014-03-12 21:19:42 == Circumvention : add directive "blacklist nx_crypto" to a file in directory /etc/modprobe.d Problem does not occur on Ubuntu 14.04 powerpc64 Big Endian image running in LPAR on same hardware . == Comment: #5 - Leonidas Da Silva Barbosa - 2014-03-13 14:48:17 == David, can you provide us with a cat /etc/issue cat /proc/cpuinfo uname -a from the system where the problem does not happen? == Comment: #6 - David A. Harnett - 2014-03-13 15:24:55 == This is the requested output from the BE image in another LPAR on the same physical machine . $ cat /etc/issue Ubuntu Trusty Tahr (development branch) \n \l $ cat /proc/cpuinfo processor : 0 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 1 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 2 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 3 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) timebase: 51200 platform: pSeries model : IBM,9179-MHD machine : CHRP IBM,9179-MHD $ uname -a Linux c277f3u1admin2 3.13.0-17-powerpc64-smp #37-Ubuntu SMP Mon Mar 10 21:58:15 UTC 2014 ppc64 ppc64 ppc64 GNU/Linux == Comment: #10 - Leonidas Da Silva Barbosa - 2014-03-14 13:19:42 == David, The hardware that are you running both image is over a PowerVM LE ? == Comment: #11 - David A. Harnett - 2014-03-14 13:32:42 == This model Power 780 (Saturn MR class) Power7 machine has special IBM internal use only firmware that permits both LE and BE OS images to run in separate PowerVM LPARs simultaneously . Our contact for the firmware is David Larson , lars...@us.ibm.com This is the third problem I observed on this machine where LE OS has problems but the same function works correctly on a nearly equivalent level of BE OS on the same physical machine . 1) nvram command fails with segfault - to be fixed in powerpc-utils package 2) ibmveth kernel driver for PowerVM virtual ethernet device - fixed in an Ubuntu 14.04 kernel 3) this problem Common thread seems to be drivers that interface with firmware/hardware platform features . == Comment: #17 - Cody P. Schafer - 2014-05-14 14:02:52 == I've seen issues on POWER8-PowerVM-ppc64le with nx-crypto, dmesg attached. note: this is still LE, but is also on P8 (not P7 as this bug was originally reported). == Comment: #18 - Cody P. Schafer - 2014-05-14 14:04:55 == Also, in my case further modules load without issue. The only problem is the log spam. == Comment: #19 - Cody P. Schafer - 2014-05-14 14:05:17 == kernel is v3.15-rc4-260-g38583f0 (from linus's tree) uname -a: Linux host 3.15.0-rc4-testing+ #8 SMP Wed May 14 02:21:38 PDT 2014 ppc64le ppc64le ppc64le GNU/Linux == Comment: #20 - George C. Wilson - 2014-05-14 14:13:32 == Hi Cody. NX crypto isn't supported on little endian kernels. We don't intend to support it because the P8 VMX crypto instructions should provide faster AES acceleration and also userspace support for it. The nx_crypto should be blacklisted or disabled in the kernel config for little endian. == Comment: #21 - Cody P. Schafer - 2014-05-14 14:15:28 == Ok, in that case someone needs to submit a patch to add a dependency on BE in the kernel's KConfig. == Comment: #22 - George C. Wilson - 2014-05-14 14:23:46 == Leonidas and Marcelo, could you please submit such a patc
[Kernel-packages] [Bug 1338063] Re: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed
Clarification: I have gone back to older kernels on my machine to confirm my feeling that this only started happening recently. The oldest kernel on my machine is 3.8.0-31-generic. The problem also occurs with when booted with this kernel so my feeling that this was recent is wrong. I have edited the original bug report to remove my assertion that it had seemed to have only started recently. ** Description changed: Using Ubuntu 14.04. Recently updated to kernel version Ubuntu 3.13.0-30.54-generic 3.13.11.2 I expect brightness of my LCD screen to remain the same and be controllable after waking from suspend. It doesn't and isn't. - - This seems to have only started recently - presumably after a recent - update. What happens: Brightness controls fully working after initial boot, both through function keys and system settings. After putting computer into suspend and then re-awakening the LCD screen comes up with lowest brightness in actual appearance but settings still show the brightness as set at suspend time. Controls for brightness have become ineffective - they slide the brightness bar along but make no difference to the actual brightness of the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: john 2060 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: john 2060 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 5 18:55:05 2014 InstallationDate: Installed on 2012-06-04 (760 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=865f4d37-5ceb-4e4a-b59b-032fa8a2c80b ro quiet splash elevator=noop vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-30-generic N/A - linux-backports-modules-3.13.0-30-generic N/A - linux-firmware 1.127.4 + linux-restricted-modules-3.13.0-30-generic N/A + linux-backports-modules-3.13.0-30-generic N/A + linux-firmware 1.127.4 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (68 days ago) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-01W00C:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-01W00C dmi.sys.vendor: TOSHIBA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338063 Title: [Toshiba Portege Z835-ST6N03] Brightness control lost after suspend screen dimmed Status in “linux” package in Ubuntu: Confirmed Bug description: Using Ubuntu 14.04. Recently updated to kernel version Ubuntu 3.13.0-30.54-generic 3.13.11.2 I expect brightness of my LCD screen to remain the same and be controllable after waking from suspend. It doesn't and isn't. What happens: Brightness controls fully working after initial boot, both through function keys and system settings. After putting computer into suspend and then re-awakening the LCD screen comes up with lowest brightness in actual appearance but settings still show the brightness as set at suspend time. Controls for brightness have become ineffective - they slide the brightness bar along but make no difference to the actual brightness of the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 2060 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 5 18:55:05 2014 InstallationDate: Installed on 2012-06-04 (760 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-3
[Kernel-packages] [Bug 1338946] Re: linux: 2.6.32-64.127 -proposed tracker
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-ec2 - bug 1339215 ** 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) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New => In Progress ** Changed in: kernel-sru-workflow/package-testing Status: In Progress => Confirmed ** Description changed: This bug is for tracking the 2.6.32-64.127 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, 08. July 2014 08:49 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Tuesday, 08. July 2014 08:49 UTC + kernel-stable-phase:PPA Testing + kernel-stable-phase-changed:Tuesday, 08. July 2014 17:10 UTC + kernel-stable-Prepare-package-end:Tuesday, 08. July 2014 17:10 UTC + kernel-stable-Promote-to-proposed-start:Tuesday, 08. July 2014 17:10 UTC + ppa-package-testing-start:Tuesday, 08. July 2014 17:10 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/1338946 Title: linux: 2.6.32-64.127 -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-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-ports-meta 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 Lucid: New Bug description: This bug is for tracking the 2.6.32-64.127 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, 08. July 2014 08:49 UTC kernel-stable-phase:PPA Testing kernel-stable-phase-changed:Tuesday, 08. July 2014 17:10 UTC kernel-stable-Prepare-package-end:Tuesday, 08. July 2014 17:10 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 08. July 2014 17:10 UTC ppa-package-testing-start:Tuesday, 08. July 2014 17:10 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1338946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338666] Re: ppc64le kernel module nx_crypto blocks loading other kernel modules
We have this patch queued for our first v3.16 based kernel upload for Utopic (14.10). Marking this Fix Committed for now. ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338666 Title: ppc64le kernel module nx_crypto blocks loading other kernel modules Status in “linux” package in Ubuntu: Fix Committed Bug description: == Comment: #0 - David A. Harnett - 2014-03-12 20:43:09 == ---Problem Description--- On Ubuntu 14.04 ppc64le in a Power7 LPAR , if kernel module nx_crypto is already loaded , attempts to load additional kernel modules fail with this message : modprobe: ERROR: could not insert 'xxx': Invalid argument where xxx is the name of module we tried to load . dmesg shows: [ 33.012917] nx: scatter/gather list overflow, pid: 806 ---uname output--- Linux c277f3u1crash2 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:47:19 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- special PowerVM Little Endian firmware level b0108l_1446.780 Machine Type = Power 780+ 9179-MHD LPAR ---Debugger--- A debugger is not configured ---Steps to Reproduce--- "lsmod" , if nx_crypto module not loaded , then "modprobe nx_crypto" ; try to load any kernel module , "modprobe nfs" Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Dave Harnett/dober...@us.ibm.com , no backup: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. == Comment: #3 - David A. Harnett - 2014-03-12 21:19:42 == Circumvention : add directive "blacklist nx_crypto" to a file in directory /etc/modprobe.d Problem does not occur on Ubuntu 14.04 powerpc64 Big Endian image running in LPAR on same hardware . == Comment: #5 - Leonidas Da Silva Barbosa - 2014-03-13 14:48:17 == David, can you provide us with a cat /etc/issue cat /proc/cpuinfo uname -a from the system where the problem does not happen? == Comment: #6 - David A. Harnett - 2014-03-13 15:24:55 == This is the requested output from the BE image in another LPAR on the same physical machine . $ cat /etc/issue Ubuntu Trusty Tahr (development branch) \n \l $ cat /proc/cpuinfo processor : 0 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 1 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 2 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 3 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) timebase: 51200 platform: pSeries model : IBM,9179-MHD machine : CHRP IBM,9179-MHD $ uname -a Linux c277f3u1admin2 3.13.0-17-powerpc64-smp #37-Ubuntu SMP Mon Mar 10 21:58:15 UTC 2014 ppc64 ppc64 ppc64 GNU/Linux == Comment: #10 - Leonidas Da Silva Barbosa - 2014-03-14 13:19:42 == David, The hardware that are you running both image is over a PowerVM LE ? == Comment: #11 - David A. Harnett - 2014-03-14 13:32:42 == This model Power 780 (Saturn MR class) Power7 machine has special IBM internal use only firmware that permits both LE and BE OS images to run in separate PowerVM LPARs simultaneously . Our contact for the firmware is David Larson , lars...@us.ibm.com This is the third problem I observed on this machine where LE OS has problems but the same function works correctly on a nearly equivalent level of BE OS on the same physical machine . 1) nvram command fails with segfault - to be fixed in powerpc-utils package 2) ibmveth kernel driver for PowerVM virtual ethernet device - fixed in an Ubuntu 14.04 kernel 3) this problem Common thread seems to be drivers that interface with firmware/hardware platform features . == Comment: #17 - Cody P. Schafer - 2014-05-14 14:02:52 == I've seen issues on POWER8-PowerVM-ppc64le with nx-crypto, dmesg attached. note: this is still LE, but is also on P8 (not P7 as this bug was originally reported). == Comment: #18 - Cody P. Schafer - 2014-05-14 14:04:55 == Also, in my case further modules load without issue. The only problem is the log spam. == Comment: #19 - Cody P. Schafer - 2014-05-14 14:05:17 == kernel is v3.15-rc4-260-g38583f0 (from linus's tree) uname -a: Linux host 3.15.0-rc4-testing+ #8 SMP
[Kernel-packages] [Bug 1338666] Re: ppc64le kernel module nx_crypto blocks loading other kernel modules
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338666 Title: ppc64le kernel module nx_crypto blocks loading other kernel modules Status in “linux” package in Ubuntu: Fix Committed Bug description: == Comment: #0 - David A. Harnett - 2014-03-12 20:43:09 == ---Problem Description--- On Ubuntu 14.04 ppc64le in a Power7 LPAR , if kernel module nx_crypto is already loaded , attempts to load additional kernel modules fail with this message : modprobe: ERROR: could not insert 'xxx': Invalid argument where xxx is the name of module we tried to load . dmesg shows: [ 33.012917] nx: scatter/gather list overflow, pid: 806 ---uname output--- Linux c277f3u1crash2 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:47:19 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- special PowerVM Little Endian firmware level b0108l_1446.780 Machine Type = Power 780+ 9179-MHD LPAR ---Debugger--- A debugger is not configured ---Steps to Reproduce--- "lsmod" , if nx_crypto module not loaded , then "modprobe nx_crypto" ; try to load any kernel module , "modprobe nfs" Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Dave Harnett/dober...@us.ibm.com , no backup: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. == Comment: #3 - David A. Harnett - 2014-03-12 21:19:42 == Circumvention : add directive "blacklist nx_crypto" to a file in directory /etc/modprobe.d Problem does not occur on Ubuntu 14.04 powerpc64 Big Endian image running in LPAR on same hardware . == Comment: #5 - Leonidas Da Silva Barbosa - 2014-03-13 14:48:17 == David, can you provide us with a cat /etc/issue cat /proc/cpuinfo uname -a from the system where the problem does not happen? == Comment: #6 - David A. Harnett - 2014-03-13 15:24:55 == This is the requested output from the BE image in another LPAR on the same physical machine . $ cat /etc/issue Ubuntu Trusty Tahr (development branch) \n \l $ cat /proc/cpuinfo processor : 0 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 1 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 2 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) processor : 3 cpu : POWER7 (architected), altivec supported clock : 3724.00MHz revision: 2.0 (pvr 004a 0200) timebase: 51200 platform: pSeries model : IBM,9179-MHD machine : CHRP IBM,9179-MHD $ uname -a Linux c277f3u1admin2 3.13.0-17-powerpc64-smp #37-Ubuntu SMP Mon Mar 10 21:58:15 UTC 2014 ppc64 ppc64 ppc64 GNU/Linux == Comment: #10 - Leonidas Da Silva Barbosa - 2014-03-14 13:19:42 == David, The hardware that are you running both image is over a PowerVM LE ? == Comment: #11 - David A. Harnett - 2014-03-14 13:32:42 == This model Power 780 (Saturn MR class) Power7 machine has special IBM internal use only firmware that permits both LE and BE OS images to run in separate PowerVM LPARs simultaneously . Our contact for the firmware is David Larson , lars...@us.ibm.com This is the third problem I observed on this machine where LE OS has problems but the same function works correctly on a nearly equivalent level of BE OS on the same physical machine . 1) nvram command fails with segfault - to be fixed in powerpc-utils package 2) ibmveth kernel driver for PowerVM virtual ethernet device - fixed in an Ubuntu 14.04 kernel 3) this problem Common thread seems to be drivers that interface with firmware/hardware platform features . == Comment: #17 - Cody P. Schafer - 2014-05-14 14:02:52 == I've seen issues on POWER8-PowerVM-ppc64le with nx-crypto, dmesg attached. note: this is still LE, but is also on P8 (not P7 as this bug was originally reported). == Comment: #18 - Cody P. Schafer - 2014-05-14 14:04:55 == Also, in my case further modules load without issue. The only problem is the log spam. == Comment: #19 - Cody P. Schafer - 2014-05-14 14:05:17 == kernel is v3.15-rc4-260-g38583f0 (from linus's tree) uname -a: Linux host 3.15.0-rc4-testing+ #8 SMP Wed May 14 02:21:38 PDT 2014 ppc64le ppc64le ppc64le GNU/Linux == Comment: #20 - George C. Wilson - 2014-05-14 14:13:32 == Hi Cody. NX crypto isn't supported on li
[Kernel-packages] [Bug 1338924] Re: Some warning messages(''NUMA: Warning: node ids are out of bound'' & ''WARNING: CPU: 5 PID: 0'' & ''warn_slowpath_common'' & ''warn_slowpath_fmt'') log in Ubuntu14.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.
If you are unable to test the mainline kernel, for example it will not boot,
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1338924
Title:
Some warning messages(''NUMA: Warning: node ids are out of bound'' &
''WARNING: CPU: 5 PID: 0'' & ''warn_slowpath_common'' &
''warn_slowpath_fmt'') log in Ubuntu14.04 dmesg.
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Problem Circumstances
==
Test Case ID :9858.1
Affected System: 2
Time to Failure: 30 minutes
Reproducible: Yes,
Current Behavior
==
Some warning messages("NUMA: Warning: node ids are out of bound" & "WARNING:
CPU: 5 PID: 0" & "warn_slowpath_common" & "warn_slowpath_fmt") log in
Ubuntu14.04 dmesg, please refer to attached files.
Reference Verification
==
1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No.
2. Which similar project/product passed? No.
Steps to reproduce the problem
==
1. Install Ubuntu 14.04 UEFI mode.
Expected Behavior
==
No abnormal message log in Ubuntu14.04 dmesg.
Config:
(Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA
2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2
VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000
(2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16
Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2
USB KB/mouse
AHCI
QTFAMW40300028, 31F06MB00E0-B2A
Ubuntu14.04 UEFI mode
Intel I210 OB LAN
AST2400-RKVM
Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID
0,1,5,6,10,50,60,8i,mini-SAS,2,
Delta DPS-650SB A
QTFCMW4140003
0.01
2A06
2.03
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338883] Re: Yama PR_SET_PTRACER_ANY fails on 32-bit user with 64-bit kernel
** Changed in: linux (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338883 Title: Yama PR_SET_PTRACER_ANY fails on 32-bit user with 64-bit kernel Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: New Bug description: This is an old bug that looks like the fix missed Precise since Yama was backported there. Yama was introduced in 3.4, but Precise is 3.2 with Yama backported. The upstream fix for this bug is missing, which can cause problems when a Yama-aware program is running in 32-bit userspace (e.g. chroot) on a 64-bit kernel. Fixed upstream by 2e4930eb7c8fb20a39dfb5f8a8f80402710dcea8 SRU Justification: - impact: Yama programs running in 32-bit chroots will fail to work correctly - test case: prctl(PR_SET_PTRACER, PR_SET_PTRACER_ANY, ...) shouldn't return EINVAL on 32-bit userspace - regression potential: nearly zero. this restores a missing function, and the patch is trivial and upstream for years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338185] Re: networking fails in 32-bit 14.04 using HyperV on Win2012R2
Can you see if this bug also affects the latest 32 bit daily image, which is available from: http://cdimage.ubuntu.com/daily-live/current/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-hyper-v ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338185 Title: networking fails in 32-bit 14.04 using HyperV on Win2012R2 Status in “linux” package in Ubuntu: Confirmed Bug description: I was running Ubuntu 13.10 32-bit as a VM on a Windows Server 2012 R2 machine with Hyper-V. In 32-bit 13.10, networking worked properly at all times, from the first installation to normal usage. I ran the upgrade to 32-bit Ubuntu 14.04 and discovered that networking is no longer working. To eliminate the possibility that there was a botched upgrade, I tried a fresh install in another VM. I performed a fresh install of 32-bit Ubuntu 14.04 in Hyper-V from ubuntu-14.04-desktop-i386.iso, and I noticed that the network was not connecting during the first part of the installation before any files are copied to the disk. After the installation completed, there was no eth0 device present. By comparison, I performed a fresh install of 64-bit Ubuntu 14.04 in Hyper-V from the ubuntu-14.04-desktop-amd64.iso, and networking worked properly at all times from the start of installation. To summarize, networking is failing in 32-bit Ubuntu 14.04 under Hyper-V in Windows Server 2012 R2. Networking is working properly in 32-bit Ubuntu 13.10 on the same machine. Networking is working properly in 64-bit Ubuntu 14.04 on the same machine. Any suggestions on getting 32-bit Ubuntu 14.04 to work in my Hyper-V VM ? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339196] Re: keypad stops working
Does this issue go away if you boot into the prior kernel? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1339196 Title: keypad stops working Status in “linux” package in Ubuntu: Incomplete Bug description: This started with a recent update. Using 3.13.0-30-generic Ubuntu 64 bit 14.04 LTS. 1: The keystrokes suddenly stop working e.g. when using LYX [latest version]. 2: The text input stops and moves to the beginning of the previously written line and overrights it [although hitting return will still execute the full line] e.g. when using R [latest version]. The problem does not occur on my 32-bit system only the 64 bit. System characteristics: Gigabyte Ultra board Keyboard: logitech K330 Mouse: Logitech M215 Memory: 15.6 GiB Processor: AMDA10-6800K APU with Radeon HD Graphics x4 Graphics: Gallium 04 on AMD RV670 Disk: 980.1 GB I've tried to fix it for a couple of weeks now but could not. Any ideas what is wrong. George Hart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338724] Re: Nouveau video artifact and system freezes with NVIDIA Geforce 8300 on Ubuntu 14.04 amd64
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338724 Title: Nouveau video artifact and system freezes with NVIDIA Geforce 8300 on Ubuntu 14.04 amd64 Status in “linux” package in Ubuntu: Incomplete Bug description: I'm sorry I cannot use Nouvea driver with NVIDIA Geforce 8300, embedded on system board Asus M3N78-EM, since after it displays some artifacts, the system freezes and I have to force shutdown with power button I tried both with standard and updated these packages: ii libdrm-nouveau2:amd64 2.4.54+git20140628.e8c3c135-0ubuntu0ricotz~trusty amd64 ii xserver-xorg-video-nouveau 1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt amd64 I have to use nvidia closed-source driver (sigh), version 304 seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2266 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 20:37:17 2014 HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35 InstallationDate: Installed on 2014-06-22 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338649] Re: Ricoh sd card reader no longer working
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338649 Title: Ricoh sd card reader no longer working Status in “linux” package in Ubuntu: Incomplete Bug description: I have a Thinkpad T410i with a Ricoh SD card reader slot: http://www.thinkwiki.org/wiki/Ricoh_5-in-1_MultiCard_Reader 0d:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: sdhci-pci Under Ubuntu 10.04 this worked fine for SD cards. I've recently reinstalled with 14.04 and now there is no response whatsoever when an SD card is inserted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andy 6496 F pulseaudio /dev/snd/pcmC0D0p: andy 6496 F...m pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 17:04:43 2014 HibernationDevice: RESUME=/dev/mapper/duvel--vg-swap_1 MachineType: LENOVO 2516CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338622] Re: LCD monitor timing misdetected: 60Hz != 60 Hz
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338622 Title: LCD monitor timing misdetected: 60Hz != 60 Hz Status in “linux” package in Ubuntu: Incomplete Bug description: X is not correctly detecting my monitors' timings. Despite being a digital connection (with allegedly EDID), I have to force a modeline with xrandr. The graphical xrandr tools (arandr, or KDE's system- settings) do not work. I used to think this was solved with the binary drivers (first nvidia, then fglrx), but I now realise that a modeline can be generated with xrandr and they will work with the open-source driver. The 1600x1200 monitors are a pair of 20" 1600x1200 VideoSeven devices, purchased in 2006, with DVI and VGA inputs. I'm using both of the DVI inputs, (one of which via an HDMI/DVI adapter cable). They tend to be a bit fussy about being driven at the required 60Hz x 75 kHz, saying that the signal is out of range: they need 60x75, they are getting 60x75, but it's not good enough!). I attach xorg.log to this. Also, here is what I get when I run xrandr (to list modes), then when I run my xrandr.sh script , then xrandr again. The 60 Hz mode is now listed as "59.9". I'm filing this on xserver-xorg-core (2:1.15.1-0ubuntu8), though it might be a video-driver bug: xserver-xorg-video-radeon #Output of Xrandr. At this point, only the DisplayPort monitor works rightly. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 4800 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1600x1200+3200+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0 + 1920x1080 50.0 1600x1200 60.0* 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 HDMI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 408mm x 306mm 1600x1200 60.0*+ 1280x1024 85.0 75.0 60.0 1024x768 85.0 75.1 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 75.0 72.8 66.7 60.0 720x40070.1 Now I run xrandr.sh, to add and apply new modes. [rjn@chocolate ~]$ ./bin/xrandr.sh This sets up my 3-head display. It can be called from ssh, as the display is forced to :0 * The 2x VideoSeven 1600x1200 displays don't normally light up at all (they think the signal is out of range at 60 Hz, Xrandr's version is 59.9 Hz) * The Samsung monitor (1920x1200) comes up at 1600x1200 * Everything is cloned, rather than 3 in a row The modelines for the VideoSeven displays are from 'cvt 1600 1200 60' . Now doing it... this may take a few seconds... Creating new mode 1600x1200_60.00... Adding this mode for the DVI-0 and HDMI-0 outputs... Setting the modes and DPIs for the 3 outputs DVI-0, HDMI-0, DisplayPort-0... Arranging the displays 3 in a row (DVI-0, HDMI-0, DisplayPort-0)... Done Now, all monitors work as they should, and here is the output of xrandr again. [rjn@chocolate ~]$ xrandr -d :0 Screen 0: minimum 320 x 200, current 5120 x 1200, maximum 16384 x 16384 DisplayPort-0 connected 1920x1200+3200+0 (normal left inverted
[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.14.1 kernel-bug-exists-upstream-3.14.11 kernel-bug-exists- upstream-3.16-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/1338706 Title: Samsung SSD 840 Series failed to set xfermode (err_mask=0x40) on Trusty with upstream kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2131 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 20:01:28 2014 HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35 InstallationDate: Installed on 2014-06-22 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338724] Re: Nouveau video artifact and system freezes with NVIDIA Geforce 8300 on Ubuntu 14.04 amd64
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.14.1 kernel-bug-exists-upstream-3.14.11 kernel-bug-exists- upstream-3.16-rc4 latest-bios-0901 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338724 Title: Nouveau video artifact and system freezes with NVIDIA Geforce 8300 on Ubuntu 14.04 amd64 Status in “linux” package in Ubuntu: Incomplete Bug description: I'm sorry I cannot use Nouvea driver with NVIDIA Geforce 8300, embedded on system board Asus M3N78-EM, since after it displays some artifacts, the system freezes and I have to force shutdown with power button I tried both with standard and updated these packages: ii libdrm-nouveau2:amd64 2.4.54+git20140628.e8c3c135-0ubuntu0ricotz~trusty amd64 ii xserver-xorg-video-nouveau 1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt amd64 I have to use nvidia closed-source driver (sigh), version 304 seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2266 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 20:37:17 2014 HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35 InstallationDate: Installed on 2014-06-22 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 Series failed to set xfermode (err_mask=0x40) on Trusty with upstream kernel
Thanks Christopher, I tested with 3 kernels and 2 upstream. The error changed from Trusty 3.13.0-30-generic to upstream kernels: from: failed to get NCQ Send/Recv Log Emask 0x1 > failed to set xfermode (err_mask=0x40) Maybe I need to edit the subject? ** Summary changed: - Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1 + Samsung SSD 840 Series failed to set xfermode (err_mask=0x40) on Trusty with upstream 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/1338706 Title: Samsung SSD 840 Series failed to set xfermode (err_mask=0x40) on Trusty with upstream kernel Status in “linux” package in Ubuntu: Confirmed Bug description: Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2131 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 7 20:01:28 2014 HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35 InstallationDate: Installed on 2014-06-22 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339238] [NEW] bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build
Public bug reported: Automatically generated BR ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 [modified: usr/src/bcmwl-6.30.223.141+bdcom/Makefile usr/src/bcmwl-6.30.223.141+bdcom/src/wl/sys/wl_dbg.h] Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-30-generic Date: Sun Jul 6 20:33:16 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.141+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c:762:2: error: implicit declaration of function ‘wlc_dump_register’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2014-04-26 (73 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageVersion: 6.30.223.141+bdcom-0ubuntu2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1339238 Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: New Bug description: Automatically generated BR ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 [modified: usr/src/bcmwl-6.30.223.141+bdcom/Makefile usr/src/bcmwl-6.30.223.141+bdcom/src/wl/sys/wl_dbg.h] Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-30-generic Date: Sun Jul 6 20:33:16 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.141+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c:762:2: error: implicit declaration of function ‘wlc_dump_register’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2014-04-26 (73 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageVersion: 6.30.223.141+bdcom-0ubuntu2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1339238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338919] Re: The information - CPU cores is incorrect in Ubuntu14.04 cpuinfo.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338919 Title: The information - CPU cores is incorrect in Ubuntu14.04 cpuinfo. Status in “linux” package in Ubuntu: Incomplete Bug description: Problem Circumstances == Test Case ID :9859.2 Affected System: 2 Time to Failure: Immediately Reproducible: Yes, Current Behavior == Boot into Ubuntu 14.04, then type command "cat /proc/cpuinfo" to check CPU information, the information - CPU cores is incorrect, please refer to attached photo. Reference Verification == 1. Which version of previous BIOS/BMC/BootUp/Runtime/HW passed? No. 2. Which similar project/product passed? No. Steps to reproduce the problem == 1.Boot into Ubuntu 14.04 2.type command "cat /proc/cpuinfo" to check CPU information Expected Behavior == The information - CPU cores is correct in Ubuntu14.04 cpuinfo. Config: (Intel) CPU,Haswell-EP,10 core,2.3GHz,2133,M0,LGA 2011,256KB/core,105W,25MB,QG99,933972,9.6GT/s, *2 VendorP/N: MTA18ASF1G72PZ-2G1A2KG, Memory,4FA72D9RGV,DDR4,17000 (2133MHz),8GB,Register,NA,15,by 4,1 rank, Qty:16 Model: ST900MM0006, HDD,SASII,900GB,SAS,10 Krpm,2.5 *2 USB KB/mouse AHCI QTFAMW40300028, 31F06MB00E0-B2A Ubuntu14.04 UEFI mode Intel I210 OB LAN AST2400-RKVM Quanta, Storage Card,LSISAS2208,SATA+SAS,PCI-E X8,Gen 3,Mezz card,RAID 0,1,5,6,10,50,60,8i,mini-SAS,2, Delta DPS-650SB A QTFCMW4140003 0.01 2A06 2.03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339238] Re: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1339238 Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: New Bug description: Automatically generated BR ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 [modified: usr/src/bcmwl-6.30.223.141+bdcom/Makefile usr/src/bcmwl-6.30.223.141+bdcom/src/wl/sys/wl_dbg.h] Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-30-generic Date: Sun Jul 6 20:33:16 2014 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.141+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_linux.c:762:2: error: implicit declaration of function ‘wlc_dump_register’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2014-04-26 (73 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageVersion: 6.30.223.141+bdcom-0ubuntu2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1339238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 362875] Re: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset
I'm encountering exactly the same bug with rt73 drivers for onboard ralink wifi chip.. Ubuntu-based LInux Mint 17.. And 3.14--30 kernels.. What th eheck! This is still a bug?! 5 years and no solution?! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/362875 Title: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset Status in “linux” package in Ubuntu: Expired Bug description: Binary package hint: linux-firmware Dear friends, [24225.012753] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24225.017901] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24225.022279] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.005773] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24226.011307] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24226.015147] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24226.020486] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24226.024151] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.003532] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71. [24227.007269] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71. [24227.020153] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. [24227.023895] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71. [24227.027645] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71. This is an example of the message I'm continually getting. ID 148f:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter Many blessings. ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 Package: linux-restricted-modules None [modified: /var/lib/dpkg/info/linux-restricted-modules.list] ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 SourcePackage: linux-meta Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
Matt, can you post config file that you used? I tried a few different configurations and (again) could not reproduce this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336135] Re: CVE-2014-4667
** Changed in: linux (Ubuntu Utopic) 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/1336135 Title: CVE-2014-4667 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: 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-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” 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: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New 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-fsl-imx51” 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-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-fsl-imx51” 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: [sctp: sk_ack_backlog wrap-around problem] DOS Break-Fix: de76e695a5ce19c121ba7e246b45f258be678a75 d3217b15a19a4779c39b212358a5c71d725822ee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335314] Re: CVE-2014-4611
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Saucy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) 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/1335314 Title: CVE-2014-4611 Status in “linux” package in Ubuntu: Fix Committed Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” 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-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux” source package in Lucid: Invalid Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Invalid Status in “linux-fsl-imx51” source package in Lucid: 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-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid 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-fsl-imx51” 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: Fix Committed 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 Saucy: Fix Committed Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: Invalid Status in “linux” source package in Trusty: Fix Committed Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” 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-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-fsl-imx51” 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-mvl-dove” source package in Utopic: Invalid Status in “linux-ti-omap4” source package in Utopic: Invalid Bug description: All versions of the LZ4 software:https://code.google.com/p/lz4 Functions Affected: lz4.c:LZ4_decompress_generic Criticality Reasoning - Due to the design of the algorithm, an attacker can specify any desired offset to a write pointer. The attacker can instrument the write in such a way as to only write four bytes at a specified offset. Subsequent code will allow t
Re: [Kernel-packages] [Bug 1339196] Re: keypad stops working
No it actually started with the prior kernel. I have since cleaned all of the prior kernels from my system. On 07/08/2014 11:22 AM, Joseph Salisbury wrote: > Does this issue go away if you boot into the prior kernel? > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > > ** Tags added: needs-bisect > -- George F. Hart, Ph.D. Professor emeritus, Department of Geology and Geophysics, LSU. Academic web: www.geol.lsu.edu/Faculty/Hart Personal web: www.ScienceAnd.net Commercial web: www.ClaredLune.com House web: www.BisonEstate.com eMails: gh...@lsu.edu z...@mric.net -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1339196 Title: keypad stops working Status in “linux” package in Ubuntu: Incomplete Bug description: This started with a recent update. Using 3.13.0-30-generic Ubuntu 64 bit 14.04 LTS. 1: The keystrokes suddenly stop working e.g. when using LYX [latest version]. 2: The text input stops and moves to the beginning of the previously written line and overrights it [although hitting return will still execute the full line] e.g. when using R [latest version]. The problem does not occur on my 32-bit system only the 64 bit. System characteristics: Gigabyte Ultra board Keyboard: logitech K330 Mouse: Logitech M215 Memory: 15.6 GiB Processor: AMDA10-6800K APU with Radeon HD Graphics x4 Graphics: Gallium 04 on AMD RV670 Disk: 980.1 GB I've tried to fix it for a couple of weeks now but could not. Any ideas what is wrong. George Hart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1339196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
Not precisely. What toolstack are you using? I can try to reproduce outside of our control plane with a config file that would work on your toolstack. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1336485] Re: [HP Pavilion dv6t-7000 CTO Entertainment Notebook PC] suspend/resume failure
No, today I noticed that if I leave it hibrenating for a while (4hrs+) than it does not do this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1336485 Title: [HP Pavilion dv6t-7000 CTO Entertainment Notebook PC] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: "Fixed but needed restart"??? ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.15.0-6-generic 3.15.0-6.11 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaahh 2555 F pulseaudio Date: Tue Jul 1 10:54:28 2014 DuplicateSignature: suspend/resume:Hewlett-Packard HP Pavilion dv6 Notebook PC:F.29 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1403099049 Failure: suspend/resume HibernationDevice: RESUME=UUID=46299c15-e9a2-44ad-b58a-6ef48099477a InstallationDate: Installed on 2014-06-27 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-6-generic root=UUID=5ee7f7cb-22cc-4bfa-b5ac-1c4d0577a870 ro acpi_osi=Linux acpi_backlight=vendor intel_pstate=enable quiet splash acpi_osi=Linux acpi_backlight=vendor intel_pstate=enable vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.15.0-6-generic N/A linux-backports-modules-3.15.0-6-generic N/A linux-firmware1.132 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/03/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181E dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.29:bd10/03/2013:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr07901020571620100:rvnHewlett-Packard:rn181E:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 07901020571620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
I am using 4.2 stable tree, configured with default parameters (i.e. no options to ./configure script): [root@ovs103 install]# xm info host : ovs103.us.oracle.com release: 3.16.0-rc1-pmu-dom0 version: #1 SMP Mon Jul 7 14:09:40 EDT 2014 machine: x86_64 nr_cpus: 32 nr_nodes : 4 cores_per_socket : 8 threads_per_core : 2 cpu_mhz: 2800 hw_caps: 178bf3ff:2fd3fbff::1710:36983203::01ebbfff:0008 virt_caps : hvm total_memory : 65534 free_memory: 856 free_cpus : 0 xen_major : 4 xen_minor : 2 xen_extra : .5-rc1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: console=com1,vga com1=38400,8n1 cc_compiler: gcc (GCC) 4.4.6 20110731 (Red Hat 4.4.6-3) cc_compile_by : root cc_compile_domain : us.oracle.com cc_compile_date: Mon Jul 7 19:12:25 EDT 2014 xend_config_format : 4 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/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
And this is my guest (14.04 desktop): Linux version 3.13.0-24-generic (buildd@panlong) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 (Ubuntu 3.13.0-24.46-generic 3.13.9) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339294] [NEW] CVE-2014-4652
*** This bug is a security vulnerability *** Public security bug reported: Race condition in the tlv handler functionality in the snd_ctl_elem_user_tlv function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 allows local users to obtain sensitive information from kernel memory by leveraging /dev/snd/controlCX access. Break-Fix: - 07f4d9d74a04aa7c72c5dae0ef97565f28f17b92 ** Affects: linux (Ubuntu) Importance: Medium Status: Fix Committed ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided S
[Kernel-packages] [Bug 1339294] Re: CVE-2014-4652
CVE-2014-4652 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Ch
[Kernel-packages] [Bug 1339297] [NEW] CVE-2014-4653
*** This bug is a security vulnerability *** Public security bug reported: sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not ensure possession of a read/write lock, which allows local users to cause a denial of service (use-after-free) and obtain sensitive information from kernel memory by leveraging /dev/snd/controlCX access. Break-Fix: - fd9f26e4eca5d08a27d12c0933fceef76ed9663d ** Affects: linux (Ubuntu) Importance: Medium Status: Fix Committed ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecid
[Kernel-packages] [Bug 1339297] Re: CVE-2014-4653
CVE-2014-4653 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Ch
[Kernel-packages] [Bug 1339303] [NEW] CVE-2014-4654
*** This bug is a security vulnerability *** Public security bug reported: The snd_ctl_elem_add function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not check authorization for SNDRV_CTL_IOCTL_ELEM_REPLACE commands, which allows local users to remove kernel controls and cause a denial of service (use-after-free and system crash) by leveraging /dev/snd/controlCX access for an ioctl call. Break-Fix: - 82262a46627bebb0febcc26664746c25cef08563 ** Affects: linux (Ubuntu) Importance: Medium Status: Fix Committed ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects:
[Kernel-packages] [Bug 1339303] Re: CVE-2014-4654
CVE-2014-4654 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Ch
[Kernel-packages] [Bug 1339304] [NEW] CVE-2014-4655
*** This bug is a security vulnerability *** Public security bug reported: The snd_ctl_elem_add function in sound/core/control.c in the ALSA control implementation in the Linux kernel before 3.15.2 does not properly maintain the user_ctl_count value, which allows local users to cause a denial of service (integer overflow and limit bypass) by leveraging /dev/snd/controlCX access for a large number of SNDRV_CTL_IOCTL_ELEM_REPLACE ioctl calls. Break-Fix: - 82262a46627bebb0febcc26664746c25cef08563 ** Affects: linux (Ubuntu) Importance: Medium Status: Fix Committed ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Saucy) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects
[Kernel-packages] [Bug 1339304] Re: CVE-2014-4655
CVE-2014-4655 ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ec2 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Saucy) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Lucid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Ch
