[Kernel-packages] [Bug 1265544] Re: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7
/es/ed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in “linux” package in Ubuntu: In Progress Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 578173] Re: [regression-release] Computer locks when switching screen, forcing user to do a hard poweroff, so causing massive data loss and hardware damage
** No longer affects: linux (Ubuntu) ** Changed in: xserver-xorg-video-ati (Ubuntu) Importance: Undecided = Low ** Changed in: xserver-xorg-video-ati (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/578173 Title: [regression-release] Computer locks when switching screen, forcing user to do a hard poweroff, so causing massive data loss and hardware damage Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: Binary package hint: xorg Since I upgrade to Lucid, Cannot switch to virtual terminals with Ctrl+Alt+F1. The screen goes black, there is no terminal. Starting another graphical section works. But when switching back the computer gets locked by a black screen with a mouse pointer, and the only way out is unplugging power. Files attached. --- Architecture: i386 DistroRelease: Ubuntu 10.04 DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.31-19-generic, i686: installed bcmwl, 5.60.48.36+bdcom, 2.6.32-22-generic, i686: installed bcmwl, 5.60.48.36+bdcom, 2.6.32-21-generic, i686: installed InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU SIEMENS AMILO Li 1718 Package: xorg 1:7.5+5ubuntu1 PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=c8889081-7814-4a9d-9f0c-bd587d56d851 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-22-generic i686 UserGroups: adm admin audio cdrom dialout dip lpadmin plugdev sambashare dmi.bios.date: 11/12/07 dmi.bios.vendor: Phoenix dmi.bios.version: V1.9 dmi.board.name: AMILO Li 1718 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: Rev.A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: ATI dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.9:bd11/12/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A: dmi.product.name: AMILO Li 1718 dmi.product.version: -1 dmi.sys.vendor: FUJITSU SIEMENS system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/578173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1263015] Re: 8086:0a16 [ASUS Zenbook UX302LG] Black screen on boot
Just tried the workaround proposed here (use drm-intel-nightly kernel, removed nvidia-prime, and remove nomodeset from grub options) and it works just as good, probably a bit better: I can plug-in an external screen, though I lost the main screen if I am to unplug/deactivate the external screen. Suspend seems to fail just as before (blank screen, yet functioning system on resume). I assume those two issues are for another bug report anyway. Note to @penalvch: the previous comment was another workaround for this bug that worked for me, not another bug report. Do you still want me to fill in a new report? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263015 Title: 8086:0a16 [ASUS Zenbook UX302LG] Black screen on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Install via LiveUSB created with unetbootin off the saucy amd64 iso was able to be completed with nomodeset. First boot into installed system resulted in lightdm cowbell being played but a backlight on / blank screen on the display. using nomodeset on installed system results in framebuffer/console being usable - but no X able to start (cannot find screen). tried some alternative kernel options : acpi_backlight=vendor, video=1920x1080-24@60 but with same results. Tried using different kernel as per bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195483 . pinned and upgraded to trusty kernel images - slightly different result in that backlight goes down and breifly have a red screen tear in upper left of screen for several seconds before reverting to same behaviour as saucy kernel. (blanked screen, backlit, lightdm cowbell plays). WORKAROUND: Upstream drm-intel-next build resulted in working lightdm/screen: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2013-12-18-trusty/ -- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1466 F pulseaudio /dev/snd/controlC0: lightdm1466 F pulseaudio CRDA: country SG: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 20) DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=808c568f-76fa-46d3-9e60-276860ebe1ec InstallationDate: Installed on 2013-12-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG MarkForUpload: True Package: linux 3.11.0.15.16 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=c4550a46-5cb3-4033-ac7f-3bc9d38959f8 ro ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 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.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 Tags: saucy package-from-proposed Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-20 (0 days ago) UserGroups: dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1263015] Re: 8086:0a16 [ASUS Zenbook UX302LG] Black screen on boot
Emmanuel, yes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263015 Title: 8086:0a16 [ASUS Zenbook UX302LG] Black screen on boot Status in “linux” package in Ubuntu: Incomplete Bug description: Install via LiveUSB created with unetbootin off the saucy amd64 iso was able to be completed with nomodeset. First boot into installed system resulted in lightdm cowbell being played but a backlight on / blank screen on the display. using nomodeset on installed system results in framebuffer/console being usable - but no X able to start (cannot find screen). tried some alternative kernel options : acpi_backlight=vendor, video=1920x1080-24@60 but with same results. Tried using different kernel as per bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195483 . pinned and upgraded to trusty kernel images - slightly different result in that backlight goes down and breifly have a red screen tear in upper left of screen for several seconds before reverting to same behaviour as saucy kernel. (blanked screen, backlit, lightdm cowbell plays). WORKAROUND: Upstream drm-intel-next build resulted in working lightdm/screen: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2013-12-18-trusty/ -- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1466 F pulseaudio /dev/snd/controlC0: lightdm1466 F pulseaudio CRDA: country SG: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 20) DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=808c568f-76fa-46d3-9e60-276860ebe1ec InstallationDate: Installed on 2013-12-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG MarkForUpload: True Package: linux 3.11.0.15.16 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=c4550a46-5cb3-4033-ac7f-3bc9d38959f8 ro ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 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.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 Tags: saucy package-from-proposed Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-20 (0 days ago) UserGroups: dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267009] [NEW] [ASUS Zenbook UX302LG] Black screen on boot
Public bug reported: Tried the same than bug #1263015 but came up with a different workaround. Install via LiveUSB created with unetbootin off the saucy amd64 iso was able to be completed with nomodeset. First boot into installed system resulted in lightdm cowbell being played but a backlight on / blank screen on the display. using nomodeset on installed system results in framebuffer/console being usable - but no X able to start (cannot find screen). tried some alternative kernel options : acpi_backlight=vendor, video=1920x1080-24@60 but with same results. WORKAROUND: set nomodeset in grub config, and install nvidia-prime package. Reboot. lightdm/screen works fine, however some video-related features are still broken, such as external screen (not even detected) and suspend to RAM (comes back alright from suspend, but for the screen that stays black). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: emmanuel 2659 F pulseaudio /dev/snd/controlC0: emmanuel 2659 F pulseaudio Date: Wed Jan 8 16:18:20 2014 InstallationDate: Installed on 2013-12-17 (21 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. UX302LG MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=d7e8b6d8-79ae-4f7a-99d0-fff2865f82cd ro quiet splash nomodeset rootfstype=ext4 acpi_osi=!Windows 2012 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1267009 Title: [ASUS Zenbook UX302LG] Black screen on boot Status in “linux” package in Ubuntu: Confirmed Bug description: Tried the same than bug #1263015 but came up with a different workaround. Install via LiveUSB created with unetbootin off the saucy amd64 iso was able to be completed with nomodeset. First boot into installed system resulted in lightdm cowbell being played but a backlight on / blank screen on the display. using nomodeset on installed system results in framebuffer/console being usable - but no X able to start (cannot find screen). tried some alternative kernel options : acpi_backlight=vendor, video=1920x1080-24@60 but with same results. WORKAROUND: set nomodeset in grub config, and install nvidia-prime package. Reboot. lightdm/screen works fine, however some video-related features are still broken, such as external screen (not even detected) and suspend to RAM (comes back alright from suspend, but for the screen that stays black). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: emmanuel 2659 F pulseaudio /dev/snd/controlC0: emmanuel 2659 F pulseaudio Date: Wed Jan 8 16:18:20 2014 InstallationDate: Installed on 2013-12-17 (21 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. UX302LG MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=d7e8b6d8-79ae-4f7a-99d0-fff2865f82cd ro quiet splash nomodeset rootfstype=ext4 acpi_osi=!Windows 2012 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1267009] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1267009 Title: [ASUS Zenbook UX302LG] Black screen on boot Status in “linux” package in Ubuntu: Confirmed Bug description: Tried the same than bug #1263015 but came up with a different workaround. Install via LiveUSB created with unetbootin off the saucy amd64 iso was able to be completed with nomodeset. First boot into installed system resulted in lightdm cowbell being played but a backlight on / blank screen on the display. using nomodeset on installed system results in framebuffer/console being usable - but no X able to start (cannot find screen). tried some alternative kernel options : acpi_backlight=vendor, video=1920x1080-24@60 but with same results. WORKAROUND: set nomodeset in grub config, and install nvidia-prime package. Reboot. lightdm/screen works fine, however some video-related features are still broken, such as external screen (not even detected) and suspend to RAM (comes back alright from suspend, but for the screen that stays black). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: emmanuel 2659 F pulseaudio /dev/snd/controlC0: emmanuel 2659 F pulseaudio Date: Wed Jan 8 16:18:20 2014 InstallationDate: Installed on 2013-12-17 (21 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. UX302LG MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=d7e8b6d8-79ae-4f7a-99d0-fff2865f82cd ro quiet splash nomodeset rootfstype=ext4 acpi_osi=!Windows 2012 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266680] Re: Localization support for nvidia-settings
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1266680 Title: Localization support for nvidia-settings Status in NVIDIA Drivers Ubuntu: New Status in Ubuntu Translations: New Status in “nvidia-settings” package in Ubuntu: New Bug description: On Ubuntu 14.04 dev with nvidia-settings 331.20-0ubuntu6 it is still only in english. Maybe nvidia-settings can be enhanced to support language files too at some point in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1266680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266852] Re: linux: 3.13.0-1.16 -proposed tracker
This bug was fixed in the package linux - 3.13.0-1.16 --- linux (3.13.0-1.16) trusty; urgency=low * First 3.13 upload. * Release tracker - LP: #1266852 linux (3.13.0-0.15) trusty; urgency=low [ Tim Gardner ] * rebase to v3.13-rc7 [ Upstream Kernel Changes ] * rebase to v3.13-rc7 linux (3.13.0-0.14) trusty; urgency=low [ Andy Whitcroft ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 [ Tim Gardner ] * Remove ubuntu/dm-raid4-5 in favor of CONFIG_MD_RAID456 * Update lttng to Version 2.4.0-rc2 * lttng: Disabled trace_kvm_async_pf_completed * [Config] CONFIG_IMA=y - LP: #1244627 [ Upstream Kernel Changes ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 linux (3.13.0-0.13) trusty; urgency=low [ Andy Whitcroft ] * ubuntu: aufs3 -- (no-up) aufs3-base.patch * ubuntu: aufs3 -- (no-up) aufs3-mmap.patch * ubuntu: aufs3 -- (no-up) aufs3-standalone.patch * ubuntu: AUFS (no-squash): basic framework and update machinary * ubuntu: AUFS -- update to 7b136a27b021da9010d8b6c101939dd298e46be7 * ubuntu: aufs3 -- enable * ubuntu: aufs3 -- update configs linux (3.13.0-0.12) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to v3.13-rc6 linux (3.13.0-0.11) trusty; urgency=low [ Andy Whitcroft ] * SAUCE: suspicious unlocked -status reading and writing in ipc/sem.c * [Config] ppc64el -- initial defconfig based -generic flavour * [Config] initial defconfig for ppc64el * [Config] ubuntuise ppc64el config * [Config] ubuntuise ppc64el config part 2 * [Config] d-i -- update empty udebs list * [Config] ppc64el -- split extras package [ Anton Blanchard ] * SAUCE: KVM: PPC: Book3S HV: Add little-endian guest support [ Benjamin Herrenschmidt ] * SAUCE: powerpc/powernv: Add calls to support little endian [ Cédric Le Goater ] * SAUCE: KVM: PPC: Book3S: add helper routine to load guest instructions * SAUCE: KVM: PPC: Book3S: add helper routines to detect endian order * SAUCE: KVM: PPC: Book3S: MMIO emulation support for little endian guests [ Paul E. McKenney ] * SAUCE: powerpc: Make 64-bit non-VMX copy_tofrom_user() bi-endian linux (3.13.0-0.10) trusty; urgency=low [ Andy Whitcroft ] * rebase to v3.13-rc5 * [Config] updateconfigs following rebase to v3.13-rc5 [ Upstream Kernel Changes ] * rebase to v3.13-rc5 - LP: #1260303 - LP: #1260303 - LP: #1260225 linux (3.13.0-0.9) trusty; urgency=low [ Andy Whitcroft ] * [Config] d-i -- allow missing firmware linux (3.13.0-0.8) trusty; urgency=low [ Andy Whitcroft ] * [Config] annotations -- first pass over entire config * [Config] drop libunwind8-dev from Build-Depends for ppc64el [ Tim Gardner ] * [Config] Add arm64 device tree files - LP: #1262901 linux (3.13.0-0.7) trusty; urgency=low [ Rajesh B Prathipati ] * SAUCE: powerpc: Make unaligned accesses endian-safe for powerpc [ Tim Gardner ] * [Config] CONFIG_REGULATOR_S2MPS11=n for FTBS [ Upstream Kernel Changes ] * rebase to v3.13-rc4 - LP: #1259790 - LP: #1259437 - LP: #1259435 linux (3.13.0-0.6) trusty; urgency=low [ Paolo Pisati ] * [Config] armhf: arm64: VIRTIO_[BLK|MMIO|NET|CONSOLE|BALLOON]=y * [Config] i386: amd64: VIRTIO_CONSOLE=y [ Tim Gardner ] * [Config] CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y linux (3.13.0-0.5) trusty; urgency=low [ Andy Whitcroft ] * correct bug listing for v3.13-rc2 rebase * [Config] ppc64el -- create linux-libc-dev * [Debian] Improve tools version message - LP: #1257715 [ Serge Hallyn ] * SAUCE: fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)] - LP: #1248590 * SAUCE: vfs: Fix a regression in mounting proc [ Tim Gardner ] * [Config] Build-in ohci-pci - LP: #1244176 * Rebase to v3.13-rc3 [ Upstream Kernel Changes ] * Revert Revert fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks - LP: #1248590 [ Upstream Kernel Changes ] * rebase to v3.13-rc3 - LP: #1256840 - LP: #1256212 linux (3.13.0-0.4) trusty; urgency=low [ Tim Gardner ] * Rebase to v3.13-rc2 [ Upstream Kernel Changes ] * rebase to v3.13-rc2 linux (3.13.0-0.3) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: Fix DocBook FTBS [ Tim Gardner ] * [Debian] Re-sign modules after debug objcopy - LP: #1253155 * [Config] CONFIG_EXT4_USE_FOR_EXT23=y [ Upstream Kernel Changes ] * doc: fix generation of device-drivers * rebase to b975dc3689fc6a3718ad288ce080924f9cb7e176 linux (3.13.0-0.2) trusty; urgency=low [ Tim Gardner ] * SAUCE: Fix DocBook FTBS linux (3.13.0-0.1) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to 7e3528c3660a2e8602abc7858b0994d611f74bc3 linux (3.13.0-0.0) trusty; urgency=low * Major release bump. -- Tim Gardner tim.gard...@canonical.com Tue, 07 Jan 2014 09:21:26 -0700 ** Changed in: linux (Ubuntu Trusty) Status: New = Fix Released -- You
[Kernel-packages] [Bug 1260303] Re: No external microphone detected on the machines with codec alc269 family
This bug was fixed in the package linux - 3.13.0-1.16 --- linux (3.13.0-1.16) trusty; urgency=low * First 3.13 upload. * Release tracker - LP: #1266852 linux (3.13.0-0.15) trusty; urgency=low [ Tim Gardner ] * rebase to v3.13-rc7 [ Upstream Kernel Changes ] * rebase to v3.13-rc7 linux (3.13.0-0.14) trusty; urgency=low [ Andy Whitcroft ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 [ Tim Gardner ] * Remove ubuntu/dm-raid4-5 in favor of CONFIG_MD_RAID456 * Update lttng to Version 2.4.0-rc2 * lttng: Disabled trace_kvm_async_pf_completed * [Config] CONFIG_IMA=y - LP: #1244627 [ Upstream Kernel Changes ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 linux (3.13.0-0.13) trusty; urgency=low [ Andy Whitcroft ] * ubuntu: aufs3 -- (no-up) aufs3-base.patch * ubuntu: aufs3 -- (no-up) aufs3-mmap.patch * ubuntu: aufs3 -- (no-up) aufs3-standalone.patch * ubuntu: AUFS (no-squash): basic framework and update machinary * ubuntu: AUFS -- update to 7b136a27b021da9010d8b6c101939dd298e46be7 * ubuntu: aufs3 -- enable * ubuntu: aufs3 -- update configs linux (3.13.0-0.12) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to v3.13-rc6 linux (3.13.0-0.11) trusty; urgency=low [ Andy Whitcroft ] * SAUCE: suspicious unlocked -status reading and writing in ipc/sem.c * [Config] ppc64el -- initial defconfig based -generic flavour * [Config] initial defconfig for ppc64el * [Config] ubuntuise ppc64el config * [Config] ubuntuise ppc64el config part 2 * [Config] d-i -- update empty udebs list * [Config] ppc64el -- split extras package [ Anton Blanchard ] * SAUCE: KVM: PPC: Book3S HV: Add little-endian guest support [ Benjamin Herrenschmidt ] * SAUCE: powerpc/powernv: Add calls to support little endian [ Cédric Le Goater ] * SAUCE: KVM: PPC: Book3S: add helper routine to load guest instructions * SAUCE: KVM: PPC: Book3S: add helper routines to detect endian order * SAUCE: KVM: PPC: Book3S: MMIO emulation support for little endian guests [ Paul E. McKenney ] * SAUCE: powerpc: Make 64-bit non-VMX copy_tofrom_user() bi-endian linux (3.13.0-0.10) trusty; urgency=low [ Andy Whitcroft ] * rebase to v3.13-rc5 * [Config] updateconfigs following rebase to v3.13-rc5 [ Upstream Kernel Changes ] * rebase to v3.13-rc5 - LP: #1260303 - LP: #1260303 - LP: #1260225 linux (3.13.0-0.9) trusty; urgency=low [ Andy Whitcroft ] * [Config] d-i -- allow missing firmware linux (3.13.0-0.8) trusty; urgency=low [ Andy Whitcroft ] * [Config] annotations -- first pass over entire config * [Config] drop libunwind8-dev from Build-Depends for ppc64el [ Tim Gardner ] * [Config] Add arm64 device tree files - LP: #1262901 linux (3.13.0-0.7) trusty; urgency=low [ Rajesh B Prathipati ] * SAUCE: powerpc: Make unaligned accesses endian-safe for powerpc [ Tim Gardner ] * [Config] CONFIG_REGULATOR_S2MPS11=n for FTBS [ Upstream Kernel Changes ] * rebase to v3.13-rc4 - LP: #1259790 - LP: #1259437 - LP: #1259435 linux (3.13.0-0.6) trusty; urgency=low [ Paolo Pisati ] * [Config] armhf: arm64: VIRTIO_[BLK|MMIO|NET|CONSOLE|BALLOON]=y * [Config] i386: amd64: VIRTIO_CONSOLE=y [ Tim Gardner ] * [Config] CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y linux (3.13.0-0.5) trusty; urgency=low [ Andy Whitcroft ] * correct bug listing for v3.13-rc2 rebase * [Config] ppc64el -- create linux-libc-dev * [Debian] Improve tools version message - LP: #1257715 [ Serge Hallyn ] * SAUCE: fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)] - LP: #1248590 * SAUCE: vfs: Fix a regression in mounting proc [ Tim Gardner ] * [Config] Build-in ohci-pci - LP: #1244176 * Rebase to v3.13-rc3 [ Upstream Kernel Changes ] * Revert Revert fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks - LP: #1248590 [ Upstream Kernel Changes ] * rebase to v3.13-rc3 - LP: #1256840 - LP: #1256212 linux (3.13.0-0.4) trusty; urgency=low [ Tim Gardner ] * Rebase to v3.13-rc2 [ Upstream Kernel Changes ] * rebase to v3.13-rc2 linux (3.13.0-0.3) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: Fix DocBook FTBS [ Tim Gardner ] * [Debian] Re-sign modules after debug objcopy - LP: #1253155 * [Config] CONFIG_EXT4_USE_FOR_EXT23=y [ Upstream Kernel Changes ] * doc: fix generation of device-drivers * rebase to b975dc3689fc6a3718ad288ce080924f9cb7e176 linux (3.13.0-0.2) trusty; urgency=low [ Tim Gardner ] * SAUCE: Fix DocBook FTBS linux (3.13.0-0.1) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to 7e3528c3660a2e8602abc7858b0994d611f74bc3 linux (3.13.0-0.0) trusty; urgency=low * Major release bump. -- Tim Gardner tim.gard...@canonical.com Tue, 07 Jan 2014 09:21:26 -0700 ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You
[Kernel-packages] [Bug 1257715] Re: linux-tools-common depends on old kernel versions for LTS point releases
This bug was fixed in the package linux - 3.13.0-1.16 --- linux (3.13.0-1.16) trusty; urgency=low * First 3.13 upload. * Release tracker - LP: #1266852 linux (3.13.0-0.15) trusty; urgency=low [ Tim Gardner ] * rebase to v3.13-rc7 [ Upstream Kernel Changes ] * rebase to v3.13-rc7 linux (3.13.0-0.14) trusty; urgency=low [ Andy Whitcroft ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 [ Tim Gardner ] * Remove ubuntu/dm-raid4-5 in favor of CONFIG_MD_RAID456 * Update lttng to Version 2.4.0-rc2 * lttng: Disabled trace_kvm_async_pf_completed * [Config] CONFIG_IMA=y - LP: #1244627 [ Upstream Kernel Changes ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 linux (3.13.0-0.13) trusty; urgency=low [ Andy Whitcroft ] * ubuntu: aufs3 -- (no-up) aufs3-base.patch * ubuntu: aufs3 -- (no-up) aufs3-mmap.patch * ubuntu: aufs3 -- (no-up) aufs3-standalone.patch * ubuntu: AUFS (no-squash): basic framework and update machinary * ubuntu: AUFS -- update to 7b136a27b021da9010d8b6c101939dd298e46be7 * ubuntu: aufs3 -- enable * ubuntu: aufs3 -- update configs linux (3.13.0-0.12) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to v3.13-rc6 linux (3.13.0-0.11) trusty; urgency=low [ Andy Whitcroft ] * SAUCE: suspicious unlocked -status reading and writing in ipc/sem.c * [Config] ppc64el -- initial defconfig based -generic flavour * [Config] initial defconfig for ppc64el * [Config] ubuntuise ppc64el config * [Config] ubuntuise ppc64el config part 2 * [Config] d-i -- update empty udebs list * [Config] ppc64el -- split extras package [ Anton Blanchard ] * SAUCE: KVM: PPC: Book3S HV: Add little-endian guest support [ Benjamin Herrenschmidt ] * SAUCE: powerpc/powernv: Add calls to support little endian [ Cédric Le Goater ] * SAUCE: KVM: PPC: Book3S: add helper routine to load guest instructions * SAUCE: KVM: PPC: Book3S: add helper routines to detect endian order * SAUCE: KVM: PPC: Book3S: MMIO emulation support for little endian guests [ Paul E. McKenney ] * SAUCE: powerpc: Make 64-bit non-VMX copy_tofrom_user() bi-endian linux (3.13.0-0.10) trusty; urgency=low [ Andy Whitcroft ] * rebase to v3.13-rc5 * [Config] updateconfigs following rebase to v3.13-rc5 [ Upstream Kernel Changes ] * rebase to v3.13-rc5 - LP: #1260303 - LP: #1260303 - LP: #1260225 linux (3.13.0-0.9) trusty; urgency=low [ Andy Whitcroft ] * [Config] d-i -- allow missing firmware linux (3.13.0-0.8) trusty; urgency=low [ Andy Whitcroft ] * [Config] annotations -- first pass over entire config * [Config] drop libunwind8-dev from Build-Depends for ppc64el [ Tim Gardner ] * [Config] Add arm64 device tree files - LP: #1262901 linux (3.13.0-0.7) trusty; urgency=low [ Rajesh B Prathipati ] * SAUCE: powerpc: Make unaligned accesses endian-safe for powerpc [ Tim Gardner ] * [Config] CONFIG_REGULATOR_S2MPS11=n for FTBS [ Upstream Kernel Changes ] * rebase to v3.13-rc4 - LP: #1259790 - LP: #1259437 - LP: #1259435 linux (3.13.0-0.6) trusty; urgency=low [ Paolo Pisati ] * [Config] armhf: arm64: VIRTIO_[BLK|MMIO|NET|CONSOLE|BALLOON]=y * [Config] i386: amd64: VIRTIO_CONSOLE=y [ Tim Gardner ] * [Config] CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y linux (3.13.0-0.5) trusty; urgency=low [ Andy Whitcroft ] * correct bug listing for v3.13-rc2 rebase * [Config] ppc64el -- create linux-libc-dev * [Debian] Improve tools version message - LP: #1257715 [ Serge Hallyn ] * SAUCE: fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)] - LP: #1248590 * SAUCE: vfs: Fix a regression in mounting proc [ Tim Gardner ] * [Config] Build-in ohci-pci - LP: #1244176 * Rebase to v3.13-rc3 [ Upstream Kernel Changes ] * Revert Revert fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks - LP: #1248590 [ Upstream Kernel Changes ] * rebase to v3.13-rc3 - LP: #1256840 - LP: #1256212 linux (3.13.0-0.4) trusty; urgency=low [ Tim Gardner ] * Rebase to v3.13-rc2 [ Upstream Kernel Changes ] * rebase to v3.13-rc2 linux (3.13.0-0.3) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: Fix DocBook FTBS [ Tim Gardner ] * [Debian] Re-sign modules after debug objcopy - LP: #1253155 * [Config] CONFIG_EXT4_USE_FOR_EXT23=y [ Upstream Kernel Changes ] * doc: fix generation of device-drivers * rebase to b975dc3689fc6a3718ad288ce080924f9cb7e176 linux (3.13.0-0.2) trusty; urgency=low [ Tim Gardner ] * SAUCE: Fix DocBook FTBS linux (3.13.0-0.1) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to 7e3528c3660a2e8602abc7858b0994d611f74bc3 linux (3.13.0-0.0) trusty; urgency=low * Major release bump. -- Tim Gardner tim.gard...@canonical.com Tue, 07 Jan 2014 09:21:26 -0700 ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed = Fix Released
[Kernel-packages] [Bug 1256840] Re: Switch device from Internal-Mic (with Mute Status) to Headset-Mic for record, recording is silent.
This bug was fixed in the package linux - 3.13.0-1.16 --- linux (3.13.0-1.16) trusty; urgency=low * First 3.13 upload. * Release tracker - LP: #1266852 linux (3.13.0-0.15) trusty; urgency=low [ Tim Gardner ] * rebase to v3.13-rc7 [ Upstream Kernel Changes ] * rebase to v3.13-rc7 linux (3.13.0-0.14) trusty; urgency=low [ Andy Whitcroft ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 [ Tim Gardner ] * Remove ubuntu/dm-raid4-5 in favor of CONFIG_MD_RAID456 * Update lttng to Version 2.4.0-rc2 * lttng: Disabled trace_kvm_async_pf_completed * [Config] CONFIG_IMA=y - LP: #1244627 [ Upstream Kernel Changes ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 linux (3.13.0-0.13) trusty; urgency=low [ Andy Whitcroft ] * ubuntu: aufs3 -- (no-up) aufs3-base.patch * ubuntu: aufs3 -- (no-up) aufs3-mmap.patch * ubuntu: aufs3 -- (no-up) aufs3-standalone.patch * ubuntu: AUFS (no-squash): basic framework and update machinary * ubuntu: AUFS -- update to 7b136a27b021da9010d8b6c101939dd298e46be7 * ubuntu: aufs3 -- enable * ubuntu: aufs3 -- update configs linux (3.13.0-0.12) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to v3.13-rc6 linux (3.13.0-0.11) trusty; urgency=low [ Andy Whitcroft ] * SAUCE: suspicious unlocked -status reading and writing in ipc/sem.c * [Config] ppc64el -- initial defconfig based -generic flavour * [Config] initial defconfig for ppc64el * [Config] ubuntuise ppc64el config * [Config] ubuntuise ppc64el config part 2 * [Config] d-i -- update empty udebs list * [Config] ppc64el -- split extras package [ Anton Blanchard ] * SAUCE: KVM: PPC: Book3S HV: Add little-endian guest support [ Benjamin Herrenschmidt ] * SAUCE: powerpc/powernv: Add calls to support little endian [ Cédric Le Goater ] * SAUCE: KVM: PPC: Book3S: add helper routine to load guest instructions * SAUCE: KVM: PPC: Book3S: add helper routines to detect endian order * SAUCE: KVM: PPC: Book3S: MMIO emulation support for little endian guests [ Paul E. McKenney ] * SAUCE: powerpc: Make 64-bit non-VMX copy_tofrom_user() bi-endian linux (3.13.0-0.10) trusty; urgency=low [ Andy Whitcroft ] * rebase to v3.13-rc5 * [Config] updateconfigs following rebase to v3.13-rc5 [ Upstream Kernel Changes ] * rebase to v3.13-rc5 - LP: #1260303 - LP: #1260303 - LP: #1260225 linux (3.13.0-0.9) trusty; urgency=low [ Andy Whitcroft ] * [Config] d-i -- allow missing firmware linux (3.13.0-0.8) trusty; urgency=low [ Andy Whitcroft ] * [Config] annotations -- first pass over entire config * [Config] drop libunwind8-dev from Build-Depends for ppc64el [ Tim Gardner ] * [Config] Add arm64 device tree files - LP: #1262901 linux (3.13.0-0.7) trusty; urgency=low [ Rajesh B Prathipati ] * SAUCE: powerpc: Make unaligned accesses endian-safe for powerpc [ Tim Gardner ] * [Config] CONFIG_REGULATOR_S2MPS11=n for FTBS [ Upstream Kernel Changes ] * rebase to v3.13-rc4 - LP: #1259790 - LP: #1259437 - LP: #1259435 linux (3.13.0-0.6) trusty; urgency=low [ Paolo Pisati ] * [Config] armhf: arm64: VIRTIO_[BLK|MMIO|NET|CONSOLE|BALLOON]=y * [Config] i386: amd64: VIRTIO_CONSOLE=y [ Tim Gardner ] * [Config] CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y linux (3.13.0-0.5) trusty; urgency=low [ Andy Whitcroft ] * correct bug listing for v3.13-rc2 rebase * [Config] ppc64el -- create linux-libc-dev * [Debian] Improve tools version message - LP: #1257715 [ Serge Hallyn ] * SAUCE: fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)] - LP: #1248590 * SAUCE: vfs: Fix a regression in mounting proc [ Tim Gardner ] * [Config] Build-in ohci-pci - LP: #1244176 * Rebase to v3.13-rc3 [ Upstream Kernel Changes ] * Revert Revert fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks - LP: #1248590 [ Upstream Kernel Changes ] * rebase to v3.13-rc3 - LP: #1256840 - LP: #1256212 linux (3.13.0-0.4) trusty; urgency=low [ Tim Gardner ] * Rebase to v3.13-rc2 [ Upstream Kernel Changes ] * rebase to v3.13-rc2 linux (3.13.0-0.3) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: Fix DocBook FTBS [ Tim Gardner ] * [Debian] Re-sign modules after debug objcopy - LP: #1253155 * [Config] CONFIG_EXT4_USE_FOR_EXT23=y [ Upstream Kernel Changes ] * doc: fix generation of device-drivers * rebase to b975dc3689fc6a3718ad288ce080924f9cb7e176 linux (3.13.0-0.2) trusty; urgency=low [ Tim Gardner ] * SAUCE: Fix DocBook FTBS linux (3.13.0-0.1) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to 7e3528c3660a2e8602abc7858b0994d611f74bc3 linux (3.13.0-0.0) trusty; urgency=low * Major release bump. -- Tim Gardner tim.gard...@canonical.com Tue, 07 Jan 2014 09:21:26 -0700 ** Changed in: linux (Ubuntu) Status: Fix Committed = Fix Released -- You
[Kernel-packages] [Bug 1260225] Re: Crackling audio on HP / AMD Hudson machines when changing volume during playback
This bug was fixed in the package linux - 3.13.0-1.16 --- linux (3.13.0-1.16) trusty; urgency=low * First 3.13 upload. * Release tracker - LP: #1266852 linux (3.13.0-0.15) trusty; urgency=low [ Tim Gardner ] * rebase to v3.13-rc7 [ Upstream Kernel Changes ] * rebase to v3.13-rc7 linux (3.13.0-0.14) trusty; urgency=low [ Andy Whitcroft ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 [ Tim Gardner ] * Remove ubuntu/dm-raid4-5 in favor of CONFIG_MD_RAID456 * Update lttng to Version 2.4.0-rc2 * lttng: Disabled trace_kvm_async_pf_completed * [Config] CONFIG_IMA=y - LP: #1244627 [ Upstream Kernel Changes ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 linux (3.13.0-0.13) trusty; urgency=low [ Andy Whitcroft ] * ubuntu: aufs3 -- (no-up) aufs3-base.patch * ubuntu: aufs3 -- (no-up) aufs3-mmap.patch * ubuntu: aufs3 -- (no-up) aufs3-standalone.patch * ubuntu: AUFS (no-squash): basic framework and update machinary * ubuntu: AUFS -- update to 7b136a27b021da9010d8b6c101939dd298e46be7 * ubuntu: aufs3 -- enable * ubuntu: aufs3 -- update configs linux (3.13.0-0.12) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to v3.13-rc6 linux (3.13.0-0.11) trusty; urgency=low [ Andy Whitcroft ] * SAUCE: suspicious unlocked -status reading and writing in ipc/sem.c * [Config] ppc64el -- initial defconfig based -generic flavour * [Config] initial defconfig for ppc64el * [Config] ubuntuise ppc64el config * [Config] ubuntuise ppc64el config part 2 * [Config] d-i -- update empty udebs list * [Config] ppc64el -- split extras package [ Anton Blanchard ] * SAUCE: KVM: PPC: Book3S HV: Add little-endian guest support [ Benjamin Herrenschmidt ] * SAUCE: powerpc/powernv: Add calls to support little endian [ Cédric Le Goater ] * SAUCE: KVM: PPC: Book3S: add helper routine to load guest instructions * SAUCE: KVM: PPC: Book3S: add helper routines to detect endian order * SAUCE: KVM: PPC: Book3S: MMIO emulation support for little endian guests [ Paul E. McKenney ] * SAUCE: powerpc: Make 64-bit non-VMX copy_tofrom_user() bi-endian linux (3.13.0-0.10) trusty; urgency=low [ Andy Whitcroft ] * rebase to v3.13-rc5 * [Config] updateconfigs following rebase to v3.13-rc5 [ Upstream Kernel Changes ] * rebase to v3.13-rc5 - LP: #1260303 - LP: #1260303 - LP: #1260225 linux (3.13.0-0.9) trusty; urgency=low [ Andy Whitcroft ] * [Config] d-i -- allow missing firmware linux (3.13.0-0.8) trusty; urgency=low [ Andy Whitcroft ] * [Config] annotations -- first pass over entire config * [Config] drop libunwind8-dev from Build-Depends for ppc64el [ Tim Gardner ] * [Config] Add arm64 device tree files - LP: #1262901 linux (3.13.0-0.7) trusty; urgency=low [ Rajesh B Prathipati ] * SAUCE: powerpc: Make unaligned accesses endian-safe for powerpc [ Tim Gardner ] * [Config] CONFIG_REGULATOR_S2MPS11=n for FTBS [ Upstream Kernel Changes ] * rebase to v3.13-rc4 - LP: #1259790 - LP: #1259437 - LP: #1259435 linux (3.13.0-0.6) trusty; urgency=low [ Paolo Pisati ] * [Config] armhf: arm64: VIRTIO_[BLK|MMIO|NET|CONSOLE|BALLOON]=y * [Config] i386: amd64: VIRTIO_CONSOLE=y [ Tim Gardner ] * [Config] CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y linux (3.13.0-0.5) trusty; urgency=low [ Andy Whitcroft ] * correct bug listing for v3.13-rc2 rebase * [Config] ppc64el -- create linux-libc-dev * [Debian] Improve tools version message - LP: #1257715 [ Serge Hallyn ] * SAUCE: fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)] - LP: #1248590 * SAUCE: vfs: Fix a regression in mounting proc [ Tim Gardner ] * [Config] Build-in ohci-pci - LP: #1244176 * Rebase to v3.13-rc3 [ Upstream Kernel Changes ] * Revert Revert fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks - LP: #1248590 [ Upstream Kernel Changes ] * rebase to v3.13-rc3 - LP: #1256840 - LP: #1256212 linux (3.13.0-0.4) trusty; urgency=low [ Tim Gardner ] * Rebase to v3.13-rc2 [ Upstream Kernel Changes ] * rebase to v3.13-rc2 linux (3.13.0-0.3) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: Fix DocBook FTBS [ Tim Gardner ] * [Debian] Re-sign modules after debug objcopy - LP: #1253155 * [Config] CONFIG_EXT4_USE_FOR_EXT23=y [ Upstream Kernel Changes ] * doc: fix generation of device-drivers * rebase to b975dc3689fc6a3718ad288ce080924f9cb7e176 linux (3.13.0-0.2) trusty; urgency=low [ Tim Gardner ] * SAUCE: Fix DocBook FTBS linux (3.13.0-0.1) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to 7e3528c3660a2e8602abc7858b0994d611f74bc3 linux (3.13.0-0.0) trusty; urgency=low * Major release bump. -- Tim Gardner tim.gard...@canonical.com Tue, 07 Jan 2014 09:21:26 -0700 ** Changed in: linux (Ubuntu) Status: Fix Committed = Fix Released -- You
[Kernel-packages] [Bug 1262901] Re: please include device-tree binaries for arm64
This bug was fixed in the package linux - 3.13.0-1.16 --- linux (3.13.0-1.16) trusty; urgency=low * First 3.13 upload. * Release tracker - LP: #1266852 linux (3.13.0-0.15) trusty; urgency=low [ Tim Gardner ] * rebase to v3.13-rc7 [ Upstream Kernel Changes ] * rebase to v3.13-rc7 linux (3.13.0-0.14) trusty; urgency=low [ Andy Whitcroft ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 [ Tim Gardner ] * Remove ubuntu/dm-raid4-5 in favor of CONFIG_MD_RAID456 * Update lttng to Version 2.4.0-rc2 * lttng: Disabled trace_kvm_async_pf_completed * [Config] CONFIG_IMA=y - LP: #1244627 [ Upstream Kernel Changes ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 linux (3.13.0-0.13) trusty; urgency=low [ Andy Whitcroft ] * ubuntu: aufs3 -- (no-up) aufs3-base.patch * ubuntu: aufs3 -- (no-up) aufs3-mmap.patch * ubuntu: aufs3 -- (no-up) aufs3-standalone.patch * ubuntu: AUFS (no-squash): basic framework and update machinary * ubuntu: AUFS -- update to 7b136a27b021da9010d8b6c101939dd298e46be7 * ubuntu: aufs3 -- enable * ubuntu: aufs3 -- update configs linux (3.13.0-0.12) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to v3.13-rc6 linux (3.13.0-0.11) trusty; urgency=low [ Andy Whitcroft ] * SAUCE: suspicious unlocked -status reading and writing in ipc/sem.c * [Config] ppc64el -- initial defconfig based -generic flavour * [Config] initial defconfig for ppc64el * [Config] ubuntuise ppc64el config * [Config] ubuntuise ppc64el config part 2 * [Config] d-i -- update empty udebs list * [Config] ppc64el -- split extras package [ Anton Blanchard ] * SAUCE: KVM: PPC: Book3S HV: Add little-endian guest support [ Benjamin Herrenschmidt ] * SAUCE: powerpc/powernv: Add calls to support little endian [ Cédric Le Goater ] * SAUCE: KVM: PPC: Book3S: add helper routine to load guest instructions * SAUCE: KVM: PPC: Book3S: add helper routines to detect endian order * SAUCE: KVM: PPC: Book3S: MMIO emulation support for little endian guests [ Paul E. McKenney ] * SAUCE: powerpc: Make 64-bit non-VMX copy_tofrom_user() bi-endian linux (3.13.0-0.10) trusty; urgency=low [ Andy Whitcroft ] * rebase to v3.13-rc5 * [Config] updateconfigs following rebase to v3.13-rc5 [ Upstream Kernel Changes ] * rebase to v3.13-rc5 - LP: #1260303 - LP: #1260303 - LP: #1260225 linux (3.13.0-0.9) trusty; urgency=low [ Andy Whitcroft ] * [Config] d-i -- allow missing firmware linux (3.13.0-0.8) trusty; urgency=low [ Andy Whitcroft ] * [Config] annotations -- first pass over entire config * [Config] drop libunwind8-dev from Build-Depends for ppc64el [ Tim Gardner ] * [Config] Add arm64 device tree files - LP: #1262901 linux (3.13.0-0.7) trusty; urgency=low [ Rajesh B Prathipati ] * SAUCE: powerpc: Make unaligned accesses endian-safe for powerpc [ Tim Gardner ] * [Config] CONFIG_REGULATOR_S2MPS11=n for FTBS [ Upstream Kernel Changes ] * rebase to v3.13-rc4 - LP: #1259790 - LP: #1259437 - LP: #1259435 linux (3.13.0-0.6) trusty; urgency=low [ Paolo Pisati ] * [Config] armhf: arm64: VIRTIO_[BLK|MMIO|NET|CONSOLE|BALLOON]=y * [Config] i386: amd64: VIRTIO_CONSOLE=y [ Tim Gardner ] * [Config] CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y linux (3.13.0-0.5) trusty; urgency=low [ Andy Whitcroft ] * correct bug listing for v3.13-rc2 rebase * [Config] ppc64el -- create linux-libc-dev * [Debian] Improve tools version message - LP: #1257715 [ Serge Hallyn ] * SAUCE: fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)] - LP: #1248590 * SAUCE: vfs: Fix a regression in mounting proc [ Tim Gardner ] * [Config] Build-in ohci-pci - LP: #1244176 * Rebase to v3.13-rc3 [ Upstream Kernel Changes ] * Revert Revert fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks - LP: #1248590 [ Upstream Kernel Changes ] * rebase to v3.13-rc3 - LP: #1256840 - LP: #1256212 linux (3.13.0-0.4) trusty; urgency=low [ Tim Gardner ] * Rebase to v3.13-rc2 [ Upstream Kernel Changes ] * rebase to v3.13-rc2 linux (3.13.0-0.3) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: Fix DocBook FTBS [ Tim Gardner ] * [Debian] Re-sign modules after debug objcopy - LP: #1253155 * [Config] CONFIG_EXT4_USE_FOR_EXT23=y [ Upstream Kernel Changes ] * doc: fix generation of device-drivers * rebase to b975dc3689fc6a3718ad288ce080924f9cb7e176 linux (3.13.0-0.2) trusty; urgency=low [ Tim Gardner ] * SAUCE: Fix DocBook FTBS linux (3.13.0-0.1) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to 7e3528c3660a2e8602abc7858b0994d611f74bc3 linux (3.13.0-0.0) trusty; urgency=low * Major release bump. -- Tim Gardner tim.gard...@canonical.com Tue, 07 Jan 2014 09:21:26 -0700 ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed = Fix Released
[Kernel-packages] [Bug 1256212] Re: Dell inspiron 5439 has mono speakers
This bug was fixed in the package linux - 3.13.0-1.16 --- linux (3.13.0-1.16) trusty; urgency=low * First 3.13 upload. * Release tracker - LP: #1266852 linux (3.13.0-0.15) trusty; urgency=low [ Tim Gardner ] * rebase to v3.13-rc7 [ Upstream Kernel Changes ] * rebase to v3.13-rc7 linux (3.13.0-0.14) trusty; urgency=low [ Andy Whitcroft ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 [ Tim Gardner ] * Remove ubuntu/dm-raid4-5 in favor of CONFIG_MD_RAID456 * Update lttng to Version 2.4.0-rc2 * lttng: Disabled trace_kvm_async_pf_completed * [Config] CONFIG_IMA=y - LP: #1244627 [ Upstream Kernel Changes ] * rebase to 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6 linux (3.13.0-0.13) trusty; urgency=low [ Andy Whitcroft ] * ubuntu: aufs3 -- (no-up) aufs3-base.patch * ubuntu: aufs3 -- (no-up) aufs3-mmap.patch * ubuntu: aufs3 -- (no-up) aufs3-standalone.patch * ubuntu: AUFS (no-squash): basic framework and update machinary * ubuntu: AUFS -- update to 7b136a27b021da9010d8b6c101939dd298e46be7 * ubuntu: aufs3 -- enable * ubuntu: aufs3 -- update configs linux (3.13.0-0.12) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to v3.13-rc6 linux (3.13.0-0.11) trusty; urgency=low [ Andy Whitcroft ] * SAUCE: suspicious unlocked -status reading and writing in ipc/sem.c * [Config] ppc64el -- initial defconfig based -generic flavour * [Config] initial defconfig for ppc64el * [Config] ubuntuise ppc64el config * [Config] ubuntuise ppc64el config part 2 * [Config] d-i -- update empty udebs list * [Config] ppc64el -- split extras package [ Anton Blanchard ] * SAUCE: KVM: PPC: Book3S HV: Add little-endian guest support [ Benjamin Herrenschmidt ] * SAUCE: powerpc/powernv: Add calls to support little endian [ Cédric Le Goater ] * SAUCE: KVM: PPC: Book3S: add helper routine to load guest instructions * SAUCE: KVM: PPC: Book3S: add helper routines to detect endian order * SAUCE: KVM: PPC: Book3S: MMIO emulation support for little endian guests [ Paul E. McKenney ] * SAUCE: powerpc: Make 64-bit non-VMX copy_tofrom_user() bi-endian linux (3.13.0-0.10) trusty; urgency=low [ Andy Whitcroft ] * rebase to v3.13-rc5 * [Config] updateconfigs following rebase to v3.13-rc5 [ Upstream Kernel Changes ] * rebase to v3.13-rc5 - LP: #1260303 - LP: #1260303 - LP: #1260225 linux (3.13.0-0.9) trusty; urgency=low [ Andy Whitcroft ] * [Config] d-i -- allow missing firmware linux (3.13.0-0.8) trusty; urgency=low [ Andy Whitcroft ] * [Config] annotations -- first pass over entire config * [Config] drop libunwind8-dev from Build-Depends for ppc64el [ Tim Gardner ] * [Config] Add arm64 device tree files - LP: #1262901 linux (3.13.0-0.7) trusty; urgency=low [ Rajesh B Prathipati ] * SAUCE: powerpc: Make unaligned accesses endian-safe for powerpc [ Tim Gardner ] * [Config] CONFIG_REGULATOR_S2MPS11=n for FTBS [ Upstream Kernel Changes ] * rebase to v3.13-rc4 - LP: #1259790 - LP: #1259437 - LP: #1259435 linux (3.13.0-0.6) trusty; urgency=low [ Paolo Pisati ] * [Config] armhf: arm64: VIRTIO_[BLK|MMIO|NET|CONSOLE|BALLOON]=y * [Config] i386: amd64: VIRTIO_CONSOLE=y [ Tim Gardner ] * [Config] CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y linux (3.13.0-0.5) trusty; urgency=low [ Andy Whitcroft ] * correct bug listing for v3.13-rc2 rebase * [Config] ppc64el -- create linux-libc-dev * [Debian] Improve tools version message - LP: #1257715 [ Serge Hallyn ] * SAUCE: fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)] - LP: #1248590 * SAUCE: vfs: Fix a regression in mounting proc [ Tim Gardner ] * [Config] Build-in ohci-pci - LP: #1244176 * Rebase to v3.13-rc3 [ Upstream Kernel Changes ] * Revert Revert fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks - LP: #1248590 [ Upstream Kernel Changes ] * rebase to v3.13-rc3 - LP: #1256840 - LP: #1256212 linux (3.13.0-0.4) trusty; urgency=low [ Tim Gardner ] * Rebase to v3.13-rc2 [ Upstream Kernel Changes ] * rebase to v3.13-rc2 linux (3.13.0-0.3) trusty; urgency=low [ Andy Whitcroft ] * Revert SAUCE: Fix DocBook FTBS [ Tim Gardner ] * [Debian] Re-sign modules after debug objcopy - LP: #1253155 * [Config] CONFIG_EXT4_USE_FOR_EXT23=y [ Upstream Kernel Changes ] * doc: fix generation of device-drivers * rebase to b975dc3689fc6a3718ad288ce080924f9cb7e176 linux (3.13.0-0.2) trusty; urgency=low [ Tim Gardner ] * SAUCE: Fix DocBook FTBS linux (3.13.0-0.1) trusty; urgency=low [ Upstream Kernel Changes ] * rebase to 7e3528c3660a2e8602abc7858b0994d611f74bc3 linux (3.13.0-0.0) trusty; urgency=low * Major release bump. -- Tim Gardner tim.gard...@canonical.com Tue, 07 Jan 2014 09:21:26 -0700 ** Changed in: linux (Ubuntu) Status: Fix Committed = Fix Released -- You
[Kernel-packages] [Bug 1250027] Re: 10de:1056 [Lenovo ThinkPad T420s] Fails to boot using nvidia drivers
With Ubuntu 13.10 (3.11.0-15-generic) on a Lenovo T420 I encountered the same problem. Booting behaviour was erratic, it succeeded roughly every second or third time. The suggested workaround (kernel parameter pci=noacpi) works for the moment. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250027 Title: 10de:1056 [Lenovo ThinkPad T420s] Fails to boot using nvidia drivers Status in “linux” package in Ubuntu: Incomplete Bug description: Booting a ThinkPad T420s with discrete graphics enabled in the causes a hang during the boot. The hang happens somewhere during udev startup, I think. WORKAROUND: User kernel parameter: pci=noacpi ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: olli 1732 F pulseaudio /dev/snd/controlC0: olli 1732 F pulseaudio /dev/snd/pcmC0D0p: olli 1732 F...m pulseaudio Date: Mon Nov 11 12:08:47 2013 HibernationDevice: RESUME=UUID=99eff1be-4759-4df7-99d6-a91a4cf999ce InstallationDate: Installed on 2013-10-19 (22 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4174PEG MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=e773c67a-283e-4a5d-b1ab-6000e6926d63 ro quiet splash pci=noacpi RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET57WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4174PEG 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:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174PEG:pvrThinkPadT420s:rvnLENOVO:rn4174PEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4174PEG dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1212856] Re: Kernel Panic - Not syncing : Fatal Exception in Interrupt in 12.04.2 LTS (64-bit)
I am also having ubuntu 12.04.2 on dell inspiron 1545 laptop. While
trying to upgrade the OS I am getting this error message again and
again. By updating Ubuntu will the kernel also get upgraded. Can this
solve 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/1212856
Title:
Kernel Panic - Not syncing : Fatal Exception in Interrupt in 12.04.2
LTS (64-bit)
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Several times, when I boot my Ubuntu 12.04.2 LTS (Precise Pangolin)
64-bit installation, I get a kernel panic during the boot. When that
happens, I have to power the machine down and power it up again.
Sometimes, the kernel panic happens several times in a row, until the
machine finally boots.
The hardware is a HP Pavilion dv6 laptop, running in Dual-Boot with
Windows 7 Home Premium (also 64-bit).
I have all Updates installed to this date (15-aug-2013), including the
kernel updates: the running kernel is 3.5.0-37
Here's the output from uname -a :
$ Linux [hostname] 3.5.0-37-generic #58~precise1-Ubuntu SMP Wed Jul 10
17:48:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
The last message of the kernel panic is almost always the following:
Kernel Panic - Not syncing : Fatal Exception in Interrupt
Sometimes, there's a message below that stating:
Shutting down cpus with NMI
The messages above the Kernel Panic message are usually different
each time. I have photographed several of the Kernel Panic screens
and I can attach some of them to this Bug Report, if that's useful.
In case it's relevant, my partition setup for this Ubuntu installation
is the following:
1 - a /boot partition (formatted as ext3)
2 - a swap partition
3 - a / partition (formatted as ext4), with encrypted home folder.
Please tell me if I should add any information to this bug report.
Thanks in advance.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-37-generic 3.5.0-37.58~precise1
ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic x86_64
NonfreeKernelModules: nvidia wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ricardo2032 F pulseaudio
/dev/snd/controlC0: ricardo2032 F pulseaudio
CRDA:
country PT:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb10 irq 43'
Mixer name : 'IDT 92HD75B3X5'
Components : 'HDA:111d7603,103c3659,00100202'
Controls : 21
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 44'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Date: Thu Aug 15 22:16:36 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3ddeb984-b63d-45cf-825f-04e59e87166d
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
MarkForUpload: True
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-37-generic
root=UUID=bd2ded4b-faa2-439f-b387-16292df03932 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-37-generic N/A
linux-backports-modules-3.5.0-37-generic N/A
linux-firmware1.79.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3659
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 32.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.15:bd01/05/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 049D212412102
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212856/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1250027] Re: 10de:1056 [Lenovo ThinkPad T420s] Fails to boot using nvidia drivers
Stefan Born, 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 a Ubuntu repository 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/1250027 Title: 10de:1056 [Lenovo ThinkPad T420s] Fails to boot using nvidia drivers Status in “linux” package in Ubuntu: Incomplete Bug description: Booting a ThinkPad T420s with discrete graphics enabled in the causes a hang during the boot. The hang happens somewhere during udev startup, I think. WORKAROUND: User kernel parameter: pci=noacpi ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: olli 1732 F pulseaudio /dev/snd/controlC0: olli 1732 F pulseaudio /dev/snd/pcmC0D0p: olli 1732 F...m pulseaudio Date: Mon Nov 11 12:08:47 2013 HibernationDevice: RESUME=UUID=99eff1be-4759-4df7-99d6-a91a4cf999ce InstallationDate: Installed on 2013-10-19 (22 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4174PEG MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=e773c67a-283e-4a5d-b1ab-6000e6926d63 ro quiet splash pci=noacpi RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET57WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4174PEG 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:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174PEG:pvrThinkPadT420s:rvnLENOVO:rn4174PEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4174PEG dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1212856] Re: Kernel Panic - Not syncing : Fatal Exception in Interrupt in 12.04.2 LTS (64-bit)
nakul, 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 a Ubuntu repository 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/1212856
Title:
Kernel Panic - Not syncing : Fatal Exception in Interrupt in 12.04.2
LTS (64-bit)
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Several times, when I boot my Ubuntu 12.04.2 LTS (Precise Pangolin)
64-bit installation, I get a kernel panic during the boot. When that
happens, I have to power the machine down and power it up again.
Sometimes, the kernel panic happens several times in a row, until the
machine finally boots.
The hardware is a HP Pavilion dv6 laptop, running in Dual-Boot with
Windows 7 Home Premium (also 64-bit).
I have all Updates installed to this date (15-aug-2013), including the
kernel updates: the running kernel is 3.5.0-37
Here's the output from uname -a :
$ Linux [hostname] 3.5.0-37-generic #58~precise1-Ubuntu SMP Wed Jul 10
17:48:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
The last message of the kernel panic is almost always the following:
Kernel Panic - Not syncing : Fatal Exception in Interrupt
Sometimes, there's a message below that stating:
Shutting down cpus with NMI
The messages above the Kernel Panic message are usually different
each time. I have photographed several of the Kernel Panic screens
and I can attach some of them to this Bug Report, if that's useful.
In case it's relevant, my partition setup for this Ubuntu installation
is the following:
1 - a /boot partition (formatted as ext3)
2 - a swap partition
3 - a / partition (formatted as ext4), with encrypted home folder.
Please tell me if I should add any information to this bug report.
Thanks in advance.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-37-generic 3.5.0-37.58~precise1
ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic x86_64
NonfreeKernelModules: nvidia wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ricardo2032 F pulseaudio
/dev/snd/controlC0: ricardo2032 F pulseaudio
CRDA:
country PT:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb10 irq 43'
Mixer name : 'IDT 92HD75B3X5'
Components : 'HDA:111d7603,103c3659,00100202'
Controls : 21
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 44'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Date: Thu Aug 15 22:16:36 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3ddeb984-b63d-45cf-825f-04e59e87166d
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
MarkForUpload: True
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-37-generic
root=UUID=bd2ded4b-faa2-439f-b387-16292df03932 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-37-generic N/A
linux-backports-modules-3.5.0-37-generic N/A
linux-firmware1.79.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3659
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 32.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias:
[Kernel-packages] [Bug 1250476] Re: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram
This is still affecting me. According to the source in 3.12, it still ships with 2.3.2-k of the intel driver, so I don't think the 3.12 kernel would solve the problem even if it were stable. http://lxr.free- electrons.com/source/drivers/net/ethernet/intel/e1000e/netdev.c?a=m68knommu#L56 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250476 Title: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. WORKAROUND: rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. The following is seen in dmsg: Nov 12 12:08:38 pk0k4dr kernel: [33964.643792] PM: Syncing filesystems ... done. Nov 12 12:08:38 pk0k4dr kernel: [33965.021021] PM: Preparing system for mem sleep Nov 12 12:08:42 pk0k4dr kernel: [33965.134863] Freezing user space processes ... (elapsed 0.001 seconds) done. Nov 12 12:08:42 pk0k4dr kernel: [33965.136441] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Nov 12 12:08:42 pk0k4dr kernel: [33965.137766] PM: Entering mem sleep Nov 12 12:08:42 pk0k4dr kernel: [33965.137838] Suspending console(s) (use no_console_suspend to debug) Nov 12 12:08:42 pk0k4dr kernel: [33965.137889] xhci_hcd :00:14.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33965.238268] xhci_hcd :00:14.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33965.238338] ehci-pci :00:1a.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33965.342280] ehci-pci :00:1a.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33965.342306] ehci-pci :00:1d.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33965.446254] ehci-pci :00:1d.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33965.578114] sd 0:0:0:0: [sda] Synchronizing SCSI cache Nov 12 12:08:42 pk0k4dr kernel: [33965.578476] sd 0:0:0:0: [sda] Stopping disk Nov 12 12:08:42 pk0k4dr kernel: [33965.802057] nouveau [ DRM] suspending fbcon... Nov 12 12:08:42 pk0k4dr kernel: [33965.802061] nouveau [ DRM] suspending display... Nov 12 12:08:42 pk0k4dr kernel: [33965.802087] nouveau [ DRM] unpinning framebuffer(s)... Nov 12 12:08:42 pk0k4dr kernel: [33965.802480] mei_me :00:16.0: suspend Nov 12 12:08:42 pk0k4dr kernel: [33965.803108] nouveau [ DRM] evicting buffers... Nov 12 12:08:42 pk0k4dr kernel: [33965.827282] nouveau [ DRM] waiting for kernel channels to go idle... Nov 12 12:08:42 pk0k4dr kernel: [33965.827309] nouveau [ DRM] suspending client object trees... Nov 12 12:08:42 pk0k4dr kernel: [33965.835924] nouveau [ DRM] suspending kernel object tree... Nov 12 12:08:42 pk0k4dr kernel: [33966.209804] i915 :00:02.0: power state changed by ACPI to D3cold Nov 12 12:08:42 pk0k4dr kernel: [33966.429324] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 Nov 12 12:08:42 pk0k4dr kernel: [33966.429328] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 Nov 12 12:08:42 pk0k4dr kernel: [33966.429330] PM: Device :00:19.0 failed to suspend async: error -2 Nov 12 12:08:42 pk0k4dr kernel: [33967.221549] nouveau :01:00.0: power state changed by ACPI to D3cold Nov 12 12:08:42 pk0k4dr kernel: [33967.221613] PM: Some devices failed to suspend, or early wake event detected Nov 12 12:08:42 pk0k4dr kernel: [33967.221661] i915 :00:02.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33967.221684] xhci_hcd :00:14.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33967.221737] mei_me :00:16.0: irq 45 for MSI/MSI-X ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jammy 3673 F pulseaudio Date: Tue Nov 12 13:42:10 2013 HibernationDevice: RESUME=UUID=36cdf9ac-9cc9-4649-9be0-ed0a81c29b26 InstallationDate: Installed on 2013-10-16 (26 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116
[Kernel-packages] [Bug 1251816] Re: Boot failure with saucy kernel 3.11 probing eisa
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201401071104_i386 has the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1251816 Title: Boot failure with saucy kernel 3.11 probing eisa Status in “linux” package in Ubuntu: Confirmed Bug description: I have an old laptop that I upgraded to saucy and it will only boot the earlier 3.8 kernel. The 3.11, 3 versions tried including the proposed, hangs on Platform eisa.0: Probing EISA bus 0 I also tried the 3.12.0-999 kernel at http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-07-saucy/ and it hangs as well. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-generic 3.11.0.14.15 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cp 1926 F pulseaudio CRDA: country CO: (2402 - 2472 @ 40), (3, 27) (5170 - 5250 @ 40), (3, 17) (5250 - 5330 @ 40), (3, 23), DFS (5735 - 5835 @ 40), (3, 30) CurrentDmesg: [ 114.938323] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 115.026165] XFS (sdb6): Mounting Filesystem [ 119.437397] XFS (sdb6): Ending clean mount [ 119.878267] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Date: Fri Nov 15 23:18:27 2013 HibernationDevice: RESUME=UUID=33c5f08a-8efc-4eb2-b6ec-497bb57df899 Lsusb: Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA PATA Combo Bridge Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: sag168168 Apollo Pro133AX MarkForUpload: True PccardctlIdent: Socket 0: no product info available Socket 1: no product info available ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=5658ed45-be8e-4c39-b0e3-1944d7a303b0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-32-generic N/A linux-backports-modules-3.8.0-32-generic N/A linux-firmware1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to saucy on 2013-11-01 (14 days ago) WpaSupplicantLog: dmi.bios.date: 10/18/2001 dmi.bios.vendor: Phoenix dmi.bios.version: 4.06CJ15 dmi.board.name: 694x686a dmi.board.vendor: VIA dmi.board.version: None 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:bd10/18/2001:svnsag168168:pnApolloPro133AX:pvr8500V:rvnVIA:rn694x686a:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Apollo Pro133AX dmi.product.version: 8500V dmi.sys.vendor: sag168168 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1251816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1252962] Re: Ralink RT3290 not working in Saucy
Kernel version 3.11.0-15.23 (currently in -updates) should have this bug fixed. Marking bug as 'fix released' ** Changed in: linux (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1252962 Title: Ralink RT3290 not working in Saucy Status in “linux” package in Ubuntu: Fix Released Bug description: RT3290 wifi will not connect in 13.10 with wpa on. By removing security a connection is achieved but it is poor signal and drops out after 5-10 minutes. Trying in 13.04 results in a connection which stays up even with wpa so this is a regression. Even in 13.04 performace is very poor (signal strength, speed) compared to W8. Kernal is using the rt2800pci module which appears poorly equiped to handle this chip. WORKAROUND: http://people.canonical.com/~henrix/lp1252962/v1/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brian 1897 F pulseaudio /dev/snd/controlC0: brian 1897 F pulseaudio CRDA: country AU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (3, 23) (5250 - 5330 @ 40), (3, 23), DFS (5735 - 5835 @ 40), (3, 30) Date: Wed Nov 20 13:10:11 2013 HibernationDevice: RESUME=UUID=65f788a6-7233-444f-b4c2-a6bb0332fd80 InstallationDate: Installed on 2013-10-30 (20 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=5d0db004-8555-4dc9-ab8b-abf05b6a3452 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 213A dmi.board.vendor: Hewlett-Packard dmi.board.version: 02.12 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.22:bd09/27/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr088410305A1620100:rvnHewlett-Packard:rn213A:rvr02.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 088410305A1620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250476] Re: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram
James Hewitt, thank you for your comment. Could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? ** Tags removed: latest-bios-2.55 ** Tags added: bios-outdated-2.56 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250476 Title: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Incomplete Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. WORKAROUND: rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. The following is seen in dmsg: Nov 12 12:08:38 pk0k4dr kernel: [33964.643792] PM: Syncing filesystems ... done. Nov 12 12:08:38 pk0k4dr kernel: [33965.021021] PM: Preparing system for mem sleep Nov 12 12:08:42 pk0k4dr kernel: [33965.134863] Freezing user space processes ... (elapsed 0.001 seconds) done. Nov 12 12:08:42 pk0k4dr kernel: [33965.136441] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Nov 12 12:08:42 pk0k4dr kernel: [33965.137766] PM: Entering mem sleep Nov 12 12:08:42 pk0k4dr kernel: [33965.137838] Suspending console(s) (use no_console_suspend to debug) Nov 12 12:08:42 pk0k4dr kernel: [33965.137889] xhci_hcd :00:14.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33965.238268] xhci_hcd :00:14.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33965.238338] ehci-pci :00:1a.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33965.342280] ehci-pci :00:1a.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33965.342306] ehci-pci :00:1d.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33965.446254] ehci-pci :00:1d.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33965.578114] sd 0:0:0:0: [sda] Synchronizing SCSI cache Nov 12 12:08:42 pk0k4dr kernel: [33965.578476] sd 0:0:0:0: [sda] Stopping disk Nov 12 12:08:42 pk0k4dr kernel: [33965.802057] nouveau [ DRM] suspending fbcon... Nov 12 12:08:42 pk0k4dr kernel: [33965.802061] nouveau [ DRM] suspending display... Nov 12 12:08:42 pk0k4dr kernel: [33965.802087] nouveau [ DRM] unpinning framebuffer(s)... Nov 12 12:08:42 pk0k4dr kernel: [33965.802480] mei_me :00:16.0: suspend Nov 12 12:08:42 pk0k4dr kernel: [33965.803108] nouveau [ DRM] evicting buffers... Nov 12 12:08:42 pk0k4dr kernel: [33965.827282] nouveau [ DRM] waiting for kernel channels to go idle... Nov 12 12:08:42 pk0k4dr kernel: [33965.827309] nouveau [ DRM] suspending client object trees... Nov 12 12:08:42 pk0k4dr kernel: [33965.835924] nouveau [ DRM] suspending kernel object tree... Nov 12 12:08:42 pk0k4dr kernel: [33966.209804] i915 :00:02.0: power state changed by ACPI to D3cold Nov 12 12:08:42 pk0k4dr kernel: [33966.429324] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 Nov 12 12:08:42 pk0k4dr kernel: [33966.429328] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 Nov 12 12:08:42 pk0k4dr kernel: [33966.429330] PM: Device :00:19.0 failed to suspend async: error -2 Nov 12 12:08:42 pk0k4dr kernel: [33967.221549] nouveau :01:00.0: power state changed by ACPI to D3cold Nov 12 12:08:42 pk0k4dr kernel: [33967.221613] PM: Some devices failed to suspend, or early wake event detected Nov 12 12:08:42 pk0k4dr kernel: [33967.221661] i915 :00:02.0: power state changed by ACPI to D0 Nov 12 12:08:42 pk0k4dr kernel: [33967.221684] xhci_hcd :00:14.0: setting latency timer to 64 Nov 12 12:08:42 pk0k4dr kernel: [33967.221737] mei_me :00:16.0: irq 45 for MSI/MSI-X ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jammy 3673 F pulseaudio Date: Tue Nov 12 13:42:10 2013 HibernationDevice: RESUME=UUID=36cdf9ac-9cc9-4649-9be0-ed0a81c29b26 InstallationDate: Installed on 2013-10-16 (26 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 987401] Re: Ubuntu should poweroff video cards not in use
Ubuntu 14.04 Trusty Tahr now has the 3.13.0-1.16 kernel. Can you please test this version and let us know the results? ** 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/987401 Title: Ubuntu should poweroff video cards not in use Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Bug description: I have a laptop with two video cards: lspci|grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: ATI Technologies Inc NI Whistler [AMD Radeon HD 6600M Series] (rev ff) I have looked around and I saw there is the vgaswitceroo module which can be used in order to turn on/off unused graphics cards and also switch the enabled one (albeit with X restarting). I believe Ubuntu should power off the unused card by default. The default behavior is to use the Integrated GPU (Intel) but still keeping the Discrete GPU (ATI) on. This can save up to 10W in my laptop, which is at least 50% more battery power previously wasted on keeping an unused GPU on. Best regards, Nikos --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrikos 3587 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 48' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,104d5300,0014 HDA:80862805,104d5300,0010' Controls : 17 Simple ctrls : 9 DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=2a386f35-058c-4b56-a4ef-086a54f6b10e InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Sony Corporation VPCCB2S1E Package: linux (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic root=UUID=30b47f3a-9136-4791-a5c8-f72e6b1c7362 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 RelatedPackageVersions: linux-restricted-modules-3.0.0-17-generic N/A linux-backports-modules-3.0.0-17-generic N/A linux-firmware1.60.1 StagingDrivers: mei Tags: oneiric running-unity staging Uname: Linux 3.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout kismet lpadmin plugdev sambashare dmi.bios.date: 04/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1100V2:bd04/15/2011:svnSonyCorporation:pnVPCCB2S1E:pvrC6099RLH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCCB2S1E dmi.product.version: C6099RLH dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267062] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1267062 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1267062 Title: sigaltstack system call unable to send proper return code (error12) Status in “linux” package in Ubuntu: Incomplete Bug description: 9.3.189.114 (root/.pasroot) (Host Machine) Run the follwoing command to go to the guest victim machine from (/var/lib/libvirt/images/jagan/new_ubuntu_alpha1) qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr- vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg- ppc64el.img.qcow2 after this command you will get the screen number. example: QEMU 1.6.0 monitor - type 'help' for more information (qemu) char device redirected to /dev/pts/16 (label serial0) Then open another host session and execute the below command # screen /dev/pts/16 (qemu) Here the screen number is /dev/pts/16 --Then you will get a blank screen so press ENTER key. The guest machine login: ubuntu/passw0rd Then do ---sudo -i Environment: === Host: Power8 Guest : ubuntu hosted on Power8 The issue: == sigaltstack system call unable send proper return value. How to run : --cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack -- ./sigaltstack02 == Getting the below error sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 = FAIL test_start tag=sigaltstack02 stime=1386653793 cmdline=sigaltstack02 contacts= analysis=exit test_output sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 execution_status initiation_status=ok duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 test_end sigaltstack() should fail and set errno to ENOMEM when the size of alternate stack area is less than MINSIGSTKSZ. But here its sigaltstack() is returning 0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267062] [NEW] sigaltstack system call unable to send proper return code (error12)
Public bug reported: 9.3.189.114 (root/.pasroot) (Host Machine) Run the follwoing command to go to the guest victim machine from (/var/lib/libvirt/images/jagan/new_ubuntu_alpha1) qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg- ppc64el.img.qcow2 after this command you will get the screen number. example: QEMU 1.6.0 monitor - type 'help' for more information (qemu) char device redirected to /dev/pts/16 (label serial0) Then open another host session and execute the below command # screen /dev/pts/16 (qemu) Here the screen number is /dev/pts/16 --Then you will get a blank screen so press ENTER key. The guest machine login: ubuntu/passw0rd Then do ---sudo -i Environment: === Host: Power8 Guest : ubuntu hosted on Power8 The issue: == sigaltstack system call unable send proper return value. How to run : --cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack -- ./sigaltstack02 == Getting the below error sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 = FAIL test_start tag=sigaltstack02 stime=1386653793 cmdline=sigaltstack02 contacts= analysis=exit test_output sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 execution_status initiation_status=ok duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 test_end sigaltstack() should fail and set errno to ENOMEM when the size of alternate stack area is less than MINSIGSTKSZ. But here its sigaltstack() is returning 0. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: ppc64el -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1267062 Title: sigaltstack system call unable to send proper return code (error12) Status in “linux” package in Ubuntu: Incomplete Bug description: 9.3.189.114 (root/.pasroot) (Host Machine) Run the follwoing command to go to the guest victim machine from (/var/lib/libvirt/images/jagan/new_ubuntu_alpha1) qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr- vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg- ppc64el.img.qcow2 after this command you will get the screen number. example: QEMU 1.6.0 monitor - type 'help' for more information (qemu) char device redirected to /dev/pts/16 (label serial0) Then open another host session and execute the below command # screen /dev/pts/16 (qemu) Here the screen number is /dev/pts/16 --Then you will get a blank screen so press ENTER key. The guest machine login: ubuntu/passw0rd Then do ---sudo -i Environment: === Host: Power8 Guest : ubuntu hosted on Power8 The issue: == sigaltstack system call unable send proper return value. How to run : --cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack -- ./sigaltstack02 == Getting the below error sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 = FAIL test_start tag=sigaltstack02 stime=1386653793 cmdline=sigaltstack02 contacts= analysis=exit test_output sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 execution_status initiation_status=ok duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 test_end sigaltstack() should fail and set errno to ENOMEM when the size of alternate stack area is less than MINSIGSTKSZ. But here its sigaltstack() is returning 0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1264879] Re: Xorg freeze / System Freeze after suspend
I will run the tests with the latest build over the weekend and post the results. Some additional information, if I switch to nvidia proprietary driver the issue does not reproduce. Also if I shutdown X (lightgdm stop) the suspend function works as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1264879 Title: Xorg freeze / System Freeze after suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Problem is related to suspend, regardless if the lid of the laptop is closed or Suspend from the menu is pressed. At resume, the screen is displayed and only the mouse can move for 10-15 seconds then everything freezes. One time I managed to switch to terminal mode and issue a lightgdm restart: The login window appeared but after the correct username/password was provided it was enable to start the session and the login prompt appeared again. So far I have tried playing with boot parameters: pcie_aspm=force (no change) nomodeset (it makes the problem worst the screen is black, not even the backlight seems to be on) Also I have tried running from : https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting wget http://people.ubuntu.com/~apw/suspend-resume/test-suspend sudo bash test-suspend --full Test1 is not able to suspend the machine, test 2 does suspend it but it does not wake up automatically after 20 seconds. And when I press a key to wake it up... it freezes. The issue does not reproduce on the same hardware with LMDE MATE Edition, Proprietary nvidia drivers, Linux 3.10-2-amd64 (x86_64), Compiled #1 SMP Debian 3.10.5-1 (2013-08-07). Any other information I could provide? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Dec 29 21:59:45 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:392d] InstallationDate: Installed on 2013-12-27 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20042 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=UUID=8a4ec989-c440-49bb-8f12-704848322677 ro persistent vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 01/28/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 29CN38WW(V2.15) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr29CN38WW(V2.15):bd01/28/2011:svnLENOVO:pn20042:pvrLenovoG560:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 20042 dmi.product.version: Lenovo G560 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Dec 29 19:50:10 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile:
[Kernel-packages] [Bug 1264879] Re: Xorg freeze / System Freeze after suspend
** Description changed: - Problem is related to suspend, regardless if the lid of the laptop is closed or Suspend from the menu is pressed. - At resume, the screen is displayed and only the mouse can move for 10-15 seconds then everything freezes. - One time I managed to switch to terminal mode and issue a lightgdm restart: The login window appeared but after the correct username/password was provided it was enable to start the session and the login prompt appeared again. - So far I have tried playing with boot parameters: - pcie_aspm=force (no change) - nomodeset (it makes the problem worst the screen is black, not even the backlight seems to be on) + Problem is related to suspend, regardless if the lid of the laptop is closed or Suspend from the menu is pressed. + At resume, the screen is displayed and only the mouse can move for 10-15 seconds then everything freezes. + One time I managed to switch to terminal mode and issue a lightgdm restart: The login window appeared but after the correct username/password was provided it was enable to start the session and the login prompt appeared again. + So far I have tried playing with boot parameters: + pcie_aspm=force (no change) + nomodeset (it makes the problem worst the screen is black, not even the backlight seems to be on) Also I have tried running from : https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting wget http://people.ubuntu.com/~apw/suspend-resume/test-suspend sudo bash test-suspend --full - Test1 is not able to suspend the machine, - test 2 does suspend it but it does not wake up automatically after 20 seconds. And when I press a key to wake it up... it freezes. + Test1 is not able to suspend the machine, + test 2 does suspend it but it does not wake up automatically after 20 seconds. And when I press a key to wake it up... it freezes. - The issue does not reproduce on the same hardware with LMDE MATE Edition, Proprietary nvidia drivers, - Linux 3.10-2-amd64 (x86_64), Compiled #1 SMP Debian 3.10.5-1 (2013-08-07). - - Any other information I could provide? + WORKAROUND: The issue does not reproduce on the same hardware with LMDE + MATE Edition, Proprietary nvidia drivers, Linux 3.10-2-amd64 (x86_64), + Compiled #1 SMP Debian 3.10.5-1 (2013-08-07). Also if I shutdown X + (lightgdm stop) the suspend function works as expected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: - + ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Dec 29 21:59:45 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed - bcmwl, 6.30.223.141+bdcom, 3.11.0-14-generic, x86_64: installed + bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed + bcmwl, 6.30.223.141+bdcom, 3.11.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: - NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:392d] + NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:392d] InstallationDate: Installed on 2013-12-27 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20042 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=UUID=8a4ec989-c440-49bb-8f12-704848322677 ro persistent vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: - + dmi.bios.date: 01/28/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 29CN38WW(V2.15) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr29CN38WW(V2.15):bd01/28/2011:svnLENOVO:pn20042:pvrLenovoG560:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 20042 dmi.product.version: Lenovo G560 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs:
[Kernel-packages] [Bug 1212856] Re: Kernel Panic - Not syncing : Fatal Exception in Interrupt in 12.04.2 LTS (64-bit)
@Christopher,
While trying to execute command ubuntu-bug linux. I get a screen stating
that Collecting problem information. But the system just hangs after
about 4-5 seconds. I am forced to restart the system.
I am now refering to links mentioned above and trying to find the
solution.
Thanking you,
nakul
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212856
Title:
Kernel Panic - Not syncing : Fatal Exception in Interrupt in 12.04.2
LTS (64-bit)
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
Several times, when I boot my Ubuntu 12.04.2 LTS (Precise Pangolin)
64-bit installation, I get a kernel panic during the boot. When that
happens, I have to power the machine down and power it up again.
Sometimes, the kernel panic happens several times in a row, until the
machine finally boots.
The hardware is a HP Pavilion dv6 laptop, running in Dual-Boot with
Windows 7 Home Premium (also 64-bit).
I have all Updates installed to this date (15-aug-2013), including the
kernel updates: the running kernel is 3.5.0-37
Here's the output from uname -a :
$ Linux [hostname] 3.5.0-37-generic #58~precise1-Ubuntu SMP Wed Jul 10
17:48:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
The last message of the kernel panic is almost always the following:
Kernel Panic - Not syncing : Fatal Exception in Interrupt
Sometimes, there's a message below that stating:
Shutting down cpus with NMI
The messages above the Kernel Panic message are usually different
each time. I have photographed several of the Kernel Panic screens
and I can attach some of them to this Bug Report, if that's useful.
In case it's relevant, my partition setup for this Ubuntu installation
is the following:
1 - a /boot partition (formatted as ext3)
2 - a swap partition
3 - a / partition (formatted as ext4), with encrypted home folder.
Please tell me if I should add any information to this bug report.
Thanks in advance.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-37-generic 3.5.0-37.58~precise1
ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic x86_64
NonfreeKernelModules: nvidia wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ricardo2032 F pulseaudio
/dev/snd/controlC0: ricardo2032 F pulseaudio
CRDA:
country PT:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb10 irq 43'
Mixer name : 'IDT 92HD75B3X5'
Components : 'HDA:111d7603,103c3659,00100202'
Controls : 21
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xd300 irq 44'
Mixer name : 'Nvidia GPU 0b HDMI/DP'
Components : 'HDA:10de000b,10de0101,00100100'
Controls : 24
Simple ctrls : 4
Date: Thu Aug 15 22:16:36 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3ddeb984-b63d-45cf-825f-04e59e87166d
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
MarkForUpload: True
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-37-generic
root=UUID=bd2ded4b-faa2-439f-b387-16292df03932 ro
RelatedPackageVersions:
linux-restricted-modules-3.5.0-37-generic N/A
linux-backports-modules-3.5.0-37-generic N/A
linux-firmware1.79.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3659
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 32.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.15:bd01/05/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 049D212412102
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212856/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 107937] [NEW] Laptop is hotter with Ubuntu installed
You have been subscribed to a public bug: My laptop (HP nc8430, Core 2 Duo 2 GHz, ATI x1600) is very hot with Ubuntu 7.04 installed. If I boot Windows, the CPU temperature is normal but in Feisty it gets over 80 degrees Celsium and I have frequency scaling enabled and fans turned on all the time. ** Affects: linux (Ubuntu) Importance: Low Status: Incomplete -- Laptop is hotter with Ubuntu installed https://bugs.launchpad.net/bugs/107937 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 1260610] Re: CVE-2013-2929
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux (Ubuntu Raring) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Raring) 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/1260610 Title: CVE-2013-2929 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: New 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 Released 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 Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Fix Committed Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Committed 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
[Kernel-packages] [Bug 1241769] Re: CVE-2013-4299
** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1241769 Title: CVE-2013-4299 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: 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-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 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 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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: Fix Released 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
[Kernel-packages] [Bug 1260613] Re: CVE-2013-2930
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** 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/1260613 Title: CVE-2013-2930 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: New 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 Released 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: New Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Committed Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 1229981] Re: CVE-2013-4345
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1229981 Title: CVE-2013-4345 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: 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-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 Released Status in “linux-lts-raring” source package in Precise: New 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: New Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 107937] Re: Laptop is hotter with Ubuntu installed
Matic Zgur, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux REPLACE-WITH-BUG-NUMBER If reproducible, could you also please test the latest upstream kernel available (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-v3.13-rc7 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. ** This bug is no longer a duplicate of bug 887842 Open-source radeon driver causes system to run hot. ** Package changed: acpi (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Attachment removed: lshw https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/243399/+files/lshw ** Attachment removed: lshal https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/243408/+files/lshal ** Attachment removed: lspci https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/243409/+files/lspci ** Attachment removed: dmesg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/243664/+files/dmesg ** Attachment removed: trip_points-cpu_info https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/428852/+files/trip_points-cpu_info ** Attachment removed: lshal https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/428853/+files/lshal ** Attachment removed: lshw https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/428854/+files/lshw ** Attachment removed: syslog https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/243665/+files/syslog ** Attachment removed: syslog.tgz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/428858/+files/syslog.tgz ** Attachment removed: acpi-debug.tgz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/428860/+files/acpi-debug.tgz ** Attachment removed: dmesg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+attachment/428856/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/107937 Title: Laptop is hotter with Ubuntu installed Status in “linux” package in Ubuntu: Incomplete Bug description: My laptop (HP nc8430, Core 2 Duo 2 GHz, ATI x1600) is very hot with Ubuntu 7.04 installed. If I boot Windows, the CPU temperature is normal but in Feisty it gets over 80 degrees Celsium and I have frequency scaling enabled and fans turned on all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/107937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 987401] Re: Ubuntu should poweroff video cards not in use
Good news that the code to enable this has finaly landed in Linux. Unfortunately, I don't have access to the hardware where this bug was initially reported against, so I cannot test this new functionality -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/987401 Title: Ubuntu should poweroff video cards not in use Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Bug description: I have a laptop with two video cards: lspci|grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: ATI Technologies Inc NI Whistler [AMD Radeon HD 6600M Series] (rev ff) I have looked around and I saw there is the vgaswitceroo module which can be used in order to turn on/off unused graphics cards and also switch the enabled one (albeit with X restarting). I believe Ubuntu should power off the unused card by default. The default behavior is to use the Integrated GPU (Intel) but still keeping the Discrete GPU (ATI) on. This can save up to 10W in my laptop, which is at least 50% more battery power previously wasted on keeping an unused GPU on. Best regards, Nikos --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrikos 3587 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 48' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,104d5300,0014 HDA:80862805,104d5300,0010' Controls : 17 Simple ctrls : 9 DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=2a386f35-058c-4b56-a4ef-086a54f6b10e InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Sony Corporation VPCCB2S1E Package: linux (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic root=UUID=30b47f3a-9136-4791-a5c8-f72e6b1c7362 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 RelatedPackageVersions: linux-restricted-modules-3.0.0-17-generic N/A linux-backports-modules-3.0.0-17-generic N/A linux-firmware1.60.1 StagingDrivers: mei Tags: oneiric running-unity staging Uname: Linux 3.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout kismet lpadmin plugdev sambashare dmi.bios.date: 04/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1100V2:bd04/15/2011:svnSonyCorporation:pnVPCCB2S1E:pvrC6099RLH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCCB2S1E dmi.product.version: C6099RLH dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248703] Re: CVE-2013-4470
** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1248703 Title: CVE-2013-4470 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: 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: Fix Released 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 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Released Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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: Fix Released 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
[Kernel-packages] [Bug 1267062] Re: sigaltstack system call unable to send proper return code (error12)
** 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/1267062 Title: sigaltstack system call unable to send proper return code (error12) Status in “linux” package in Ubuntu: Confirmed Bug description: 9.3.189.114 (root/.pasroot) (Host Machine) Run the follwoing command to go to the guest victim machine from (/var/lib/libvirt/images/jagan/new_ubuntu_alpha1) qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append root=/dev/sda -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr- vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg- ppc64el.img.qcow2 after this command you will get the screen number. example: QEMU 1.6.0 monitor - type 'help' for more information (qemu) char device redirected to /dev/pts/16 (label serial0) Then open another host session and execute the below command # screen /dev/pts/16 (qemu) Here the screen number is /dev/pts/16 --Then you will get a blank screen so press ENTER key. The guest machine login: ubuntu/passw0rd Then do ---sudo -i Environment: === Host: Power8 Guest : ubuntu hosted on Power8 The issue: == sigaltstack system call unable send proper return value. How to run : --cd /root/ltp-full-20130904/testcases/kernel/syscalls/sigaltstack -- ./sigaltstack02 == Getting the below error sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 = FAIL test_start tag=sigaltstack02 stime=1386653793 cmdline=sigaltstack02 contacts= analysis=exit test_output sigaltstack021 TPASS : stgaltstack() fails, Invalid Flag value, errno:22 sigaltstack022 TFAIL : sigaltstack() returned 0, expected -1, errno:12 execution_status initiation_status=ok duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 test_end sigaltstack() should fail and set errno to ENOMEM when the size of alternate stack area is less than MINSIGSTKSZ. But here its sigaltstack() is returning 0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1252419] Re: CVE-2013-4511
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1252419 Title: CVE-2013-4511 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: 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-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 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 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 1249272] Re: CVE-2013-4513
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1249272 Title: CVE-2013-4513 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: 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: 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: Invalid Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 1249276] Re: CVE-2013-4515
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1249276 Title: CVE-2013-4515 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 Released 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 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 1249274] Re: CVE-2013-4514
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1249274 Title: CVE-2013-4514 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 Released 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 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 1261564] Re: CVE-2013-4587
** Changed in: linux (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1261564 Title: CVE-2013-4587 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: New 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: 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 Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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: 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
[Kernel-packages] [Bug 1261566] Re: CVE-2013-6367
** Changed in: linux (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1261566 Title: CVE-2013-6367 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: New 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: 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 Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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: 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
[Kernel-packages] [Bug 1261568] Re: CVE-2013-6368
** Changed in: linux (Ubuntu Trusty) Status: New = Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1261568 Title: CVE-2013-6368 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: New 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: 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 Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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: 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
[Kernel-packages] [Bug 1254900] Re: CVE-2013-4592
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux (Ubuntu Raring) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Raring) 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/1254900 Title: CVE-2013-4592 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: 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: 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: Invalid 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 Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Fix Committed Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Committed 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”
[Kernel-packages] [Bug 1256080] Re: CVE-2013-6378
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux (Ubuntu Raring) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Raring) 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/1256080 Title: CVE-2013-6378 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: 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-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 Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: Fix Committed Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Committed 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
[Kernel-packages] [Bug 1256083] Re: CVE-2013-6380
** Changed in: linux-armadaxp (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New = Fix Committed ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: New = Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Raring) 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/1256083 Title: CVE-2013-6380 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: 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: New 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: New Status in “linux” source package in Quantal: Fix Committed Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Committed Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Committed 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
[Kernel-packages] [Bug 1256094] Re: CVE-2013-6383
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1256094 Title: CVE-2013-6383 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: 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: Fix Released 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 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 1260622] Re: CVE-2013-7027
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1260622 Title: CVE-2013-7027 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: New 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: Fix Released 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 Released Status in “linux-lts-raring” source package in Precise: Fix Released 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: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Fix Released 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:
[Kernel-packages] [Bug 1260619] Re: CVE-2013-7026
** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1260619 Title: CVE-2013-7026 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: New 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: New Status in “linux-lts-raring” source package in Precise: New 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: New Status in “linux” source package in Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: New 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: 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
[Kernel-packages] [Bug 1252426] Re: CVE-2013-6763
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Saucy) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Quantal) Status: Fix Committed = Fix Released ** Changed in: linux-ti-omap4 (Ubuntu Raring) Status: Fix Committed = Fix Released ** Changed in: linux-lts-raring (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1252426 Title: CVE-2013-6763 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: 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-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 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 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 Quantal: Fix Released Status in “linux-armadaxp” source package in Quantal: Fix Committed Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid 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-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: Won't Fix Status in “linux-lts-backport-natty” source package in Raring: Won't Fix Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: 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
[Kernel-packages] [Bug 1267075] [NEW] CVE-2013-7263
*** This bug is a security vulnerability *** Public security bug reported: The Linux kernel before 3.12.4 updates certain length values before ensuring that associated data structures have been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call, related to net/ipv4/ping.c, net/ipv4/raw.c, net/ipv4/udp.c, net/ipv6/raw.c, and net/ipv6/udp.c. Break-Fix: - bceaa90240b6019ed73b49965eac7d167610be69 ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects:
[Kernel-packages] [Bug 1267075] Re: CVE-2013-7263
CVE-2013-7263 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1267078] [NEW] CVE-2013-7264
*** This bug is a security vulnerability *** Public security bug reported: The l2tp_ip_recvmsg function in net/l2tp/l2tp_ip.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - bceaa90240b6019ed73b49965eac7d167610be69 ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring)
[Kernel-packages] [Bug 1267078] Re: CVE-2013-7264
CVE-2013-7264 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1267079] [NEW] CVE-2013-7265
*** This bug is a security vulnerability *** Public security bug reported: The pn_recvmsg function in net/phonet/datagram.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel stack memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - bceaa90240b6019ed73b49965eac7d167610be69 ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance:
[Kernel-packages] [Bug 1267079] Re: CVE-2013-7265
CVE-2013-7265 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1266984] Re: Kernel 3.13-rc7 [AMD Radeon HD 6800] System Crashes and Reboots
Can you test the 3.12.6 kernel and the 3.13-rc1 to 3.13-rc6 kernels and see if you can find where it broke? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1266984 Title: Kernel 3.13-rc7 [AMD Radeon HD 6800] System Crashes and Reboots Status in “linux” package in Ubuntu: Confirmed Bug description: Using the latest 3.13-rc7 on two of my AMD machines, both of which have Radeon HD 6850 graphics cards in them, the system crashes when playing videos. I think it may be easier to cause the crash when playing a video that is 720p+. It also is not limited to crashing when playing videos, but can also crash simply from browsing the web or doing anything that causes a demand on the GPU. It may or may not be related to DPM implemented in the latest kernels. Using kernel 3.12 from Trusty repos with DPM enabled, it works fine. I have a machine with a Radeon HD 7950 but I have not tested it yet. Similarly, I have used an AMD Richland APU which crashes with kernel 3.13 immediately on the login screen. Put simply, there needs to be a lot of testing of AMD chips before releasing kernel 3.13 for Trusty stable. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ching 2397 F pulseaudio /dev/snd/controlC0: ching 2397 F pulseaudio CRDA: country AU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (3, 23) (5250 - 5330 @ 40), (3, 23), DFS (5735 - 5835 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Jan 7 23:50:13 2014 HibernationDevice: RESUME=UUID=39d467a4-e793-46df-9a88-10813a999704 MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=1533ba1d-4ff6-4974-839f-5074ef65a6f1 ro splash quiet radeon.audio=1 radeon.dpm=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.119 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78T-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/13/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267081] [NEW] CVE-2013-7266
*** This bug is a security vulnerability *** Public security bug reported: The mISDN_sock_recvmsg function in drivers/isdn/mISDN/socket.c in the Linux kernel before 3.12.4 does not ensure that a certain length value is consistent with the size of an associated data structure, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring)
[Kernel-packages] [Bug 1267081] Re: CVE-2013-7266
CVE-2013-7266 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1267082] Re: CVE-2013-7267
CVE-2013-7267 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1267082] [NEW] CVE-2013-7267
*** This bug is a security vulnerability *** Public security bug reported: The atalk_recvmsg function in net/appletalk/ddp.c in the Linux kernel before 3.12.4 updates a certain length value without ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance: Low
[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
Hi Joseph, with bit delay, happy new year. I tested your Kernel, and it works (FYI: i disabled my grub command line parameter pci=realloc=off) some infos: Linux production01 3.13.0-031300rc2-generic #201312121210 SMP Thu Dec 12 17:12:35 UTC 2013 x86_64 GNU/Linux modinfo ixgbe filename: /lib/modules/3.13.0-031300rc2-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:3.15.1-k lspci -v 22:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01) Subsystem: Intel Corporation Ethernet Server Adapter X520-2 Flags: bus master, fast devsel, latency 0, IRQ 60 Memory at e360 (64-bit, non-prefetchable) [size=512K] I/O ports at bcc0 [size=32] Memory at e37f8000 (64-bit, non-prefetchable) [size=16K] Expansion ROM at e370 [disabled] [size=512K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] MSI-X: Enable+ Count=64 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [e0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-1b-21-ff-ff-9c-f7-70 Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [160] Single Root I/O Virtualization (SR-IOV) Kernel driver in use: ixgbe Thomas -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1267083] [NEW] CVE-2013-7268
*** This bug is a security vulnerability *** Public security bug reported: The ipx_recvmsg function in net/ipx/af_ipx.c in the Linux kernel before 3.12.4 updates a certain length value without ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance: Low
[Kernel-packages] [Bug 1267085] [NEW] CVE-2013-7269
*** This bug is a security vulnerability *** Public security bug reported: The nr_recvmsg function in net/netrom/af_netrom.c in the Linux kernel before 3.12.4 updates a certain length value without ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance: Low
[Kernel-packages] [Bug 1267085] Re: CVE-2013-7269
CVE-2013-7269 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1267087] [NEW] CVE-2013-7270
*** This bug is a security vulnerability *** Public security bug reported: The packet_recvmsg function in net/packet/af_packet.c in the Linux kernel before 3.12.4 updates a certain length value before ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance:
[Kernel-packages] [Bug 1267087] Re: CVE-2013-7270
CVE-2013-7270 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1267090] Re: CVE-2013-7271
CVE-2013-7271 ** 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 Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) 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 Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) 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 Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1267090] [NEW] CVE-2013-7271
*** This bug is a security vulnerability *** Public security bug reported: The x25_recvmsg function in net/x25/af_x25.c in the Linux kernel before 3.12.4 updates a certain length value without ensuring that an associated data structure has been initialized, which allows local users to obtain sensitive information from kernel memory via a (1) recvfrom, (2) recvmmsg, or (3) recvmsg system call. Break-Fix: - f3d3342602f8bcbf37d7c46641cb9bca7618eb1c ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low 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: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low 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: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance: Low
[Kernel-packages] [Bug 1263681] Re: DisplayPort hotplugging is not detected on a ThinkPad X220
Managed to update the BIOS at last (by following the advice from http://www.floccinaucinihilipilification.net/blog/2011/10/2/updating- the-bios-of-a-thinkpad-x220-using-linux.html). $ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date 8DET69WW (1.39 ) 07/18/2013 DisplayPort hotplugging continues to not work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263681 Title: DisplayPort hotplugging is not detected on a ThinkPad X220 Status in “linux” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Get a Lenovo ThinkPad X220 with Intel graphics (PCI ID 8086:0126, rev 09) 2. Get a DisplayPort - DVI cable, plug the DVI end into a monitor (Samsung SyncMaster 193p+) 3. Plug the DP end into the ThinkPad What I expect: - hotplug is detected within a reasonable time, GNOME automatically extends my desktop What actually happens - nothing Things that work: - if I run 'xrandr' in an xterm, the monitor is detected instantly and GNOME reconfigures the screen. - if I open System Preferences - Display, it does an xrandr probe behind my back and instantly detects/reconfigures the screen. - if I plug the DP cable before I open the laptop lid to wake it up from S3 sleep, the external monitor is detected. - if I use a VGA cable instead of the DP - DVI one, hotplug is detected within seconds - if I *unplug* the DP cable, the unplug is detected instantly. - I once waited ~5 minutes without running xrandr, and it actually detected the monitor and reconfigured. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-extra-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mg 2722 F pulseaudio Date: Mon Dec 23 14:33:12 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=bf592a79-5f4e-486d-b69d-7525d492dcc6 InstallationDate: Installed on 2012-07-25 (515 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: 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 4291WJF MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=36079681-53fc-4ca2-80ac-98321c07e8d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-17 (66 days ago) WifiSyslog: dmi.bios.date: 05/31/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET47WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291WJF 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:bvr8DET47WW(1.17):bd05/31/2011:svnLENOVO:pn4291WJF:pvrThinkPadX220:rvnLENOVO:rn4291WJF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291WJF dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 998200] Re: Wrong driver for GigE Net Cards RTL8111/8168B
I have RTL8111/8168/8411 which loads r8169 too (in Ubuntu 12.04). Raised
separated ticket just in case
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266725 pls merge
if it's duplicate or pls fix driver for my card too if it's separate but
similar issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/998200
Title:
Wrong driver for GigE Net Cards RTL8111/8168B
Status in HWE Next Project:
Fix Released
Status in The Linux Kernel:
Fix Released
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Precise:
New
Status in “linux” source package in Quantal:
New
Bug description:
Symptoms : Wireless connection ultra slow, but working
r8169 module was loaded in modprobe, but r8168 was needed for better
performances.
lspci lines:
01:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 (rev
34)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B
PCI Express Gigabit Ethernet controller (rev 06)
OS: ubuntu 12.04 64bit (new install)
Hardware: samsung series 5 NP530U3B-A02FR
see also :
http://askubuntu.com/questions/96343/internet-unusably-slow-with-realtek-semiconductor-co-ltd-rtl8111-8168b-card
http://amk1.wordpress.com/2009/06/09/realtek-8168-module-issue/
Driver I used to get it work : LINUX driver for kernel 2.6.x and 2.4.x
(Support x86 and x64)
8.029.00 2012/3/29 @
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1PNid=13PFid=5Level=5Conn=4DownTypeID=3GetDown=false
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1816 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 48'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0269,144dc0c7,00100202
HDA:80862805,80860101,0010'
Controls : 25
Simple ctrls : 12
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=870a0871-aafe-49c4-9ea8-d05af6aec76c
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_AU:en
TERM=xterm
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=cea150a2-afd6-4955-859e-e5ed68cccea1 ro quiet splash pcie_aspm=force
vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: mei
Tags: precise staging precise staging
Uname: Linux 3.2.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/18/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04XK
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 530U3BI/530U4BI/530U4BH
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr04XK:bd01/18/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3BI/530U4BI/530U4BH
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/998200/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 607560] Re: jbd2 writing block every 5 - 10 seconds, preventing disk spin-down and making noise
** 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/607560 Title: jbd2 writing block every 5 - 10 seconds, preventing disk spin-down and making noise Status in “linux” package in Ubuntu: Confirmed Bug description: jbd2 writes blocks to the hard disk every 5 seconds. This makes an annoying click/tick noise and prevents the disk from spinning down to conserve power. jbd2 appears in logs as several entries like... Jul 19 21:35:45 edge kernel: [ 3312.913759] jbd2/sda5-8(350): WRITE block 42280704 on sda5 ... and can be observed using iotop. Since the noise only occurs in Ubuntu and not in Windows 7 it is probably a software problem. The excessive writes may reduce the disk's lifespan. WORKAROUND: Adding commit=60 to the partition's entry in fstab increases the interval to 30-45 seconds. Threads covering this problem * http://ubuntuforums.org/showthread.php?t=1489637 * https://bbs.archlinux.org/viewtopic.php?pid=692073 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-23-generic-pae 2.6.32-23.37 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-23.37-generic-pae 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rcx 2456 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 22' Mixer name : 'Intel G45 DEVIBX' Components : 'HDA:10ec0269,17aa21bc,0014 HDA:80862804,80860101,0010' Controls : 16 Simple ctrls : 8 Date: Mon Jul 19 23:24:03 2010 Frequency: Every 5-10 seconds. HibernationDevice: RESUME=UUID=ae276af8-b805-466a-a688-8d175cd3f2d7 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: LENOVO 05782AU ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic-pae root=UUID=01d19f79-8c81-4da6-949d-db8f4d85b84a ro quiet splash ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 RelatedPackageVersions: linux-firmware 1.34.1 SourcePackage: linux dmi.bios.date: 06/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 80ET37WW (1.14 ) dmi.board.name: 05782AU 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:bvr80ET37WW(1.14):bd06/11/2010:svnLENOVO:pn05782AU:pvrThinkPadEdge:rvnLENOVO:rn05782AU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 05782AU dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1260330] Re: linux: 3.12.0-8.16 -proposed tracker
*** This bug is a duplicate of bug 1266852 *** https://bugs.launchpad.net/bugs/1266852 ** This bug has been marked a duplicate of bug 1266852 linux: 3.13.0-1.16 -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/1260330 Title: linux: 3.12.0-8.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow package-testing series: New Status in Kernel Development Workflow prepare-package series: In Progress Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Trusty: New Bug description: This bug is for tracking the 3.12.0-8.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 12. December 2013 13:50 UTC kernel-phase-changed:Thursday, 12. December 2013 13:50 UTC kernel-phase:Prepare To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1260330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266852] Re: linux: 3.13.0-1.16 -proposed tracker
** Changed in: kernel-development-workflow/package-testing Status: Confirmed = Fix Released ** Changed in: kernel-development-workflow/promote-to-release Status: New = Fix Released ** Changed in: kernel-development-workflow Status: In Progress = 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/1266852 Title: linux: 3.13.0-1.16 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow package-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.13.0-1.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 07. January 2014 17:14 UTC kernel-Package-testing-start:Wednesday, 08. January 2014 04:58 UTC kernel-phase:Testing kernel-phase-changed:Wednesday, 08. January 2014 04:58 UTC kernel-Prepare-package-end:Wednesday, 08. January 2014 04:58 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1266852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248270] Re: Please set CONFIG_EXT3_FS=n and CONFIG_EXT2_FS=n and CONFIG_EXT4_USE_FOR_EXT23=y
linux-3.13.0-1.16 ** Changed in: linux (Ubuntu Trusty) Status: In Progress = 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/1248270 Title: Please set CONFIG_EXT3_FS=n and CONFIG_EXT2_FS=n and CONFIG_EXT4_USE_FOR_EXT23=y Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: When the old code is disabled the ext4 driver takes over and does a better job and gives a smaller kernel. Specifically the ext4 driver does a better job of resisting fragmentation since it uses delayed allocation, and supports online resize, whereas the ext2 driver does not. Config changes requested: CONFIG_EXT3_FS=y - n CONFIG_EXT2_FS=y - n CONFIG_EXT4_USE_FOR_EXT23 (NEW) - y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1190341] Re: [MacBookPro10, 1] Backlight stopped working after update of linux-image with nvidia 313.30
No working backlight with daily-live ISO image downloaded yesterday :-( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1190341 Title: [MacBookPro10,1] Backlight stopped working after update of linux-image with nvidia 313.30 Status in “linux” package in Ubuntu: Incomplete Bug description: I am using Ubuntu 13.04, nvidia 313.30, fresh installation from scratch, on a MacBookPro10,1 (the one with Retina display). Two of my partition are encrypted (swap and /srv on which /home is bind mounted).Since some upgrade to linux-image-3.8.0-24 backlight control does not work anymore. I am stuck with 3.8.0-23 in order to get something kind of working (I have to go in sleep mode at least once in order to get backlight control available). The last almost working kernel is 3.8.0-23. I even tried 3.9.0-030900 upstream kernel with no success. Everything was working fine with the first installation of 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-23-generic 3.8.0-23.34 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruno 2696 F pulseaudio /dev/snd/controlC0: bruno 2696 F pulseaudio CRDA: country FR: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Wed Jun 12 21:02:22 2013 HibernationDevice: RESUME=UUID=a703c1e3-dfc2-46af-9905-b21abb747366 InstallationDate: Installed on 2013-02-06 (126 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121017.3) MachineType: Apple Inc. MacBookPro10,1 MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=5cafafc5-a506-4205-b6ba-e9fed6f9db99 ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-23-generic N/A linux-backports-modules-3.8.0-23-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-05 (68 days ago) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B02.1208081132 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B02.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1244645] Re: 8086:0106 [Lenovo B570] Brightness is at 100 percent and will not change
Here's the thread from ubuntu forums where this has been disscussed http://ubuntuforums.org/showthread.php?t=2181534. Christopher, This is more than an issue with the B570 as this is happening to most computers with Intel Graphics. The workaround is written here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244645/comments/4 as all it does is load an x11 module for the Intel Backlight device wich for some reason is not loaded upon installation by default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244645 Title: 8086:0106 [Lenovo B570] Brightness is at 100 percent and will not change Status in “linux” package in Ubuntu: Confirmed Bug description: I have seen this issue before as it was in the 13.10 betas. When I try any setting and method to change the brigtness it fails and remains at 100%. PLease feel free to contact me to get more information WORKAROUND: Create /usr/share/X11/xorg.conf.d/20-intel.conf with the following text: Section Device Identifier card0 Driver intel Option Backlight intel_backlight BusID PCI:0:2:0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 22.303888] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 22.304339] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 54.899779] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 54.952839] ISO 9660 Extensions: RRIP_1991A Date: Fri Oct 25 07:36:52 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3975] InstallationDate: Installed on 2013-10-25 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MachineType: LENOVO 1068BAU MarkForUpload: True ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=96b54589-c267-4291-b79c-3ff62dddb522 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN43WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pn1068BAU:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 1068BAU dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Oct 25 07:34:51 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.14.3-3ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265024] Re: TLS register TPIDRURW not preserved on context switch and fork
This kernel doesn't boot for me either, although I'm not really sure what is going wrong. I've installed it by downloading linux-headers-3.2.0-58-omap, linux- headers-3.2.0-58 and linux-image-3.2.0-58-omap, doing dpkg -i on those three .debs, and later run a modified version of the flash-kernel script to install it (to allow this to be flashed despite the omap vs omap4 mismatch). On boot it goes as far as Starting kernel ... but it never prints Uncompressing Linux as the other kernels do. The test kernel I built myself that works just fine was built using the cross building instructions from http://omappedia.org/wiki/Ubuntu_kernel_for_OMAP4, based on http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- precise.git;a=shortlog;h=refs/heads/ti-omap4, with the cherry-picked conflict resolved as in the attached patch. ** Patch added: 0001-ARM-7735-2-Preserve-the-user-r-w-register-TPIDRURW-o.patch https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/1265024/+attachment/3943370/+files/0001-ARM-7735-2-Preserve-the-user-r-w-register-TPIDRURW-o.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1265024 Title: TLS register TPIDRURW not preserved on context switch and fork Status in “linux-ti-omap4” package in Ubuntu: In Progress Bug description: Please backport commit a4780adeefd042482f624f5e0d577bf9cdcbb760 (which is included in upstream kernel 3.11) to the ti-omap4 packages for ubuntu precise. I tried doing this manually, and when cherrypicking there's a minor pretty trivial conflict to resolve, and after cherrypicking it works just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/1265024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266551] Re: linux: 3.2.0-59.89 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress = 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/1266551 Title: linux: 3.2.0-59.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-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 Precise: New Bug description: This bug is for tracking the 3.2.0-59.89 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 06. January 2014 19:37 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Monday, 06. January 2014 19:37 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266857] Re: linux: 3.5.0-46.69 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New = In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New = Fix Released ** Description changed: This bug is for tracking the 3.5.0-46.69 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, 07. January 2014 17:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 07. January 2014 17:18 UTC + kernel-stable-Certification-testing-end:Wednesday, 08. January 2014 14:02 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/1266857 Title: linux: 3.5.0-46.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress 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-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Quantal: New Bug description: This bug is for tracking the 3.5.0-46.69 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, 07. January 2014 17:18 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Tuesday, 07. January 2014 17:18 UTC kernel-stable-Certification-testing-end:Wednesday, 08. January 2014 14:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 987401] Re: Ubuntu should poweroff video cards not in use
OK, I hope you don't mind if I mark this bug as Fix Released. ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/987401 Title: Ubuntu should poweroff video cards not in use Status in “linux” package in Ubuntu: Fix Released Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Bug description: I have a laptop with two video cards: lspci|grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: ATI Technologies Inc NI Whistler [AMD Radeon HD 6600M Series] (rev ff) I have looked around and I saw there is the vgaswitceroo module which can be used in order to turn on/off unused graphics cards and also switch the enabled one (albeit with X restarting). I believe Ubuntu should power off the unused card by default. The default behavior is to use the Integrated GPU (Intel) but still keeping the Discrete GPU (ATI) on. This can save up to 10W in my laptop, which is at least 50% more battery power previously wasted on keeping an unused GPU on. Best regards, Nikos --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrikos 3587 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 48' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,104d5300,0014 HDA:80862805,104d5300,0010' Controls : 17 Simple ctrls : 9 DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=2a386f35-058c-4b56-a4ef-086a54f6b10e InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Sony Corporation VPCCB2S1E Package: linux (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic root=UUID=30b47f3a-9136-4791-a5c8-f72e6b1c7362 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 RelatedPackageVersions: linux-restricted-modules-3.0.0-17-generic N/A linux-backports-modules-3.0.0-17-generic N/A linux-firmware1.60.1 StagingDrivers: mei Tags: oneiric running-unity staging Uname: Linux 3.0.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout kismet lpadmin plugdev sambashare dmi.bios.date: 04/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1100V2:bd04/15/2011:svnSonyCorporation:pnVPCCB2S1E:pvrC6099RLH:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCCB2S1E dmi.product.version: C6099RLH dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1246131] Re: Apple Magic Trackpad connection instability
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246131 Title: Apple Magic Trackpad connection instability Status in “bluez” package in Ubuntu: Confirmed Bug description: I believe this issue is related to https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1216690. Connection drops out frequently, often accompanied by a mouse low battery notification. I have attached a compressed hci.log file. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 09:46:08 2013 InstallationDate: Installed on 2013-10-22 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6510 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=7f2c43b2-d3ad-4865-8230-768b23d023be ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd07/11/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: F0:7B:CB:AA:D7:5C ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:78393 acl:3434 sco:0 events:113 errors:0 TX bytes:1851 acl:33 sco:0 commands:43 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter
Christopher M. Penalver (penalvch) wrote on 2013-11-17: #31 Janne Savikko, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? Hi Christopher. Unfortunately I can not test this issue anymore, because I got an other model from retailer because of hardware problems. I too was running Ubuntu 11.10 before upgrade to 12.04, so as Jussi Palomäki wrote, this problem seems to be related to memory controller and was revealed when using old kernel. Jussi Palomäki (jmmpal) wrote on 2013-10-26: I believe mine was actually a memory controller related problem that was originally caused by a bug in Ubuntu 11.10: https://help.ubuntu.com/community/AsusZenbook#Suspend At least there seems to be a workaround available: open the case and unplug the battery. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/989191 Title: Asus Zenbook UX31E powers off on plugin in/out AC adapter Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: When I have logged in to Unity and plug in or out AC adapter to Asus Zenbook UX31E, computer powers off. Sometimes this needs couple of tries (waiting or not waiting in between) when plugin in or out AC adapter. This problem doesn't occur when I have switched to console or when in LightDM login screen. Problem doesn't happen with MS Windows either. And yes, there's enough power in my battery too, I can boot up and use the computer without AC adapter. syslog prints these lines to stdout in console, when plugin AC adapter first out and then in: [ 869.521396] asus_wmi: Unknown key 57 pressed [ 874.704525] asus_wmi: Unknown key 58 pressed [ 876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id What you also need: 1) lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 2) I could guess kernel, but it happens _only_ when I have logged in to Unity (or Unity 2D)... 3) I expect that my computer doesn't power off. 4) Computer powers off. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/989191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter
Fix released: PCI: EHCI: fix crash during suspend on ASUS computers https://github.com/torvalds/linux/commit/dbf0e4c7257f8d684ec1a3c919853464293de66e ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/989191 Title: Asus Zenbook UX31E powers off on plugin in/out AC adapter Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Fix Released Bug description: When I have logged in to Unity and plug in or out AC adapter to Asus Zenbook UX31E, computer powers off. Sometimes this needs couple of tries (waiting or not waiting in between) when plugin in or out AC adapter. This problem doesn't occur when I have switched to console or when in LightDM login screen. Problem doesn't happen with MS Windows either. And yes, there's enough power in my battery too, I can boot up and use the computer without AC adapter. syslog prints these lines to stdout in console, when plugin AC adapter first out and then in: [ 869.521396] asus_wmi: Unknown key 57 pressed [ 874.704525] asus_wmi: Unknown key 58 pressed [ 876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id What you also need: 1) lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 2) I could guess kernel, but it happens _only_ when I have logged in to Unity (or Unity 2D)... 3) I expect that my computer doesn't power off. 4) Computer powers off. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/989191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265544] Re: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7
I built the next test kernel, up to the following commit: e9cb81a22841908b1c075156b409a538d09c8466 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1265544 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1265544 Title: 8086:0a16 [UX302LG] black screen on boot 3.12.0-7 Status in “linux” package in Ubuntu: In Progress Bug description: Same description/workaround as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015 I tried both Enable CSM and non-CSM boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 Date: Thu Jan 2 09:59:33 2014 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:8a03 Atmel Corp. Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX302LG ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-7-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266551] Re: linux: 3.2.0-59.90 -proposed tracker
** Summary changed: - linux: 3.2.0-59.89 -proposed tracker + linux: 3.2.0-59.90 -proposed tracker ** Description changed: - This bug is for tracking the 3.2.0-59.89 upload package. This bug will + This bug is for tracking the 3.2.0-59.90 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, 06. January 2014 19:37 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Monday, 06. January 2014 19:37 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/1266551 Title: linux: 3.2.0-59.90 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-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 Precise: New Bug description: This bug is for tracking the 3.2.0-59.90 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, 06. January 2014 19:37 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Monday, 06. January 2014 19:37 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266551] Re: linux: 3.2.0-59.90 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New = 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/1266551 Title: linux: 3.2.0-59.90 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-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 Precise: New Bug description: This bug is for tracking the 3.2.0-59.90 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, 06. January 2014 19:37 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Monday, 06. January 2014 19:37 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266551/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1118447] Re: Race condition with network and NFS mounts causes boottime hang
This bug very clearly has nothing at all to do with the BIOS. Christopher, it is inappropriate to ask bug submitters to test with a new BIOS for bugs like this - the BIOS is entirely unrelated to the network filesystem layer, and if upgrading the BIOS did have any effect, it would be *irrelevant* to the bug at hand. ** Tags removed: bios-outdated-1903 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1118447 Title: Race condition with network and NFS mounts causes boottime hang Status in “linux” package in Ubuntu: Confirmed Status in “nfs-utils” package in Ubuntu: Incomplete Bug description: I seem to experience a race condition during boot of my ubuntu 12.04 server: In approx. one of seven boots, the server hangs during bootup. This is what I see on the screen: After the line * Starting configure network device there is a short delay of about 1 second, then messages continue. I see * Starting Mount network filesystems [ OK ] * Starting set sysctls from /etc/sysctl.conf [ OK ] * Starting configure network device [ OK ] * Stopping Mount network filesystems [ OK ] * Stopping set sysctls from /etc/sysctl.conf [ OK ] * Starting Block the mounting event for NFS filesytems until statd is running [ OK ] * Stopping Block the mounting event for NFS filesytems until statd is running [ OK ] * Starting Block the mounting event for NFS filesytems until statd is running [ OK ] * Stopping Block the mounting event for NFS filesytems until statd is running [ OK ] The last messages repeats several times, and then the boot process hangs. In 6/7 of cases, I wait for a minute, and after that bootup continues. But in approx 1/7 cases, the system hangs at this point forever. The machine does not respond to CTRL-ALT-DEL, I have to reboot it using SysRq-Keys. WORKAROUND: Setting the NFS entries in fstab to noauto completely removes the problem: There is no timeout during boot, and no lockup any more. The machine boote smoothly with the NFS-shares unmounted. After the machine is up, we can manually mount the NFS-shares without a problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-37-generic 3.2.0-37.58 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:252: keine Soundkarten gefunden ... ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: arecord: device_list:252: keine Soundkarten gefunden ... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 85.200104] lxcbr0: no IPv6 routers present Date: Thu Feb 7 15:50:40 2013 HibernationDevice: RESUME=UUID=6c172536-57cc-4deb-867a-0718d572f23e IwConfig: lono wireless extensions. eth0 no wireless extensions. lxcbr0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcEnviron: LANGUAGE=de:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=/dev/mapper/lvmvg-root ro debug splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Es läuft kein PulseAudio-Dienst oder nicht als Sessiondienst. RelatedPackageVersions: linux-restricted-modules-3.2.0-37-generic N/A linux-backports-modules-3.2.0-37-generic N/A linux-firmware1.79.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-28 (285 days ago) dmi.bios.date: 07/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd07/04/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1242180] Re: saucy regression - three monitors no longer work
You do know that no one knows what the fix is, only that it is in 3.12? You can see that Timo gave up trying to find it in mid-November. If Ubuntu is actually going to figure out the fix and backport it, then go for it. However I am extremely sceptical and had to devise my own workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: I've just upgraded from raring. There I had 3 monitors attached to my Intel HD Graphics 4000 (i7 3770 cpu) where it all works perfectly. (Two monitors are identical flanking my centre displayport monitor.) In saucy I can get any two monitors working, and any attempt to get all 3 working results in an error about setting crtc with a different number. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 14:28:59 2013 MarkForUpload: True SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265024] Re: TLS register TPIDRURW not preserved on context switch and fork
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1265024 Title: TLS register TPIDRURW not preserved on context switch and fork Status in “linux-ti-omap4” package in Ubuntu: In Progress Bug description: Please backport commit a4780adeefd042482f624f5e0d577bf9cdcbb760 (which is included in upstream kernel 3.11) to the ti-omap4 packages for ubuntu precise. I tried doing this manually, and when cherrypicking there's a minor pretty trivial conflict to resolve, and after cherrypicking it works just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/1265024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1265971] Re: Kernel panic during boot 3.11.0-15-generic
That is good news. Yes, the fix will be coming in the next stable release. ** Changed in: linux (Ubuntu) Status: Incomplete = 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/1265971 Title: Kernel panic during boot 3.11.0-15-generic Status in “linux” package in Ubuntu: Fix Committed Bug description: I've updated to 3.11.0-15-generic via aptitude and tried to reboot. During boot I've got a kernel panic with messages: uncompression error UFS: cannot open root device ... or unknown-block(0,0): error -6 Please append a correct root= boot option Previous version (3.11.0-14-generic) works on the same notebook, with the same BIOS settings. I can boot into it using corresponding GRAB option. Actually, I reported this bug using ubuntu-bug linux when loaded into previous version. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 2190 F pulseaudio /dev/snd/pcmC0D0p: nick 2190 F...m pulseaudio Date: Sat Jan 4 12:47:07 2014 InstallationDate: Installed on 2013-04-27 (251 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N76VJ MarkForUpload: True ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=6aa7ef52-c41f-4856-950a-bef3ba7b78e5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-23 (73 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N76VJ.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N76VJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN76VJ.203:bd07/09/2013:svnASUSTeKCOMPUTERINC.:pnN76VJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N76VJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1261524] Re: Same USB HDD gets different mounting behaviour depending on filesystem used?
Output of lsusb -v ** Attachment added: lsusb-v https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261524/+attachment/3943740/+files/lsusb-v ** Changed in: linux (Ubuntu) Status: Incomplete = 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/1261524 Title: Same USB HDD gets different mounting behaviour depending on filesystem used? Status in “linux” package in Ubuntu: New Bug description: Running Saucy on my laptop. I have a 2TB USB3.0 external HDD that is factory formatted in NTFS. When I first plugged it in, it was mounted like so: drwx-- 1 bladernr bladernr 4096 Dec 16 12:47 Alexandria and I was able to start creating a python script inside the disk : -rw--- 1 bladernr bladernr 179 Dec 16 12:47 update-library However, it was absolutely impossible to make that script executable. I tried remounting the drive by setting umaks, dmask and fmask to 0777, and I also tried setting the exec option. But there was absolutely no way I could make that script executable. So I reformatted the disk in ext4. This time, the drive mounted with ownership being root:root. Thus, still unusable, but even moreso this time because after I plugged in my hard disk, I was unable to even read the disk, let alone try to copy data or create files on it. In order to make my USB disk actually usable, as my user, I had to take the additional step of using chown on a cli. A user shouldn't have to take extraordinary measures like this to make their external HDD usable. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bladernr 2560 F pulseaudio /dev/snd/controlC2: bladernr 2560 F pulseaudio /dev/snd/controlC0: bladernr 2560 F pulseaudio Date: Mon Dec 16 15:21:35 2013 HibernationDevice: RESUME=UUID=c2f4cbc3-a904-4dbf-acd4-0a28f482d683 InstallationDate: Installed on 2012-03-15 (641 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120307) MachineType: Alienware M15x MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=e7eedf5d-5aad-4230-b123-47162b1acea6 ro RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-06-22 (177 days ago) dmi.bios.date: 08/24/2010 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd08/24/2010:svnAlienware:pnM15x:pvrA08:rvnAlienware:rn:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.name: M15x dmi.product.version: A08 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1261524] Re: Same USB HDD gets different mounting behaviour depending on filesystem used?
Joseph: I don't. This was on my primary workstation running Saucy and because I needed the drive, I couldn't just sit on it while debugging this. So I formatted it in ext4 as noted above, and worked around the root ownership. I'm pretty sure the permissions thing when it was formatted NTFS is due to NTFS not really supporting unix-style permissions, however, I was a bit taken that I was unable to make a script executable (AFAIK, executables on WIndows are marked Executable somehow on NTFS drives). But that's a fairly complex issue, Im led to believe. Once I chown'd the drive with my user name, the change stuck and now when I plug it in, I get the correct user/group ownership. I just found it very odd that my drive, after being formatted in ext4, when plugged in, was UID/GID root but still mounted to /media/MYUSERNAME/DISKLABEL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1261524 Title: Same USB HDD gets different mounting behaviour depending on filesystem used? Status in “linux” package in Ubuntu: New Bug description: Running Saucy on my laptop. I have a 2TB USB3.0 external HDD that is factory formatted in NTFS. When I first plugged it in, it was mounted like so: drwx-- 1 bladernr bladernr 4096 Dec 16 12:47 Alexandria and I was able to start creating a python script inside the disk : -rw--- 1 bladernr bladernr 179 Dec 16 12:47 update-library However, it was absolutely impossible to make that script executable. I tried remounting the drive by setting umaks, dmask and fmask to 0777, and I also tried setting the exec option. But there was absolutely no way I could make that script executable. So I reformatted the disk in ext4. This time, the drive mounted with ownership being root:root. Thus, still unusable, but even moreso this time because after I plugged in my hard disk, I was unable to even read the disk, let alone try to copy data or create files on it. In order to make my USB disk actually usable, as my user, I had to take the additional step of using chown on a cli. A user shouldn't have to take extraordinary measures like this to make their external HDD usable. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bladernr 2560 F pulseaudio /dev/snd/controlC2: bladernr 2560 F pulseaudio /dev/snd/controlC0: bladernr 2560 F pulseaudio Date: Mon Dec 16 15:21:35 2013 HibernationDevice: RESUME=UUID=c2f4cbc3-a904-4dbf-acd4-0a28f482d683 InstallationDate: Installed on 2012-03-15 (641 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120307) MachineType: Alienware M15x MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=e7eedf5d-5aad-4230-b123-47162b1acea6 ro RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-06-22 (177 days ago) dmi.bios.date: 08/24/2010 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd08/24/2010:svnAlienware:pnM15x:pvrA08:rvnAlienware:rn:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.name: M15x dmi.product.version: A08 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1257766] Re: can not reduce brightness on HP ZBook
Yes, it is still an issue on ubuntu 13.10. (No proprietary NVidia driver installed.) I will test the problem on the latest development version of ubuntu. The issue is worse than you might expect. I often need to read and edit documents and those use a white background (typically PDF documents). The brightness is so high that it turns the notebook almost unusable for me. Please note that the HP ZBook series is rather new (selling started about September 2013) and this might be the reason why not so many people complain about the brightness bug. Nevertheless, the other user confirmed the issue very recently (25th December). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1257766 Title: can not reduce brightness on HP ZBook Status in “linux” package in Ubuntu: Incomplete Bug description: machine: HP ZBook 15 (Intel Core i7 4700MQ Haswell, NVIDIA Quadro K1100M 2GB, 1920 x 1080 display) I go to the settings/Brightness Lock section. The button which should controll the screen brightness is on the right-hand side. I move it to the left-hand side but nothing happens. The screen brightness remains to be 100% (too much for me). The machine is running on the AC power cable. The machine uses an intel graphics driver. It contains also the NVidia card but that one is apparently inactive and the system did not offer me to install it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Dec 4 15:32:39 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1909] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1909] InstallationDate: Installed on 2013-12-04 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ZBook 15 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=b1bd90e2-af55-4f94-a86e-ec16ca8b47e4 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.06 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.06:bd10/25/2013:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10303:rvnHewlett-Packard:rn1909:rvrKBCVersion94.47:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Dec 4 15:18:15 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4589 vendor AUO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1261524] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1261524 Title: Same USB HDD gets different mounting behaviour depending on filesystem used? Status in “linux” package in Ubuntu: Confirmed Bug description: Running Saucy on my laptop. I have a 2TB USB3.0 external HDD that is factory formatted in NTFS. When I first plugged it in, it was mounted like so: drwx-- 1 bladernr bladernr 4096 Dec 16 12:47 Alexandria and I was able to start creating a python script inside the disk : -rw--- 1 bladernr bladernr 179 Dec 16 12:47 update-library However, it was absolutely impossible to make that script executable. I tried remounting the drive by setting umaks, dmask and fmask to 0777, and I also tried setting the exec option. But there was absolutely no way I could make that script executable. So I reformatted the disk in ext4. This time, the drive mounted with ownership being root:root. Thus, still unusable, but even moreso this time because after I plugged in my hard disk, I was unable to even read the disk, let alone try to copy data or create files on it. In order to make my USB disk actually usable, as my user, I had to take the additional step of using chown on a cli. A user shouldn't have to take extraordinary measures like this to make their external HDD usable. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bladernr 2560 F pulseaudio /dev/snd/controlC2: bladernr 2560 F pulseaudio /dev/snd/controlC0: bladernr 2560 F pulseaudio Date: Mon Dec 16 15:21:35 2013 HibernationDevice: RESUME=UUID=c2f4cbc3-a904-4dbf-acd4-0a28f482d683 InstallationDate: Installed on 2012-03-15 (641 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120307) MachineType: Alienware M15x MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=e7eedf5d-5aad-4230-b123-47162b1acea6 ro RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-06-22 (177 days ago) dmi.bios.date: 08/24/2010 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd08/24/2010:svnAlienware:pnM15x:pvrA08:rvnAlienware:rn:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.name: M15x dmi.product.version: A08 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266540] Re: linux: 3.11.0-16.25 -proposed tracker
** Summary changed: - linux: 3.11.0-16.24 -proposed tracker + linux: 3.11.0-16.25 -proposed tracker ** Description changed: - This bug is for tracking the 3.11.0-16.24 upload package. This bug will + This bug is for tracking the 3.11.0-16.25 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, 06. January 2014 18:44 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Monday, 06. January 2014 18:44 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/1266540 Title: linux: 3.11.0-16.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: New 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: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-16.25 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, 06. January 2014 18:44 UTC kernel-stable-phase:Prepare kernel-stable-phase-changed:Monday, 06. January 2014 18:44 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1266540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266737] Re: error sda: WRITE SAME failed when installing package
I tested by upgrading my kernel using apt-get dist-upgrade command. I tried the same scenario that is mentioned in the bug after upgrade. This is the state on my guest root@ubuntu:~# dpkg --list | grep linux ii libselinux1:ppc64el 2.2.1-1ubuntu2 ppc64el SELinux runtime shared libraries ii linux-headers-3.13.0-0 3.13.0-0.15 all Header files related to Linux kernel version 3.13.0 ii linux-headers-3.13.0-0-generic 3.13.0-0.15 ppc64el Linux kernel headers for version 3.13.0 on PowerPC 64el SMP ii linux-headers-3.13.0-1 3.13.0-1.16 all Header files related to Linux kernel version 3.13.0 ii linux-headers-3.13.0-1-generic 3.13.0-1.16 ppc64el Linux kernel headers for version 3.13.0 on PowerPC 64el SMP ii linux-headers-generic3.13.0.1.3 ppc64el Generic Linux kernel headers ii linux-headers-virtual3.13.0.1.3 ppc64el Transitional package. ii linux-image-3.13.0-0-generic 3.13.0-0.15 ppc64el Linux kernel image for version 3.13.0 on PowerPC 64el SMP ii linux-image-3.13.0-1-generic 3.13.0-1.16 ppc64el Linux kernel image for version 3.13.0 on PowerPC 64el SMP ii linux-image-virtual 3.13.0.1.3 ppc64el This package will always depend on the latest minimal generic kernel image. ii linux-virtual3.13.0.1.3 ppc64el Minimal Generic Linux kernel and headers ii util-linux 2.20.1-5.1ubuntu11 ppc64el Miscellaneous system utilities root@ubuntu:~# But still I am seeing the same issue again on my guest. Setting up perlbrew (0.66-1) ... Setting up perlindex (1.606-1) ... Generating index (this may take a while)...[ 1468.347473] sda: WRITE SAME failed. Manually zeroing. done. Setting up perlmagick (8:6.7.7.10-6ubuntu2) ... Setting up perlprimer-doc (1.1.21-1) ... Setting up perltidy (20120701-1) ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1266737 Title: error sda: WRITE SAME failed when installing package Status in “linux” package in Ubuntu: Confirmed Bug description: Description: == Was installing perl packages using apt-get install command. I saw WRITE SAME failed displayed during the process. Command used : apt-get install perl* on my Ubuntu guest to install all perl packages. I saw the message as below . . . . Setting up perlindex (1.606-1) ... Generating index (this may take a while)...sda: WRITE SAME failed. Manually zeroing. done. it took few seconds to complete and later on the process continued. Environment: Host: Power8 Guest : ubuntu hosted on Power8 used below qemu command : [root@localhost ubuntu_alpha1]# cat kvmg.p8.h KERNEL=trusty-server-cloudimg-ppc64el-vmlinuz-generic #FSIMAGE=trusty-server-cloudimg-ppc64el.img FSIMAGE=trusty-server-cloudimg-ppc64el.img.qcow2 MEM=8G qemu-system-ppc64 \ -enable-kvm -M pseries -cpu POWER8 -smp cores=4,threads=1 -m $MEM \ -net nic -net user \ -device spapr-vscsi -drive file=$FSIMAGE \ -kernel $KERNEL \ -append earlyprintk root=/dev/sda console=hvc0 --no-sessions \ -nographic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1266737] Re: error sda: WRITE SAME failed when installing package
you can get the guest access by logging into 9.3.189.114(root/.pasroot) cd /var/lib/libvirt/images/harini/bug_verify_image run ./kvmg_p8 -- this has qemu command and this will get the console for guest. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1266737 Title: error sda: WRITE SAME failed when installing package Status in “linux” package in Ubuntu: Confirmed Bug description: Description: == Was installing perl packages using apt-get install command. I saw WRITE SAME failed displayed during the process. Command used : apt-get install perl* on my Ubuntu guest to install all perl packages. I saw the message as below . . . . Setting up perlindex (1.606-1) ... Generating index (this may take a while)...sda: WRITE SAME failed. Manually zeroing. done. it took few seconds to complete and later on the process continued. Environment: Host: Power8 Guest : ubuntu hosted on Power8 used below qemu command : [root@localhost ubuntu_alpha1]# cat kvmg.p8.h KERNEL=trusty-server-cloudimg-ppc64el-vmlinuz-generic #FSIMAGE=trusty-server-cloudimg-ppc64el.img FSIMAGE=trusty-server-cloudimg-ppc64el.img.qcow2 MEM=8G qemu-system-ppc64 \ -enable-kvm -M pseries -cpu POWER8 -smp cores=4,threads=1 -m $MEM \ -net nic -net user \ -device spapr-vscsi -drive file=$FSIMAGE \ -kernel $KERNEL \ -append earlyprintk root=/dev/sda console=hvc0 --no-sessions \ -nographic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 607560] Re: jbd2 writing block every 5 - 10 seconds, preventing disk spin-down and making noise
Lonnie Lee Best / Rafael Duarte Vencioneck, 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 a Ubuntu repository 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 ** 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/607560 Title: jbd2 writing block every 5 - 10 seconds, preventing disk spin-down and making noise Status in “linux” package in Ubuntu: Incomplete Bug description: jbd2 writes blocks to the hard disk every 5 seconds. This makes an annoying click/tick noise and prevents the disk from spinning down to conserve power. jbd2 appears in logs as several entries like... Jul 19 21:35:45 edge kernel: [ 3312.913759] jbd2/sda5-8(350): WRITE block 42280704 on sda5 ... and can be observed using iotop. Since the noise only occurs in Ubuntu and not in Windows 7 it is probably a software problem. The excessive writes may reduce the disk's lifespan. WORKAROUND: Adding commit=60 to the partition's entry in fstab increases the interval to 30-45 seconds. Threads covering this problem * http://ubuntuforums.org/showthread.php?t=1489637 * https://bbs.archlinux.org/viewtopic.php?pid=692073 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-23-generic-pae 2.6.32-23.37 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-23.37-generic-pae 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rcx 2456 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 22' Mixer name : 'Intel G45 DEVIBX' Components : 'HDA:10ec0269,17aa21bc,0014 HDA:80862804,80860101,0010' Controls : 16 Simple ctrls : 8 Date: Mon Jul 19 23:24:03 2010 Frequency: Every 5-10 seconds. HibernationDevice: RESUME=UUID=ae276af8-b805-466a-a688-8d175cd3f2d7 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: LENOVO 05782AU ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic-pae root=UUID=01d19f79-8c81-4da6-949d-db8f4d85b84a ro quiet splash ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 RelatedPackageVersions: linux-firmware 1.34.1 SourcePackage: linux dmi.bios.date: 06/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 80ET37WW (1.14 ) dmi.board.name: 05782AU 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:bvr80ET37WW(1.14):bd06/11/2010:svnLENOVO:pn05782AU:pvrThinkPadEdge:rvnLENOVO:rn05782AU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 05782AU dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
